-
Notifications
You must be signed in to change notification settings - Fork 9
Committer Keys
This page lists the keys in use by Metasploit committers.
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 merges and commits is easy and fun. Have a local signing key generated, 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.
- Home Welcome to Metasploit!
- Using Metasploit A collection of useful links for penetration testers.
-
Setting Up a Metasploit Development Environment From
apt-get installtogit push. - CONTIBUTING.md What should your contributions look like?
- Landing Pull Requests Working with other people's contributions.
- Using Git All about Git and GitHub.
- Contributing to Metasploit Be a part of our open source community.
- Meterpreter All about the Meterpreter payload.