Changes between Version 13 and Version 14 of keyringer
- Timestamp:
- Aug 18, 2017, 1:25:27 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
keyringer
v13 v14 1 1 = MFPL Shared Keyring = 2 3 == NOTE: repo change May 2017 ==4 5 The old MF/PL keys respository was in: `gitosis@git.mayfirst.org:mfpl/keys`. Now it is: `gitolite3@git.mayfirst.org:keys`6 7 Please update!8 2 9 3 [wiki:support-team Support Team Home] 10 4 11 MFPL uses an OpenPGP encrypted file, that is shared via git, to store root and encrypted disk passphrases. If you have '''broken''' keyringer, some instructions for repair can be found at #6700.5 The May First/People Link shared keyring maintains our shared passwords and other sensitive data on accessible to the support team, such as protocols on handling attacks and sensitive data about our networks. 12 6 13 To help us securely read and create new keys, we use a program called [http://git.sarava.org/?p=keyringer.git;a=summary keyringer]. 7 ''NOTE: repo change May 2017'': The old MF/PL keys respository was in: `gitosis@git.mayfirst.org:mfpl/keys`. Now it is: `gitolite3@git.mayfirst.org:keys`. Please update! 14 8 15 = Setting up Keyringer = 9 == Documents == 10 11 Our protocol and network documents are in the folder called docs. 12 13 For passwords, MFPL uses an OpenPGP encrypted file, that is shared via git, to store root and encrypted disk passphrases. To help us securely read and create new keys, we use a program called [http://git.sarava.org/?p=keyringer.git;a=summary keyringer]. 14 15 == Setting up Keyringer == 16 16 17 Members of the support team can access the keys by following these steps: 17 18 … … 34 35 }}} 35 36 36 = Editing a Keyringer Entry = 37 == Editing a Keyringer Entry == 38 37 39 From time to time you may need to edit a row in the keyring, for example after changing a password. 38 40 39 == Using the helper script==41 === Using the helper script === 40 42 41 43 The MF/PL keyringer repository comes with a script call pass that can be used as a wrapper to the keyringer commands used to decrypt and encrypt the keyring file. … … 55 57 And follow the prompts. 56 58 57 == Manually==59 === Manually === 58 60 59 61 Assuming that you have keyringer set up properly, there is a command should unlock the keys, and pass it to an editor. It also creates a decrypted temp file in the keyringer temp directory. The command is: