Gnuk - Revision history

61.244.94.211 at 16:23, 31 October 2013

2013-10-31T16:23:47Z

← Older revision		Revision as of 09:23, 31 October 2013
Line 13:		Line 13:
	2. Install the following packages:		2. Install the following packages:

	* gnupg/gnupg2 (gnupg version >= 1.4 ~~or gnupg2~~)		* gnupg/gnupg2 (gnupg version >= 1.4)
	* gpg-agent		* gpg-agent
	* scdaemon		* scdaemon

Lilia at 06:52, 14 May 2013

2013-05-14T06:52:02Z

← Older revision		Revision as of 23:52, 13 May 2013
Line 42:		Line 42:
	Add your pub key to the server you want to auth with your GPG token:		Add your pub key to the server you want to auth with your GPG token:
	ssh ~/.ssh/authorized_keys		ssh ~/.ssh/authorized_keys


			5a. Add udev rules for the FST. Create a file called /lib/udev/rules.d/60-gnupg.rules with the following contents:

			ATTR{idVendor}=="234b", ATTR{idProduct}=="0000", ENV{ID_SMARTCARD_READER}="1", ENV{ID_SMARTCARD_READER_DRIVER}="gnupg", GROUP="plugdev", MODE="644"
			LABEL="gnupg_rules_end"

Unixjazz at 06:12, 14 May 2013

2013-05-14T06:12:33Z

← Older revision		Revision as of 23:12, 13 May 2013
Line 15:		Line 15:
	* gnupg/gnupg2 (gnupg version >= 1.4 or gnupg2)		* gnupg/gnupg2 (gnupg version >= 1.4 or gnupg2)
	* gpg-agent		* gpg-agent
			* scdaemon
	* python-pyscard (to use a tool for removing keys)		* python-pyscard (to use a tool for removing keys)


	3. Edit your GPG configuration:		3. Edit your GPG configuration:

Unixjazz at 06:06, 14 May 2013

2013-05-14T06:06:21Z

← Older revision		Revision as of 23:06, 13 May 2013
Line 15:		Line 15:
	* gnupg/gnupg2 (gnupg version >= 1.4 or gnupg2)		* gnupg/gnupg2 (gnupg version >= 1.4 or gnupg2)
	* gpg-agent		* gpg-agent
	* gnupg-pkcs11-scd (substitute for scdaemon under 'Squeeze')
	* python-pyscard (to use a tool for removing keys)		* python-pyscard (to use a tool for removing keys)

108.85.224.67 at 21:15, 24 April 2013

2013-04-24T21:15:16Z

← Older revision		Revision as of 14:15, 24 April 2013
Line 117:		Line 117:
	Add this line to 'gnome-keyring-ssh.desktop':		Add this line to 'gnome-keyring-ssh.desktop':
	X-GNOME-Autostart-enabled=false		X-GNOME-Autostart-enabled=false

	Add this line to 'gnome-keyring-gpg.desktop':		Add this line to 'gnome-keyring-gpg.desktop':
	X-GNOME-Autostart-enabled=false		X-GNOME-Autostart-enabled=false

108.85.224.67 at 21:13, 24 April 2013

2013-04-24T21:13:57Z

← Older revision		Revision as of 14:13, 24 April 2013
Line 74:		Line 74:
	gpg> save		gpg> save
	This will apply the changes		This will apply the changes


	7. Write your public and private GPG keys to the token		7. Write your public and private GPG keys to the token
Line 92:		Line 91:
	gpg> save		gpg> save
	This command will save the info to the token and exit the shell		This command will save the info to the token and exit the shell


	8. Using your keys in other computers with GPG installed		8. Using your keys in other computers with GPG installed
Line 107:		Line 105:
	gpg> trust		gpg> trust
	This command will set the key you just installed as 'trusted'. Given it is your own key, set it to (5) 'ultimate' trust		This command will set the key you just installed as 'trusted'. Given it is your own key, set it to (5) 'ultimate' trust


	9. Before you use the token, make sure you deactivate other gpg agents. Here are some popular agents:		9. Before you use the token, make sure you deactivate other gpg agents. Here are some popular agents:

Line 123:		Line 120:
	Add this line to 'gnome-keyring-gpg.desktop':		Add this line to 'gnome-keyring-gpg.desktop':
	X-GNOME-Autostart-enabled=false		X-GNOME-Autostart-enabled=false


	11. Common Issues		11. Common Issues

