MHSIGN(1)

NAME
mhsign - Script to interface gnupg signing with nmh email

SYNOPSIS
mhsign [-drRmbe] file
edit mhsign [-drRmbe]

DESCRIPTION
mhsign is a script to simplify signing and encrypting command line mh mail, using gnupg. When used directly, the source file, typically an mh draft file, is replaced by the signed or encrypted message. A backup copy of the original is saved, following usual mh conventions, in order to permit recovery from mistakes. mhsign is normally used from the whatnow prompt in the form
edit mhsign The user should have a file .pgpkeys in the MH directory (normally $HOME/Mail), or in the gnupg directory (normally $HOME/.gnupg). If both files exist, the one in the gnupg directory takes precedence. The .pgpkeys file is used to define an rsa key and a dss key for the user. It is permissible to only have one of these key definition lines. Other lines in the file may be used to define public keys for recipients. This is intended mainly to handle exceptions, where the recipient address used in email does not match the key uid in the user keyring. A sample file:
0x12345678    my_rsakey
0x98765432    my_dsskey
0x88888888    john@nowhere.org
Options

-d  Use dsskey to sign (this is the default)

-r  Use rsakey to sign. This will be defaulted if there is no dsskey defined.

-R  Use rsakey to sign, and force encryption to be pgp2 compatible. This requires that all recipient keys be pgp2 compatible.

-e  Encrypt to recipients, in addition to signing. The message will also be encrypted to the signing key.

-m  Use the PGP/Mime standard for signing and encrypting. This is automatic if the message is already a multipart mime message. Otherwise the default is to sign/encrypt in the old-fashioned non-mime manner, for compatibility with older software. When a message is signed but not encrypted, using the PGP/Mime formatting, any line beginning with "From " will be indented, and any trailing spaces will be removed from lines in the message body. This is to ensure maximum compatibility. Where trailing blanks are important (sending patches, for example), it would be wise to use quoted-printable or other mime encoding for that component.

-b  When PGP/Mime formatting, DO NOT remove trailing blanks nor indent any "From " lines. Note that using this option may result in signatures not verifying properly, depending on the software used for verification.

SEE ALSO
mhpgp(1), gpg