The gpg docs are here http://www.gnupg.org/gph/en/manual.html and yes, you need to generate a keypair first before trying to sign something.
I don't know if it is ok to gen and store keys on apache boxes, though. Anyone know? If you can get Cygwin or something equivalent that lets you run gpg and shell scripts locally, you can use the scripts that I added to /committers/releases to create and verify the sigs once you have created the keypair using gpg --gen-key hth, Phil On Mon, 14 Mar 2005 09:56:17 -0000, Eric Pugh <[EMAIL PROTECTED]> wrote: > I was taking a swing at ascii armour'ing the signatures, and have a > couple questions. Following the directions in > http://wiki.apache.org/jakarta-commons/SigningReleases, there is a > section about using gpg. > > I logged onto my Apache account, and tried to do the command: > > gpg --armor --export 'your name' > > However, nothing gets produced. What I am wondering is if I need to > somehow install my key? I followed the PGPMail directions, so my > private key is on my windows laptop. Do I need to create using gpg my > main key instead? > > There are some tantalizing mentions in PGPMail's documentation about > ascii armouring, but no details on how to do it, just that it exists. > > Eric > > -----Original Message----- > From: robert burrell donkin > [mailto:[EMAIL PROTECTED] > Sent: Friday, March 11, 2005 9:01 PM > To: Jakarta Commons Developers List > Subject: Re: [VOTE] [email] promote RC4 to 1.0 status > > hi eric > > could you ascii armour the signatures? > > (it's not essential but it makes them a lot nicer to read and download) > > - robert > > On Fri, 2005-03-11 at 20:30, Eric Pugh wrote: > > Hi all, > > > > A couple of packaging issues were discovered in Email 1.0 RC3. I was > > encouraged to fix them and then call for a fresh vote, so I appreciate > > > the understanding of the community that the (now) 4 release candidates > > > it's taken to get email to 1.0. My first time signing a project. > > > > The release candidate is available at > > http://www.apache.org/~epugh/email/distributions/ and is just RC3 with > > > some packaging tweaks, not Java code changes. The documentation is > > available at http://www.apache.org/~epugh/email/docs > > > > This is a full release vote (and so three +1's are required). please > > check the release before voting +1. i will not tally the votes before > > 2300 hours GMT on Tuesday 15th of March. > > > > here's my +1 > > > > - Eric > > > > -8<------------------------------------------------------------- > > [ ] +1 Promote RC4 to commons-email-1.0 > > [ ] +0 In favour of this release > > [ ] -0 Against this release > > [ ] -1 Do not release RC4 > > ---------------------------------------------------------------- > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