108.85.224.67 at 21:13, 24 April 2013

2013-04-24T21:13:01Z

← Older revision		Revision as of 14:13, 24 April 2013
Line 38:		Line 38:

	Generate your ssh keys [5]:		Generate your ssh keys [5]:
	gpgkey2ssh ~~ADD_YOUR_SUBKEY_ID_HERE~~ >> sshpubkey.txt		gpgkey2ssh TYPE_YOUR_SUBKEY_ID_HERE >> sshpubkey.txt

	Add your pub key to the server you want to auth with your GPG token:		Add your pub key to the server you want to auth with your GPG token:
Line 79:		Line 79:

	Invoke GPG shell with this command, adding your key ID where indicated:		Invoke GPG shell with this command, adding your key ID where indicated:
	gpg --edit-key ~~ADD_YOUR_KEY_ID_HERE~~		gpg --edit-key TYPE_YOUR_KEY_ID_HERE

	gpg> keytocard		gpg> keytocard
Line 103:		Line 103:

	The key is now registered by your local install of GPG, but you have to set the trust of it:		The key is now registered by your local install of GPG, but you have to set the trust of it:
	gpg --edit-key ~~ADD_YOUR_KEY_ID_HERE~~		gpg --edit-key TYPE_YOUR_KEY_ID_HERE

	gpg> trust		gpg> trust
Line 127:		Line 127:
	11. Common Issues		11. Common Issues

	* If you get ~~the~~ 'OpenPGP card not available: general error', try killing gpg-agents, such as gnome-keyring;		* If you get 'OpenPGP card not available: general error', try killing gpg-agents, such as gnome-keyring;
	* If you type a wrong PIN three times, you will lock the device permanently, be extra carefull!		* If you type a wrong PIN three times, you will lock the device permanently, be extra carefull!
	* If you need to re-write keys to the token, make sure to delete the keys on it first [6].		* If you need to re-write keys to the token, make sure to delete the keys on it first [6].
	* If you remove your keys from the device, your PIN will be erased as well and reverted to the default PIN (12345678), remember to change it.		* If you remove your keys from the device, your PIN will be erased as well and reverted to the default PIN (12345678), remember to change it!.

108.85.224.67 at 21:09, 24 April 2013

2013-04-24T21:09:31Z

108.85.224.67 at 21:06, 24 April 2013

2013-04-24T21:06:31Z

← Older revision		Revision as of 14:06, 24 April 2013
Line 131:		Line 131:
	* If you type a wrong PIN three times, you will lock the device permanently, be extra carefull!		* If you type a wrong PIN three times, you will lock the device permanently, be extra carefull!
	* If you need to re-write keys to the token, make sure to delete the keys on it first [6].		* If you need to re-write keys to the token, make sure to delete the keys on it first [6].
			* If you remove your keys from the device, your PIN will be erased as well and reverted to the default PIN (12345678), remember to change it.

Unixjazz at 23:53, 22 March 2013

2013-03-22T23:53:27Z

← Older revision		Revision as of 16:53, 22 March 2013
Line 2:		Line 2:
	'''		'''

	This is a quick tutorial on how to get your public and private key to work with the Flying Stone Tiny[1] GPG token. All the information here was taken from the complete documentation of Gnuk written by its author[2]. Benefits of the Flying Stone Tiny-01 include: a) keeping your secrets separated from a hard-disk, which is a common medium for the storage of GPG secrets and could potentially represent a major security risk; b) ability to use your keys in multiple computers; c) hardware-lock preventing the secrets to be read from the token; d) it is USB, which means it is (almost) universal, dipensing the need for a Smart Card reader, while having all the benefits of a smart card; d) it is all free software-based (GPLv3), therefore it is not only transparent and widely available, but also free for further improvements and new inventive usages.		This is a quick tutorial on how to get your public and private key to work with the Flying Stone Tiny[1] GPG token. All the information here was taken from the complete documentation of Gnuk written by its author[2]. Benefits of the Flying Stone Tiny-01 include: a) keeping your secrets separated from a hard-disk, which is a common medium for the storage of GPG secrets and could potentially represent a major security risk; b) ability to use your keys in multiple computers; c) hardware-lock preventing the secrets to be read from the token; d) it is USB, which means it is (almost) universal, dipensing the need for a Smart Card reader, while having all the benefits of a smart card; d) it is all free software-based (GPLv3), therefore it is not only transparent and widely available, but also free for further improvements and new inventive usages. After completing the tutorial, if you still have questions, access the Q&A forum [3] and check Riseup's tutorial [7].

	After completing the tutorial, if you still have questions, access the Q&A forum [3] and check Riseup's tutorial [].

