The keys used to sign a release belong to the release manager. If you are the release manager, you should use your keys. Damitha's instructions explain how to create a pair of keys. Ideally you should get someone else who knows you to validate your keys (its based on a "web of trust").
Paul
On 3/6/06, Damitha Kumarage <[EMAIL PROTECTED]> wrote:
Fred Preston wrote:
>
> Hi All,
> I'm trying to put up a new Axis release 1.6b onto Minotaur but
> I don't have the keys to create the .asc files. Does anyone know
> anything about this and how I can create the .asc files?
>
> Regards,
>
> Fred Preston.
To create a key pair
gpg --gen-key
This will be stored in ~/.gnupg
But I think you need to reuse the key pair used to release the earlier
release.
If you insist on creating a new key add this to the KEYS file
example.
gpg --armor --export [EMAIL PROTECTED] > MY_KEYS
copy the entry in MY_KEYS to KEYS file in the apache release folder
to create .asc files use for example
gpg --armor --output axis2c-src-M0.4.tar.gz.asc --detach-sig
axis2c-src-M0.4.tar.gz
regards
damitha
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
