From owner-freebsd-current@FreeBSD.ORG Sun Jul 4 20:43:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3482E16A4CE for ; Sun, 4 Jul 2004 20:43:46 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id F271543D31 for ; Sun, 4 Jul 2004 20:43:45 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 0635E6520C; Sun, 4 Jul 2004 21:43:45 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 98133-01; Sun, 4 Jul 2004 21:43:44 +0100 (BST) Received: from empiric.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 1B6A6651EE; Sun, 4 Jul 2004 21:43:44 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id DFA77614B; Sun, 4 Jul 2004 21:43:42 +0100 (BST) Date: Sun, 4 Jul 2004 21:43:42 +0100 From: Bruce M Simpson To: n0g0013 Message-ID: <20040704204342.GH13687@empiric.dek.spc.org> Mail-Followup-To: n0g0013 , freebsd-current@freebsd.org References: <0E972CEE334BFE4291CD07E056C76ED802E86EBB@bragi.housing.ufl.edu> <40E59559.8090907@cronyx.ru> <20040704202309.GA30837@eyore.cobbled.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <20040704202309.GA30837@eyore.cobbled.net> cc: freebsd-current@freebsd.org Subject: PGP headers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2004 20:43:46 -0000 --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--