Re: ContactInfo?

[F. Fox]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nathaniel Dube wrote:
> In the torrc file is the ContactInfo option.  Here's an example.
> 
> #ContactInfo 1234D/ Random Person 
> 
> My question is, what format should I put my GPG key?
(snip)

I don't know if it's really that strict a convention.

FWIW, mine looks like this:

ContactInfo 4096R/A6DA0830 F. Fox (New RSA key) 

Basically, the 4096R indicates that it's a 4096-bit RSA key (D would be
for Diffie-Hellman-based keys). The part after the 0x in your key ID, is
what goes after the slash.

- --
F. Fox
AAS, CompTIA A+/Network+/Security+
Owner of Tor node "kitsune"
http://fenrisfox.livejournal.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBSDN3Guj8TXmm2ggwAQgJxxAAicECdOPjSqX/O4F6QVrUKEv3YhpZ+gt/
SfEfmLCAv3t/hK/7rtjbNbCYu6DmfJf9t+DGi4LkjEu/4DLPgtjtDuyE/BlkT0eT
WYXc9m/DRX5rN3GhP0yF7SzXUl7WgDYOWgiijr18ESZ+diCPgdlAfOzj0xkwS57a
vMTWOTw0hewizb63O2wb50K9zQsX7GT/6bSJXAoPAYEUXLD4Hiy0bGjuGmyth+/I
xzxZYOLNVz0z0DYS6Sc92IgjMmoJ/0jF10Wc0tuYpxqRnkDcpRJYJAiAavfZmzVC
XMa+hJR2Kd6g1vCxqgexkq7SLyvRBj2e9VFrCV/+ekCUojFB68Dr4oYRqvFygadM
U8ax6YFtILU7O8UmLpQWCMuHrLx8jHwZ1Rcq8liOcnPsOGr4yWpLwy63g7R7XKxj
daeTCptl85sFxtCt63f0v+p3XXI75HjoWema1EAc+ex93o9wDl9YJhKCsupPE5A7
AcIOHXEBHaX3mLiluNPVR1S0F487YErq2y6ew4KHOXuoDtiZTGPAUk0kl9KoXAb7
V1jxdmeqg8fhozdW/RhPnQAfwAYD8MbbpBJk666cMImEqH662eq286toxFeWWdHE
TSUCpREwjbspocHr0xqxpREGAjhD+csg78fDVlY+ylXUsGAFIP6+g5bMhU3+B30C
jzjlGClJTP4=
=OsCo
-END PGP SIGNATURE-

Re: ContactInfo?

[Nick Mathewson]

On Sun, May 18, 2008 at 11:41:02PM +0200, Karsten Loesing wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hey Nathaniel,
> 
> | In the torrc file is the ContactInfo option.  Here's an example.
> |
> | #ContactInfo 1234D/ Random Person 
> |
> | My question is, what format should I put my GPG key?
> 
> That doesn't matter so much. The intention of the contact line is not to
> parse it automatically (previous attempts were not very successful), but
> are read by humans. In fact, it might be better to obfuscate that line a
> bit in order to prevent the bots from collecting your address -- or make
> their "lives" a bit harder. Further, in most cases your GPG key won't be
> used to encrypt notice message to you or verify your mails to us anyway.

Though when we want it, we *really* want it.  :) The short-key format
is usually good enough, though if you want to include a fingerprint or
a long keyid, that would probably be fine.

(A line with a long keyid would look like:

   ContactInfo 1024R/ Somebody 

You can make gpg emit long keyids rather than short ones by specifying
"--keyid-format long" on the command line.)

yrs,
-- 
Nick Mathewson

Re: ContactInfo?

[Karsten Loesing]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hey Nathaniel,

| In the torrc file is the ContactInfo option.  Here's an example.
|
| #ContactInfo 1234D/ Random Person 
|
| My question is, what format should I put my GPG key?

That doesn't matter so much. The intention of the contact line is not to
parse it automatically (previous attempts were not very successful), but
are read by humans. In fact, it might be better to obfuscate that line a
bit in order to prevent the bots from collecting your address -- or make
their "lives" a bit harder. Further, in most cases your GPG key won't be
used to encrypt notice message to you or verify your mails to us anyway.

By the way, thank you for running a relay!

- --Karsten
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIMKJu0M+WPffBEmURAiRYAJ4kt9GAxLzj8ZFb1MvU8k4ZSCljBgCcCwwe
5fjeF2xi8RUc2fH7QLiKuj0=
=v3ae
-END PGP SIGNATURE-