Files
metasploit-gs/Committer-Keys.md
T
2013-12-16 13:36:57 -08:00

3.3 KiB

This page lists the keys in use by Metasploit committers.

Account E-mail Gist MIT
@jvazquez-r7 juan.vazquez@metasploit.com B9352D83 0x38D99152B9352D83
@jvennix-r7 joev@metasploit.com 3E85A2B0 0x127b05fb3e85a2b0
@limhoff-r7 luke_imhoff@rapid7.com 4A071FB3 0x858AC3174A071FB3
@Meatballs1 eat_meatballs@hotmail.co.uk 1F2F8B38 0x5380EAF01F2F8B38
@OJ oj@buffered.io 1FAA5749 0x49EEE7511FAA5749
@scriptjunkie1 scriptjunkie@scriptjunkie.us 591C6B5D 0xE0F49052591C6B5D
@todb-r7 tod_beardsley@rapid7.com ADB9F193 0x1EFFB682ADB9F193
@wchen-r7 wei_chen@rapid7.com F06F730B 0x2384DB4EF06F730B
@wvu-r7 william_vu@rapid7.com C1629024 0xE761DCB4C1629024

Signing criteria

In order to get @todb-r7 to sign your key, you should:

  • tell him your Key ID over some mechanism (IRC, Skype, etc)
  • post it to https://gist.github.com under your GitHub account

If you are near by, he'll ask you to confirm your Key ID in meatspace, using unique biometric and contextual data to verify your identity. If not, he'll e-mail you, using that key and a known e-mail address, and expect your response.

This constitutes verification that your key is, in fact, yours. Please set a reasonable expiration date (18 months is recommended), key length (2048 or better), and use good sense when managing your private key availability.

Signing HOWTO

Signing merges and commits is easy and fun. Generate a signing key, if you don't have one already, using your favorite PGP/GPG interface (I use gpg --gen-key). Then add this to your $HOME/.gitconfig:

[user]
  name = Your Name
  email = your_email@example.com
  signingkey = DEADBEEF # Must match name and email exactly!
[alias]
  c = commit -S --edit
  m = merge -S --no-ff --edit

Using git c and git m from now on will sign every commit with your DEADBEEF key.