[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: signature and missing key

On Wed, Jun 18, 2003 at 12:15:09PM -0400, Derrick 'dman' Hudson wrote:
> On Tue, Jun 17, 2003 at 11:32:14PM +0100, Pigeon wrote:
> | With a dialup, it would be rather useful to be able to do this from the MTA
> | rather than the MUA.
> True.
> | Unfortunately /usr/share/doc/exim/spec.txt.gz contains no references
> | to either gpg or pgp.  Am I really out of luck for built-in
> | solutions?
> No, but you are out of luck (AFAIK) for ready-made solutions.
> What you can do is instruct exim to pass all messages through a pipe
> as it delivers them.  In your system filter put
>     unseen pipe "/usr/local/bin/gpg-key-retrieve"
> (read the exim manual for setting up a system filter; it really is
> quite trivial)

Yeah, you sorted me out with exim filters some time ago actually,
thanks! All mail comes through my only user, so I'm running it from
~/.forward to keep all my mail filtering in one place.

> Then create the program "gpg-key-retrieve".  It needs to parse enough
> of the message to determine the key's id and then merely run the gpg
> command to retrieve it.

This little hack seems to work, both for single messages and for
digests. It's not totally immune against getting the odd key that you
don't need, but I don't think that's a major problem.

TMPFILE=`mktemp -t getakey.XXXXXXXXXX` || exit 1
TMPGPG=`mktemp -t getakey.gpg.XXXXXXXXXX`
if [ $? -ne 0 ]; then
  rm -f $TMPFILE
  exit 1
sed -n -e '/^-----BEGIN PGP SIGNATURE-----$/,/^-----END PGP SIGNATURE-----$/p' > $TMPFILE 2>/dev/null
if [ -s $TMPFILE ]; then
  gpg --verify --keyserver $KEYSERVER $TMPFILE /dev/null > $TMPGPG 2>&1
  grep 'requesting key' $TMPGPG > /dev/null 2>&1 && (echo -n 'Key requested at '; 822-date; cat $TMPGPG) >> $LOGFILE
rm -f $TMPFILE
rm -f $TMPGPG


Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F

Attachment: pgpgPbhGO968J.pgp
Description: PGP signature

Reply to: