Date: Sun, 4 Jul 2004 21:43:42 +0100 From: Bruce M Simpson <bms@spc.org> To: n0g0013 <ttz@cobbled.net> Cc: freebsd-current@freebsd.org Subject: PGP headers Message-ID: <20040704204342.GH13687@empiric.dek.spc.org> In-Reply-To: <20040704202309.GA30837@eyore.cobbled.net> References: <0E972CEE334BFE4291CD07E056C76ED802E86EBB@bragi.housing.ufl.edu> <40E59559.8090907@cronyx.ru> <p06002035bd0b4bebb128@[10.0.1.3]> <20040704202309.GA30837@eyore.cobbled.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
[off-topic]
On Sun, Jul 04, 2004 at 09:23:09PM +0100, n0g0013 wrote:
> what is the story with PGP signatures these days? last i
> investigated there was a multi-part mime format that was meant
> to be standard and nobody used (except mutt, which i use).
>
> does anyone use that format or is it all inline now? mutt
> won't recognise the inline format as signed (and consequently
> won't verify the content).
I use procmail filter rules which handle this.
--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="rc.legacy-pgp"
# Add a "Content-Type: application/pgp" header so Mutt will know the
# mail is encrypted.
:0
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
:0 fBw
* ^.*-----BEGIN PGP MESSAGE-----
* ^.*-----END PGP MESSAGE-----
| formail -i "Content-Type: application/pgp; format=text; x-action=encrypt"
:0 fBw
* ^.*-----BEGIN PGP SIGNED MESSAGE-----
* ^.*-----BEGIN PGP SIGNATURE-----
* ^.*-----END PGP SIGNATURE-----
| formail -i "Content-Type: application/pgp; format=text; x-action=sign"
}
--Dxnq1zWXvFF0Q93v--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040704204342.GH13687>