-
Notifications
You must be signed in to change notification settings - Fork 36
Managing Credentials
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.
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
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}.
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
About the software
System Overview
Client Application
Server Application
Server Platform
Development practices
GitHub Usage
Java Style
Testing
Releases
For field users and testers
Software Install and Configuration
Upon Receiving Your Gear
Setting Up a Tablet
Setting Up a Server
Setting Up an Access Point
Reference Configuration