VAGUE Archives

February 2006

VAGUE@LIST.UVM.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Campbell <[log in to unmask]>
Reply To:
Vermont Area Group of Unix Enthusiasts <[log in to unmask]>
Date:
Sat, 18 Feb 2006 18:50:14 -0500
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (40 lines)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 17 Feb 2006, Anthony Carrico wrote:

> On Fri, Feb 17, 2006 at 08:39:33PM -0500, Anthony Carrico wrote:
> > I think you may have to do something like using a TEMPORARY key ring
> > to create and export each sig. Then you just email it and later it
> > will show up in your real keyring when it makes it into a keyserver
> > and you sync.
>
> Here is a lightly edited example of this method:
>
	Armed with this suggestion, I've produced a shell script to do the
drudge work involved in this, which, if anyone else wants it, I've put up
at:

	http://www.ci-n.com/~jcampbel/gpguidsign

	It's invoked with "gpguidsign ABCD1234 [log in to unmask]". You
still need to select the UID to be signed manually and make sure that you're
actually signing the one that you told it you were going to sign, and type
your passphrase a couple of times, but that's an improvement over manually
typing the whole series of gpg commands. It doesn't handle error conditions
very gracefully, but as long as you don't tell it yes when it asks to send
the email, the worst it should do is create and delete a couple of tempfiles
and spew some error messages.

- -- 
John Campbell
[log in to unmask]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD97LCPu/PJk2ePZ0RAuxcAKCgL0AKqwPXermf3CCpCaBMRZoIbQCfaewh
wSMVTOEskoZoY1ct6It5SjA=
=j0eg
-----END PGP SIGNATURE-----

ATOM RSS1 RSS2