Revision as of 15:44, 4 October 2012 by Ghudson
This is information for developers who are newly receiving commit access.
- Athena account: MITKC staff will sponsor as appropriate. See http://web.mit.edu/accounts/www/getaccount.html for some overview information about Athena accounts.
- X.509 client certificate: Needed for RT access, among others. Information on how to obtain one is at http://web.mit.edu/ist/topics/certificates/index.html
- RT account
- Git access
- Daptiv access (for some contributors working on time-sensitive projects)
- Posting authorization to cvs-krb5 if you are going to commit stuff.
Where stuff is at
- Git URL git.mit.edu:/git/krb5.git -- you may need to put "username@" in front of the hostname if your local username is not the same as your Athena account name. Kerberos-authenticated SSH is best, if you can get it to work.
- SSH to athena.dialup.mit.edu if you want easy access to AFS, a UNIX shell, etc.
- You'll need to set GSSAPIDelegateCredentials=yes in order to do passwordless login, because user home directories are in AFS, and the administrators didn't want to confuse users who logged in with Kerberos but couldn't access their files.
- RT https://krbdev.mit.edu/rt/ (or https://krbdev.mit.edu:444/rt/ if your browser doesn't deal with "optional" SSL client certificate verification)