diff options
author | Tom Ryder <tom@sanctum.geek.nz> | 2017-10-14 02:11:48 +1300 |
---|---|---|
committer | Tom Ryder <tom@sanctum.geek.nz> | 2017-10-14 02:11:48 +1300 |
commit | 3c2f72ce27f5d85280c855d960326c42ffde6ab9 (patch) | |
tree | 0ca6ee10ef4fc61606c46ab80dd4999c9cab4446 | |
parent | Correct usage information for runcrypt (diff) | |
download | Mail-Run-Crypt-3c2f72ce27f5d85280c855d960326c42ffde6ab9.tar.gz Mail-Run-Crypt-3c2f72ce27f5d85280c855d960326c42ffde6ab9.zip |
Mention that signing is optional
-rw-r--r-- | lib/Mail/Run/Crypt.pm | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/Mail/Run/Crypt.pm b/lib/Mail/Run/Crypt.pm index 4d7f74d..d1d56e0 100644 --- a/lib/Mail/Run/Crypt.pm +++ b/lib/Mail/Run/Crypt.pm @@ -144,11 +144,11 @@ error content, it is mailed (each stream separately) to a specified recipient address. The idea is to allow you to view the output of automated commands while having -the content encrypted as it passes through to your mailserver, and have some -assurance that the content was actually generated by the server concerned. -C<cron(8)> scripts are the ideal use case, but this would also with C<at(1)> or -anything else that might non-interactively run jobs for which output is -significant. +the content encrypted as it passes through to your mailserver, and (optionally) +have some assurance that the content was actually generated by the server +concerned. C<cron(8)> scripts are the ideal use case, but this would also with +C<at(1)> or anything else that might non-interactively run jobs for which +output is significant. You probably want to call this with the C<runcrypt(1)> program installed by this distribution, which provides a means to set the properties for the module |