Confidential Howto - Revision history

Rfs: /* How to look at the confidential information */

2010-09-25T18:50:08Z

How to look at the confidential information

Valerie at 20:42, 6 July 2010

2010-07-06T20:42:15Z

Rfs: spelling

2007-08-17T20:47:53Z

spelling

Shawn: /* Howto change the confidential information */

2007-08-17T20:23:14Z

Howto change the confidential information

Stillflame: /* Howto change the confidential information */ more

2007-08-17T20:13:01Z

Howto change the confidential information: more

Stillflame: /* Howto change the confidential information */ bettered

2007-08-17T20:07:22Z

Howto change the confidential information: bettered

Stillflame: /* Howto look at the confidential information */ mentioned password

2007-08-17T20:02:49Z

Howto look at the confidential information: mentioned password

Stillflame: started the howto on using gpg to view confidential information file

2007-08-17T19:40:06Z

started the howto on using gpg to view confidential information file

New page

==Howto look at the confidential information==

* make sure you are an accepted member of the list of authorized people, and therefore belong to the appropriate svn group and have access to the confidential information gpg key
* make sure you understand the proper handling of both the gpg key and the actual confidential information
* this implies that you do all of the following on a computer you have reasonable trust in
* that does not include ryukin or any other public server at freegeek
* check for van Eck Phreakers in the immediate area
* just in case, wrap your head in aluminum foil to prevent them from stealing your password
* svn co svn+ssh://svn.freegeek.org/svn/freegeek_confidential
* cd freegeek_confidential
* gpg -d < passwords
* read it in your terminal
* make sure you close your terminal
* make sure you delete any copy you make of the decrypted information

==Howto change the confidential information==
* review the security notes from the previous section
* gpg -d < passwords > new_passwords
* edit new_passwords
* gpg -se < new_passwords > passwords
* rm new_passwords

==Howto handle a compromise of this security==
whether because of mishandled keys, staffing changes, or malicious attack, there will come a time when this information will need to have a "change of guards".

* change all the passwords at each of the places listed
* gpg --gen-key
* gpg -se < new_passwords > passwords
* rm new_passwords
* gpg --export 8ae62f03 > key
* gpg --export-secret-keys 8ae62f03 > secret_key
* ''very carefully'' redistribute the new key

@@ Line 4: / Line 4: @@
 * Make sure you understand the proper handling of both the gpg key and the actual confidential information.
 * This implies that you do all of the following on a computer you have reasonable trust in.
-* That does not include ryukin or any other public server at Free Geek.
+* That does not include [[Free Geek's internal application server]] or any other public server at Free Geek.
 * Check for van Eck Phreakers in the immediate area.
 * Just in case, wrap your head in aluminum foil to prevent them from stealing your password.

← Older revision		Revision as of 20:42, 6 July 2010
Line 39:		Line 39:
	* gpg --export-secret-keys 8ae62f03 > secret_key		* gpg --export-secret-keys 8ae62f03 > secret_key
	* ''Very carefully'' redistribute the new key.		* ''Very carefully'' redistribute the new key.
		+
		+	[[Category: Procedures]]

@@ Line 1: / Line 1: @@
-==Howto look at the confidential information==
+==How to look at the confidential information==
-* make sure you are an accepted member of the list of authorized people, and therefore belong to the appropriate svn group and have access to the confidential information gpg key
+* Make sure you are an accepted member of the list of authorized people, and therefore belong to the appropriate svn group and have access to the confidential information gpg key.
-* make sure you understand the proper handling of both the gpg key and the actual confidential information
+* Make sure you understand the proper handling of both the gpg key and the actual confidential information.
-* this implies that you do all of the following on a computer you have reasonable trust in
+* This implies that you do all of the following on a computer you have reasonable trust in.
-* that does not include ryukin or any other public server at freegeek
+* That does not include ryukin or any other public server at Free Geek.
-* check for van Eck Phreakers in the immediate area
+* Check for van Eck Phreakers in the immediate area.
-* just in case, wrap your head in aluminum foil to prevent them from stealing your password
+* Just in case, wrap your head in aluminum foil to prevent them from stealing your password.
 * svn co svn+ssh://svn.freegeek.org/svn/freegeek_confidential
 * cd freegeek_confidential
 * gpg -d < passwords
-* gpg will ask you for a password - type it in
+* gpg will ask you for a password. Type it in.
-* read the passwords in your terminal
+* Read the passwords in your terminal.
-* make sure you close your terminal
+* Make sure you close your terminal.
-* make sure you delete any copy you make of the decrypted information
+* Make sure you delete any copy you make of the decrypted information.
-==Howto change the confidential information==
+==How to change the confidential information==
-* review the security notes from the previous section
+* Review the security notes from the previous section.
 * gpg -d < passwords > to_edit
 ** "-d" is for decrypt
 ** gpg will ask you for a password.  type it in
-* edit to_edit
+* Edit to_edit
 * gpg -se < to_edit > passwords
 ** "-se" is for sign and encrypt
@@ Line 29: / Line 29: @@
 * svn commit
-==Howto handle a compromise of this security==
+==How to handle a compromise of this security==
-whether because of mishandled keys, staffing changes, or malicious attack, there will come a time when this information will need to have a "change of guards".
+Whether because of mishandled keys, staffing changes, or malicious attack, there will come a time when this information will need to have a "change of guards".
-* change all the passwords at each of the places listed
+* Change all the passwords at each of the places listed.
 * gpg --gen-key
 * gpg -se < new_passwords > passwords
@@ Line 38: / Line 38: @@
 * gpg --export 8ae62f03 > key
 * gpg --export-secret-keys 8ae62f03 > secret_key
-* ''very carefully'' redistribute the new key
+* ''Very carefully'' redistribute the new key.

@@ Line 18: / Line 18: @@
 * review the security notes from the previous section
 * gpg -d < passwords > to_edit
-* gpg will ask you for a password.  type it in
+** "-d" is for decrypt
 * edit to_edit
 * gpg -se < to_edit > passwords
-* gpg will ask you for a password.  type it in
+** "-se" is for sign and encrypt
-* gpg may ask you if you should use this key even though you don't know it is someone.  say yes.
+** gpg will ask you for a password.  type it in
-* gpg will ask you who to encrypt it for.  type "staff", hit enter, then hit enter when it repeats the question again
+** gpg may ask you if you should use this key even though you don't know it is someone.  say yes.
 * rm to_edit
 * svn commit

@@ Line 22: / Line 22: @@
 * gpg -se < to_edit > passwords
 * gpg will ask you for a password.  type it in
-* gpg will ask you if you should use this key even though you don't know it is someone.  say yes.
+* gpg may ask you if you should use this key even though you don't know it is someone.  say yes.
-* rm new_passwords
+* gpg will ask you who to encrypt it for.  type "staff", hit enter, then hit enter when it repeats the question again
 ==Howto handle a compromise of this security==