Re: [Possible SPAM] Re: UID changes (was Key Revocation)

2007-05-02 Thread Robert J. Hansen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > pub 1024D/98E6705C 2005-11-23 > uid Chris Pollock (New email address as of 04/21/07) > <[EMAIL PROTECTED]> > uid Chris Pollock <[EMAIL PROTECTED]> No need to put the (New email...) comment in place. The rul

[Possible SPAM] Re: UID changes (was Key Revocation)

2007-05-02 Thread Chris
On Sunday 22 April 2007 1:18 am, Robert J. Hansen wrote: > > Optionally, later on you can also do a (again, you have to pick > > whether to "revuid" or "deluid) (a "#" indicates a comment): > > This will not work if you've sent your key to a keyserver, as is > recommended. It will also not work if

Re: UID changes (was Key Revocation)

2007-04-23 Thread Dirk Traulsen
Am 21 Apr 2007 um 23:25 hat Henry Hertz Hobbit geschrieben: > Once your changes are done, make sure you generate a new > revocation file with a: > > $ gpg -a --gen-revoke 98E6705C > rev_cpollock_embarqmail_com.asc > Is it really necessary to generate a new revocation certificate if you only cha

Re: UID changes (was Key Revocation)

2007-04-21 Thread Robert J. Hansen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > Optionally, later on you can also do a (again, you have to pick > whether to "revuid" or "deluid) (a "#" indicates a comment): This will not work if you've sent your key to a keyserver, as is recommended. It will also not work if you've sent yo

Re: UID changes (was Key Revocation)

2007-04-21 Thread Henry Hertz Hobbit
David Shaw wrote: > You select the user id with "uid x" where x is the number of > the user ID. Then "revuid". Optionally, later on you can also do a (again, you have to pick whether to "revuid" or "deluid) (a "#" indicates a comment): $ gpg --edit-key 98E6705C Command> uid # shows uids so yo