Date: Sun, 04 Jul 2004 23:08:34 +0200 From: Stephan van Beerschoten <stephanb@whacky.net> To: n0g0013 <ttz@cobbled.net> Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: ibcs2 and svr4 compat removed, linux to follow Message-ID: <40E871D2.8040405@whacky.net> 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
n0g0013 wrote: >On 02.07-19:31, Brad Knowles wrote: >[ ... ] > > >> Yup. PGP sign everything, and make sure that your keys don't >>ever get stolen or compromised. That makes it much harder for >>someone to successfully impersonate you. >> >> > >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). > > > Been there, done it, fixed it. Try the following recipe in your .procmailrc if you use procmail. If you don't, consider doing it ;) # Make old style PGP readable for Mutt: # :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" } :0 fBw * ^-----BEGIN PGP PUBLIC KEY BLOCK----- * ^-----END PGP PUBLIC KEY BLOCK----- | formail -i "Content-Type: application/pgp-keys; format=text;" Have fun :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40E871D2.8040405>