Skip to content

Managing Credentials

Adam Kalachman edited this page Mar 19, 2015 · 1 revision

Overview

This document describes how we manage credentials used for administration. Only project administrators have access to these credentials; if you feel that you need access, please contact one of them.

Tasks

Cloning the Repo

All credentials are stored as 3DES-encrypted files in the release GitHub repo. If you have access, you'll want to clone the repo into the same directory as your other repos:

git clone https://github.com/ProjectBuendia/release.git

Decrypting a Credential

In order to decrypt a credential, you'll need access to the master password, which is only known to project administrators.

Once you have the password, you can decrypt a password by running, for example:

cd passwords ./decrypt.sh godaddy.enc

You'll be prompted for the master password.

Once you've finished using a password, clear your screen buffer! On Mac, you can do this by pressing {nav Cmd + K}.

Encrypting a Credential

First, follow the instructions in Decrypting a Credential to access the master password. Next, create a file under passwords with all the credential information you need. Then, run:

./encrypt.sh service-name

where service-name is the name of the service for which the password is used. Enter the master password twice when prompted. When complete, the original file will be deleted, leaving behind only the encrypted file of form service-name.enc.

Verify that the password has been encrypted properly, then push the change to GitHub:

git checkout dev git pull git add service-name.enc git commit -a -m 'Added a password for service-name' git push

Clone this wiki locally