← Older revision		Revision as of 14:09, 24 April 2013
Line 1:		Line 1:
	'''Using Gnuk on Debian Wheezy		'''Using Gnuk on Debian Wheezy'''
	'''

	This is a quick tutorial on how to get your public and private key to work with the Flying Stone Tiny[1] GPG token. All the information here was taken from the complete documentation of Gnuk written by its author[2]. Benefits of the Flying Stone Tiny-01 include: a) keeping your secrets separated from a hard-disk, which is a common medium for the storage of GPG secrets and could potentially represent a major security risk; b) ability to use your keys in multiple computers; c) hardware-lock preventing the secrets to be read from the token; d) it is USB, which means it is (almost) universal, dipensing the need for a Smart Card reader, while having all the benefits of a smart card; d) it is all free software-based (GPLv3), therefore it is not only transparent and widely available, but also free for further improvements and new inventive usages. After completing the tutorial, if you still have questions, access the Q&A forum [3] and check Riseup's tutorial [7].		This is a quick tutorial on how to get your public and private key to work with the Flying Stone Tiny[1] GPG token. All the information here was taken from the complete documentation of Gnuk written by its author[2]. Benefits of the Flying Stone Tiny-01 include: a) keeping your secrets separated from a hard-disk, which is a common medium for the storage of GPG secrets and could potentially represent a major security risk; b) ability to use your keys in multiple computers; c) hardware-lock preventing the secrets to be read from the token; d) it is USB, which means it is (almost) universal, dipensing the need for a Smart Card reader, while having all the benefits of a smart card; d) it is all free software-based (GPLv3), therefore it is not only transparent and widely available, but also free for further improvements and new inventive usages. After completing the tutorial, if you still have questions, access the Q&A forum [3] and check Riseup's tutorial [7], or just pop-up at #noisebridge on Freenode and ask us.


	1. Check requerements for using the GPG token:		1. Check requerements for using the GPG token:

	- Your GPG keys must be RSA 2048 bits, if your keys do not met the requirement, generate new keys[4];		* Your GPG keys must be RSA 2048 bits, if your keys do not met the requirement, generate new keys[4];
	- FST-01 USB token with Gnuk pre-installed ~~(click here for alternatives)~~;		* FST-01 USB token with Gnuk pre-installed;
	- GNU/Linux system (should work on other *nix systems, but not yet tested).		* GNU/Linux system (should work on other *nix systems, but not yet tested).


	2. Install the following packages:		2. Install the following packages:

	- gnupg/gnupg2 (gnupg version >= 1.4 or gnupg2)		* gnupg/gnupg2 (gnupg version >= 1.4 or gnupg2)
	- gpg-agent		* gpg-agent
	- gnupg-pkcs11-scd (substitute for scdaemon under 'Squeeze')		* gnupg-pkcs11-scd (substitute for scdaemon under 'Squeeze')
	- python-pyscard (to use a tool for removing keys)		* python-pyscard (to use a tool for removing keys)


Line 112:		Line 111:
	9. Before you use the token, make sure you deactivate other gpg agents. Here are some popular agents:		9. Before you use the token, make sure you deactivate other gpg agents. Here are some popular agents:

	- gnome-keyring (GNOME)		* gnome-keyring (GNOME)
	- kwallet (KDE)		* kwallet (KDE)
	- seahorse		* seahorse


Line 128:		Line 127:
	11. Common Issues		11. Common Issues

	* If you get the 'OpenPGP card not available: general error', try killing gpg-agents, such as gnome-keyring;		* If you get the 'OpenPGP card not available: general error', try killing gpg-agents, such as gnome-keyring;
	* If you type a wrong PIN three times, you will lock the device permanently, be extra carefull!		* If you type a wrong PIN three times, you will lock the device permanently, be extra carefull!
	* If you need to re-write keys to the token, make sure to delete the keys on it first [6].		* If you need to re-write keys to the token, make sure to delete the keys on it first [6].
	* If you remove your keys from the device, your PIN will be erased as well and reverted to the default PIN (12345678), remember to change it.		* If you remove your keys from the device, your PIN will be erased as well and reverted to the default PIN (12345678), remember to change it.