aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWojciech Polak <polak@gnu.org>2003-08-24 18:23:30 +0000
committerWojciech Polak <polak@gnu.org>2003-08-24 18:23:30 +0000
commit66efe3f3046d623e3f8234ccc9502973c5c9b4a8 (patch)
treeb50f69b559a75f2bf10a4d957ab8c8e2970ce12c /doc
parent453eff1936ab5214fdb113507f383a077def9d8e (diff)
downloadanubis-66efe3f3046d623e3f8234ccc9502973c5c9b4a8.tar.gz
anubis-66efe3f3046d623e3f8234ccc9502973c5c9b4a8.tar.bz2
Updated
Diffstat (limited to 'doc')
-rw-r--r--doc/anubis.texi49
1 files changed, 39 insertions, 10 deletions
diff --git a/doc/anubis.texi b/doc/anubis.texi
index f2acf45..2a4bea3 100644
--- a/doc/anubis.texi
+++ b/doc/anubis.texi
@@ -470,6 +470,10 @@ This option specifies an output level for an additional file
@end table
@end deffn
+@deffn Option tracefile @var{file-name}
+@opindex tracefile @var{file-name}
+@end deffn
+
@node Proxy Settings, Encryption Settings, Output Settings, CONTROL Section
@subsection Proxy Settings
@@ -1346,37 +1350,62 @@ GNU Anubis supports the GNU Privacy Guard via the
@cmindex gpg-encrypt @var{gpg-keys}
This command enables encrypting your outgoing message with the
GNU Privacy Guard (Pretty Good Privacy) public key(s).
-@var{gpg-keys} is a comma separated list of keys.
+@var{gpg-keys} is a comma separated list of keys (with no space
+between commas and keys).
@smallexample
gpg-encrypt "John's public key"
@end smallexample
@end deffn
-@deffn Command gpg-sign @var{passphrase}
-@deffnx Command gpg-sign @samp{yes}
-@cmindex gpg-sign @var{passphrase}
+@deffn Command gpg-sign @var{gpg-signer-key}
+@deffnx Command gpg-sign @samp{yes-or-default}
+@cmindex gpg-sign @var{gpg-signer-key}
This command signs the outgoing message with your
-GNU Privacy Guard private key. Specify the @var{passphrase} unless
-you have already set it using @code{gpg-passphrase}. In the latter
-case, use the second form of the command.
+GNU Privacy Guard private key. Specify a @var{passphrase} with
+@code{gpg-passphrase}. Value @samp{default} means your default
+private key, but you can change it if you have more than one
+private key.
For example:
@smallexample
-gpg-sign "my passphrase"
+gpg-sign default
@end smallexample
or
@smallexample
@group
-gpg-passphrase "my passphrase"
-gpg-sign yes
+gpg-passphrase "my office key passphrase"
+gpg-sign office@@example.key
@end group
@end smallexample
@end deffn
+@deffn Command gpg-sign-encrypt @var{gpg-keys}[:@var{gpg-signer-key}]
+@deffnx Command gpg-se @var{gpg-keys}[:@var{gpg-signer-key}]
+@cmindex gpg-sign-encrypt @var{gpg-keys}[:@var{gpg-signer-key}]
+This command signs and encrypts (both at same time) your outgoing message.
+It has the same effect as @command{gpg -se}. The first argument is
+required and is exactly the same as for @samp{gpg-encrypt}. The second
+argument is optional and must be preceded with a colon (@samp{:}).
+It specifies an optional signer key, which by default is set to your
+default private key (exactly the same as for @samp{gpg-sign}).
+
+For example:
+
+@smallexample
+gpg-sign-encrypt John@@example.key
+@end smallexample
+
+or
+
+@smallexample
+gpg-se John@@example.key:office@@example.key
+@end smallexample
+@end deffn
+
@node External Processor, Quick Example, Mail Encryption, Action List
@subsection Using an External Processor

Return to:

Send suggestions and report system problems to the System administrator.