On Sunday 22 May 2005 9:38 pm, John Hendrickson wrote: > Hi, > > I authored xdm-options Is that the package you want sponsored and added to Debian? Have you read the New Maintainers' Guide? http://www.debian.org/doc/maint-guide/index.en.html and the list FAQ: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html and the developer's reference: http://www.debian.org/doc/developers-reference/ You also need to check out WNPP and submit an ITP bugreport: http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-newpackage > My gpg private key (see user id below) was made using defaults from > sarge's gpg --gen-key. Should I beg for it to be signed? http://www.debian.org/devel/join/nm-step2 > I would also like to help Debian by doing (whatever is seems important > that my skills allow). New Package maintainer. Fletching bug reports. > Whatever, except MS Windows. It's rare that "tasks" are "assigned" to new developers or new applicants (like me). Volunteer work depends on motivation and that requires interest. You alone can decide which tasks interest you enough to keep you motivated to finish the work required. > # --keyserver keyring.debian.org > # --keyserver subkeys.pgp.net Am I right in thinking you created this key as root? If you did, export the public and secret keys to files in your user space, delete the keys from root and import them into a user keyring. (Make sure you have a revocation certificate printed out too.) There's nothing you need to do with keys that requires access as root and it's generally not advisable to have secret keys available to root. http://www.dcglug.org.uk/linux_adm/gnupg.html > gpg --recv-keys E75400DB The key is fine, created yesterday. You'll need to meet at least one existing Debian Developer (DD) and do some keysigning before this key can be part of your application to Debian as a new developer. http://www.dcglug.org.uk/linux_doc/gnupgsign.html#intro > gpg: key E75400DB: "John D. Hendrickson (Have Fun!) > <debguy@sourceforge.net>" no BTW. all sourceforge email is redirected to a real account - it's common for people to put the real account in the UID rather than the SF one. There's no intrinsic problem, AFAICT, but there's no real reason not to have the real account in a UID on the same key either. As it stands, you would have to ensure your email client can send mail as the SF ID so that the From: field is the SF address, not the yahoo address because email verification is part of the keysigning. You must be able to send signed email from at least one email address listed as a UID in the key. Any queries on gnupg - after you've read the page above - off-list please, gnupg is off-topic for this list. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpZdgkE5M8mQ.pgp
Description: PGP signature