Noisebridge - User contributions [en]

People

2013-06-21T08:42:08Z

108.85.224.67:

{{Membership}}[[Category:Members]]

The marshmallowy good enjoyables associated with Noisebridge.

This is ''not'' a membership list. Anyone may add themselves to it. Its names are maintained solely by those who have added them to it.

Add yourself in alphabetical order by first name.

[[User:SFSlim|Aaron Muszalski]]

[[AdamJODonnell|Adam J. O'Donnell]]

[[User:elgreengeeto|Adam Skory]]

[[User:adamwaters|Adam Waters]]

[[User:awright|Adam J. Wright]]

[[User:OpenBuddha|Al Billings]]

[[User:AlSweigart|Al Sweigart]]

[[User:Orph|Alex Graveley]]

[[User:VonGuard|Alex Handy]]

[[User:Alison|Alison B.]]

[[User:Amouravski|Andrei Mouravski]]

[[User:Adi|Andy Isaacson]]

[[User:Vniow|Ani Niow]]

[[User:LeMonkey|Ari Braginsky]]

[[User:Paulproteus|Asheesh]]

[[User:Yerdua|AudreyPenven]]

[[Usr:Bifrost|Evil Bifrost]]

[[User:Bill|Bill Paul]]

[[User:Endenizen|Brian Ferrell]]

[[User:warner|Brian Warner]]

[[User:caitlyn|Caity]]

[[User:charliep|Charlie Hsu]]

[[User:chris-kun|Chris Bolton]]

[[User:murph|Chris Murphy]]

[[User:chris|Chris Palmer]]

[[User:christie|Christie Dudley]]

[[User:cmaier|Christoph Maier]]

[[User:cobolt|Cobolt]]

[[User:colleen|Colleen Smith]]

[[User:ladyfox14|Cristina Chow]]

[[User:da3mon|damon mccormick]]

[[User:cubes|Daneil C. Silverstein]]

[[User:fdr|Dan Farina]]

[[Daniela Steinsapir]]

[[User:Malaclyps|Danny O'Brien]]

[[User:awkwardwhitejew|Dan Sherizen]]

[[User:Avidd|Davidfine]]

[[DavidMolnar]]

[[User:David415|David Stainton]]

[[User:dr1ce|Dr1ce]]

[[User:edrabbit|Ed Hunsinger]]

[[User:eleddy|Elizabeth Leddy]]

[[User:Eri|Eri Comparri]]

[[User:Eric Vinyl|Eric Vinyl]]

[[User:EkriirkE|Erik Johnson]]

[[User:chaoflow|Florian Friesdorf]]

[[User:Binaryfever|Fred McHale]]

[[User:gpvillamil|Gian Pablo Villamil]]

[[User:glenjarvis|Glen Jarvis]]

[[Greg Albrecht]]

[[User:grey|grey]]

[[User:glamrock|Griffin Boyce]]

[[User:Azureviolin|Hao Zhang]]

[[User:mooflyfoof|Heather Lynch]]

[[Håkon Nilsen]]

[[User:verbal|ian]]

[[User:DejaPu|Isky]]

[[JakeAppelbaum]]

[[User:Jared|Jared Dunne]]

[[Jason Araujo]]

[[User:mightyohm|Jeff Keyzer]]

[[Jeff Tchang]]

[[User:JeffreyATW|Jeffrey Carl Faden]]

[[User:jnny|Jenny Ryan]]

[[User:Jessabella|Jessabella Hancilla]]

[[User:wrecca|Gescykae Welz 'formerly Jesse']]

[[User:Thex|J.C.]]

[[User:joachimp|Joachim Pedersen]]

[[User:jlapenna|Joe LaPenna]]

[[JimStockford]]

[[User:BuddhaHacker|Jonas S Karlsson]]

[[User:Jof|Jonathan Lassoff]]

[[User:aeonsf|John Menerick]]

[[User:Kaufman|John J. Kaufman]]

[[User:jtfoote|Jonathan Foote]]

[[User:jbm|Josh Myer]]

[[User:Jabra|Joshua D. Abraham]]

[[User:keith|keith causey]]

[[User:Kenhaggerty|Ken M. Haggerty]]

[[User:Kreedy|Kevin Reedy]]

[[User:Kimardenmiller|Kim Miller]]

[[User:Kragen|Kragen Javier Sitaker]]

[[User:netsniper|Kristian Erik Hermansen]]

[[User:Gadlen|Lee Sonko]]

[[User:Leif|Leif Ryge]]

[[User:le|Luiz Eduardo]]

[[User:Lizzard|Liz Henry]]

[[Malakkar Vohryzek]]

[[User:Marc|Marc Powell]]

[[User:Mfb|Mark Burdett]]

[[User:Kripto|Mark Cohen]]

[[User:WlfyIT|Matt "Wolfy" Meier]]

[[User:matt|Matt Peterson]]

[[User:theUtherSide|Matthew Downs]]

[[User:Mattbot|Mattbot]]

[[User:Maymay|Meitar "maymay" Moscovitz]]

[[Mendelt Siebenga]]

[[User:Meredith|Meredith scheff]]

[[User:Meyermagic|Meyer S. Jacobs]]

[[User:Micah|Micah]]

[[User:mprados|Michael Prados]]

[[User:MichaelShiloh|Michael Shiloh]]

[[User:MCT|Michael Toren (mct)]]

[[User:Michiexile|Mikael Vejdemo Johansson]]

[[User:maltman23|Mitch Altman]]

[[User:Mlp|Mlp]]

[[User:miloh|R. Miloh Alexander]]

[[User:Reverend Mik|Reverend Mik McAllister]]

[[User:mkw813|Morgan]]

[[User:Tnkgrl|Myriam Joire]]

[[NateLawson]]

[[User:neha|Neha Chriss]]

[[User:flipzagging|Neil Kandalgaonkar]]

[[User:Nickthedude | Nickthedude]]

[[User:Owen|Owen]]

[[User:Enki|Paul Böhm]]

[[User:Pearl|Pearl]]

[[User:Pde|Peter Eckersley]]

[[User:standardusername|Peter Youngmeister]]

[[User:h0mee|Praveen Sinha]]

[[Quinn Norton]]

[[User:rachel|Rachel McConnell]]

[[User:rick|Rick Deacon]]

[[User:Rikke|Rikke Rasmussen]]

[[User:rubin110|Rubin Starset]]

[[User:RyanBagueros|Ryan Bagueros]]

[[User:Topsycatt|Sam Sobell]]

[[User:sethalves|Seth Alves]]

[[User:Schoen|Seth Schoen]]

[[User:Simone|Simone Davalos]]

[[User:skyex|skye x]]

[[User:mrcamuti|Steve Camuti]]

[[User:Mediapathic|Steen]]

[[User:ThOMG|Thom Hastings]]

[[User:Tony Longshanks|Tony Longshanks LeTigre]]

[[User:Unixjazz|Unixjazz]]

[[User:Whimzy|The Whimsical Wizard of ZiP]]

[[User:window|Window Snyder]]

[[User:xndr|Xander Hudson]]

[[User:yan|yan]]

[[User:zephyr|Zephyr]]

[[User:ZandrMilewski|Zandr Milewski]]

Gnuk

2013-04-24T21:15:16Z

108.85.224.67:

'''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], or just pop-up at #noisebridge on Freenode and ask us.

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];
* FST-01 USB token with Gnuk pre-installed;
* GNU/Linux system (should work on other *nix systems, but not yet tested).

2. Install the following packages:

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

3. Edit your GPG configuration:

Add the following content to your ~/.gnupg/gpg.conf file:

use-agent
personal-digest-preferences SHA256
cert-digest-algo SHA256
default-preference-list SHA512 SHA384 SHA256 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
default-key ADD_YOUR_KEY_ID_HERE

4. In order to use the token, make sure you are running gpg-agent, if not:

Run gpg-agent:
gpg-agent --daemon --enable-ssh-support

5. If you are planning to use the token to authenticate with OpenSSH

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

Add your pub key to the server you want to auth with your GPG token:
ssh ~/.ssh/authorized_keys

6. Personalize your token

To change your personal info, URL where your pub key is, etc., run:
gpg --card-edit

gpg> admin
Allow admin commands to be executed

gpg> name
Register name and surname of the token owner

gpg> url
Address for the location of your public keys, important setting to help you register the token in other machines

gpg> passwd
Set-up your PIN for the usage of the token, please this is not your 'passphrase' for the GPG private key
The default PIN from the factory is "123456"; your new PIN should not be bigger than 8 characters.
It does not have to be numbers -- the acronym PIN is misleading here.

gpg> forcesig
This will change the default setting of 'signature force PIN' OFF

gpg> login
Register your login name

gpg> help
This is command is your friend, if you want to further customize the token!

gpg> save
This will apply the changes

7. Write your public and private GPG keys to the token

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

gpg> keytocard
This command will *move* your pub GPG key to the token

gpg> toggle
This command changes from pub key to the private key operation

gpg> keytocard
This command will move your private key to the token

gpg> save
This command will save the info to the token and exit the shell

8. Using your keys in other computers with GPG installed

Invoke the GPG shell with this command:
gpg --card-edit

gpg> fetch
This command will retrieve your keys and add it to the local GPG keychain

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

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

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

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

10. Access '/etc/xdg/autostart' and '~/.config/autostart' and add a new entry to the following config files:

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

11. Common Issues

* 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 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!*.

12. Sources

[1] http://www.seeedstudio.com/wiki/FST-01

[2] http://www.fsij.org/doc-gnuk/

[3] http://no-passwd.net/askbot/questions/scope:all/sort:activity-desc/page:1/

[4] http://keyring.debian.org/creating-key.html

[5] http://www.programmierecke.net/howto/gpg-ssh.html

[6] http://no-passwd.net/askbot/question/51/how-to-deletereplace-the-key-in-gnuk/

[7] https://we.riseup.net/debian/using-the-openpgp-card-with-subkeys

Gnuk

2013-04-24T21:13:57Z

108.85.224.67:

'''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], or just pop-up at #noisebridge on Freenode and ask us.

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];
* FST-01 USB token with Gnuk pre-installed;
* GNU/Linux system (should work on other *nix systems, but not yet tested).

2. Install the following packages:

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

3. Edit your GPG configuration:

Add the following content to your ~/.gnupg/gpg.conf file:

use-agent
personal-digest-preferences SHA256
cert-digest-algo SHA256
default-preference-list SHA512 SHA384 SHA256 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
default-key ADD_YOUR_KEY_ID_HERE

4. In order to use the token, make sure you are running gpg-agent, if not:

Run gpg-agent:
gpg-agent --daemon --enable-ssh-support

5. If you are planning to use the token to authenticate with OpenSSH

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

Add your pub key to the server you want to auth with your GPG token:
ssh ~/.ssh/authorized_keys

6. Personalize your token

To change your personal info, URL where your pub key is, etc., run:
gpg --card-edit

gpg> admin
Allow admin commands to be executed

gpg> name
Register name and surname of the token owner

gpg> url
Address for the location of your public keys, important setting to help you register the token in other machines

gpg> passwd
Set-up your PIN for the usage of the token, please this is not your 'passphrase' for the GPG private key
The default PIN from the factory is "123456"; your new PIN should not be bigger than 8 characters.
It does not have to be numbers -- the acronym PIN is misleading here.

gpg> forcesig
This will change the default setting of 'signature force PIN' OFF

gpg> login
Register your login name

gpg> help
This is command is your friend, if you want to further customize the token!

gpg> save
This will apply the changes

7. Write your public and private GPG keys to the token

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

gpg> keytocard
This command will *move* your pub GPG key to the token

gpg> toggle
This command changes from pub key to the private key operation

gpg> keytocard
This command will move your private key to the token

gpg> save
This command will save the info to the token and exit the shell

8. Using your keys in other computers with GPG installed

Invoke the GPG shell with this command:
gpg --card-edit

gpg> fetch
This command will retrieve your keys and add it to the local GPG keychain

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

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

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

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

10. Access '/etc/xdg/autostart' and '~/.config/autostart' and add a new entry to the following config files:

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

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

11. Common Issues

* 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 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!*.

12. Sources

[1] http://www.seeedstudio.com/wiki/FST-01

[2] http://www.fsij.org/doc-gnuk/

[3] http://no-passwd.net/askbot/questions/scope:all/sort:activity-desc/page:1/

[4] http://keyring.debian.org/creating-key.html

[5] http://www.programmierecke.net/howto/gpg-ssh.html

[6] http://no-passwd.net/askbot/question/51/how-to-deletereplace-the-key-in-gnuk/

[7] https://we.riseup.net/debian/using-the-openpgp-card-with-subkeys

Gnuk

2013-04-24T21:13:01Z

108.85.224.67:

'''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], or just pop-up at #noisebridge on Freenode and ask us.

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];
* FST-01 USB token with Gnuk pre-installed;
* GNU/Linux system (should work on other *nix systems, but not yet tested).

2. Install the following packages:

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

3. Edit your GPG configuration:

Add the following content to your ~/.gnupg/gpg.conf file:

use-agent
personal-digest-preferences SHA256
cert-digest-algo SHA256
default-preference-list SHA512 SHA384 SHA256 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
default-key ADD_YOUR_KEY_ID_HERE

4. In order to use the token, make sure you are running gpg-agent, if not:

Run gpg-agent:
gpg-agent --daemon --enable-ssh-support

5. If you are planning to use the token to authenticate with OpenSSH

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

Add your pub key to the server you want to auth with your GPG token:
ssh ~/.ssh/authorized_keys

6. Personalize your token

To change your personal info, URL where your pub key is, etc., run:
gpg --card-edit

gpg> admin
Allow admin commands to be executed

gpg> name
Register name and surname of the token owner

gpg> url
Address for the location of your public keys, important setting to help you register the token in other machines

gpg> passwd
Set-up your PIN for the usage of the token, please this is not your 'passphrase' for the GPG private key
The default PIN from the factory is "123456"; your new PIN should not be bigger than 8 characters.
It does not have to be numbers -- the acronym PIN is misleading here.

gpg> forcesig
This will change the default setting of 'signature force PIN' OFF

gpg> login
Register your login name

gpg> help
This is command is your friend, if you want to further customize the token!

gpg> save
This will apply the changes

7. Write your public and private GPG keys to the token

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

gpg> keytocard
This command will *move* your pub GPG key to the token

gpg> toggle
This command changes from pub key to the private key operation

gpg> keytocard
This command will move your private key to the token

gpg> save
This command will save the info to the token and exit the shell

8. Using your keys in other computers with GPG installed

Invoke the GPG shell with this command:
gpg --card-edit

gpg> fetch
This command will retrieve your keys and add it to the local GPG keychain

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

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

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

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

10. Access '/etc/xdg/autostart' and '~/.config/autostart' and add a new entry to the following config files:

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

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

11. Common Issues

* 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 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!*.

12. Sources

[1] http://www.seeedstudio.com/wiki/FST-01

[2] http://www.fsij.org/doc-gnuk/

[3] http://no-passwd.net/askbot/questions/scope:all/sort:activity-desc/page:1/

[4] http://keyring.debian.org/creating-key.html

[5] http://www.programmierecke.net/howto/gpg-ssh.html

[6] http://no-passwd.net/askbot/question/51/how-to-deletereplace-the-key-in-gnuk/

[7] https://we.riseup.net/debian/using-the-openpgp-card-with-subkeys

Gnuk

2013-04-24T21:09:31Z

108.85.224.67:

'''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], or just pop-up at #noisebridge on Freenode and ask us.

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];
* FST-01 USB token with Gnuk pre-installed;
* GNU/Linux system (should work on other *nix systems, but not yet tested).

2. Install the following packages:

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

3. Edit your GPG configuration:

Add the following content to your ~/.gnupg/gpg.conf file:

use-agent
personal-digest-preferences SHA256
cert-digest-algo SHA256
default-preference-list SHA512 SHA384 SHA256 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
default-key ADD_YOUR_KEY_ID_HERE

4. In order to use the token, make sure you are running gpg-agent, if not:

Run gpg-agent:
gpg-agent --daemon --enable-ssh-support

5. If you are planning to use the token to authenticate with OpenSSH

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

Add your pub key to the server you want to auth with your GPG token:
ssh ~/.ssh/authorized_keys

6. Personalize your token

To change your personal info, URL where your pub key is, etc., run:
gpg --card-edit

gpg> admin
Allow admin commands to be executed

gpg> name
Register name and surname of the token owner

gpg> url
Address for the location of your public keys, important setting to help you register the token in other machines

gpg> passwd
Set-up your PIN for the usage of the token, please this is not your 'passphrase' for the GPG private key
The default PIN from the factory is "123456"; your new PIN should not be bigger than 8 characters.
It does not have to be numbers -- the acronym PIN is misleading here.

gpg> forcesig
This will change the default setting of 'signature force PIN' OFF

gpg> login
Register your login name

gpg> help
This is command is your friend, if you want to further customize the token!

gpg> save
This will apply the changes

7. Write your public and private GPG keys to the token

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

gpg> keytocard
This command will *move* your pub GPG key to the token

gpg> toggle
This command changes from pub key to the private key operation

gpg> keytocard
This command will move your private key to the token

gpg> save
This command will save the info to the token and exit the shell

8. Using your keys in other computers with GPG installed

Invoke the GPG shell with this command:
gpg --card-edit

gpg> fetch
This command will retrieve your keys and add it to the local GPG keychain

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> 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:

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

10. Access '/etc/xdg/autostart' and '~/.config/autostart' and add a new entry to the following config files:

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

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

11. Common Issues

* 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 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*.

12. Sources

[1] http://www.seeedstudio.com/wiki/FST-01

[2] http://www.fsij.org/doc-gnuk/

[3] http://no-passwd.net/askbot/questions/scope:all/sort:activity-desc/page:1/

[4] http://keyring.debian.org/creating-key.html

[5] http://www.programmierecke.net/howto/gpg-ssh.html

[6] http://no-passwd.net/askbot/question/51/how-to-deletereplace-the-key-in-gnuk/

[7] https://we.riseup.net/debian/using-the-openpgp-card-with-subkeys

Gnuk

2013-04-24T21:06:31Z

108.85.224.67:

'''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].

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];
- FST-01 USB token with Gnuk pre-installed (click here for alternatives);
- GNU/Linux system (should work on other *nix systems, but not yet tested).

2. Install the following packages:

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

3. Edit your GPG configuration:

Add the following content to your ~/.gnupg/gpg.conf file:

use-agent
personal-digest-preferences SHA256
cert-digest-algo SHA256
default-preference-list SHA512 SHA384 SHA256 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
default-key ADD_YOUR_KEY_ID_HERE

4. In order to use the token, make sure you are running gpg-agent, if not:

Run gpg-agent:
gpg-agent --daemon --enable-ssh-support

5. If you are planning to use the token to authenticate with OpenSSH

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

Add your pub key to the server you want to auth with your GPG token:
ssh ~/.ssh/authorized_keys

6. Personalize your token

To change your personal info, URL where your pub key is, etc., run:
gpg --card-edit

gpg> admin
Allow admin commands to be executed

gpg> name
Register name and surname of the token owner

gpg> url
Address for the location of your public keys, important setting to help you register the token in other machines

gpg> passwd
Set-up your PIN for the usage of the token, please this is not your 'passphrase' for the GPG private key
The default PIN from the factory is "123456"; your new PIN should not be bigger than 8 characters.
It does not have to be numbers -- the acronym PIN is misleading here.

gpg> forcesig
This will change the default setting of 'signature force PIN' OFF

gpg> login
Register your login name

gpg> help
This is command is your friend, if you want to further customize the token!

gpg> save
This will apply the changes

7. Write your public and private GPG keys to the token

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

gpg> keytocard
This command will *move* your pub GPG key to the token

gpg> toggle
This command changes from pub key to the private key operation

gpg> keytocard
This command will move your private key to the token

gpg> save
This command will save the info to the token and exit the shell

8. Using your keys in other computers with GPG installed

Invoke the GPG shell with this command:
gpg --card-edit

gpg> fetch
This command will retrieve your keys and add it to the local GPG keychain

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> 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:

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

10. Access '/etc/xdg/autostart' and '~/.config/autostart' and add a new entry to the following config files:

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

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

11. Common Issues

* 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 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*.

12. Sources

[1] http://www.seeedstudio.com/wiki/FST-01

[2] http://www.fsij.org/doc-gnuk/

[3] http://no-passwd.net/askbot/questions/scope:all/sort:activity-desc/page:1/

[4] http://keyring.debian.org/creating-key.html

[5] http://www.programmierecke.net/howto/gpg-ssh.html

[6] http://no-passwd.net/askbot/question/51/how-to-deletereplace-the-key-in-gnuk/

[7] https://we.riseup.net/debian/using-the-openpgp-card-with-subkeys

User:Unixjazz

2013-03-22T23:41:12Z

108.85.224.67: /* on-going projects */

Hi there! <br>
This is [http://tux.gseis.ucla.edu/ me]

== on-going projects ==

* [https://noisebridge.net/wiki/Bookclub Bookclub]
* Raspbarricade: Portable Live Audio Streamer
* VP8+Webm streaming
* Hacking + Free and Open Source research

== tutorials ==

* Gnuk - GPG crypto USB token

User:Unixjazz

2013-03-22T23:39:45Z

108.85.224.67:

Hi there! <br>
This is [http://tux.gseis.ucla.edu/ me]

== on-going projects ==

* [https://noisebridge.net/wiki/Bookclub Bookclub]
* raspbarricade -- portable live audio streamer
* vp8+webm streaming

== tutorials ==

* Gnuk - GPG crypto USB token

Bookclub

2013-03-13T23:02:05Z

108.85.224.67:

We compile here is a list of books on technology, culture, and politics.

Obsessively compiled list of books by Miah is on [http://www.goodreads.com/group/show/41745.Noisebridge_Book_Club Goodreads].

Noisebridge library can be found here: [http://www.librarything.com/profile/noisebridge LibraryThing]
<br>(at least, 1/3 of the books are listed here)

== Technology and Culture ==

Abbate, Janet. 1999. Inventing the Internet. Cambridge Mass: MIT Press.

Benkler, Yochai. 2011. The Penguin and the Leviathan: How Cooperation Triumphs over Self-Interest. Random House Digital, Inc.

Beyer, Kurt. 2009. Grace Hopper and the Invention of the Information Age. Cambridge Mass.: MIT Press.

Coleman, Gabriella. 2012. Coding Freedom: The Ethics and Aesthetics of Hacking. Princeton University Press.

Ellul, Jacques. 1964. The Technological Society. Jonathan Cape.

Galloway, Alexander R. 2004. Protocol: How Control Exists After Decentralization. MIT Press.

Kelty, Christopher. 2008. Two Bits : the Cultural Significance of Free Software. Durham: Duke University Press.

Levy, Steven. 2001. Crypto: How the Code Rebels Beat the Government--Saving Privacy in the Digital Age. Penguin.

Montfort, Nick, and Ian Bogost. 2009. Racing the Beam: The Atari Video Computer System. MIT Press.

Pasquinelli, Matteo. 2008. Animal Spirits: a Bestiary of the Commons. NAi Publishers.

Reagle, Joseph. 2010. Good Faith Collaboration : the Culture of Wikipedia. Cambridge Mass.: MIT Press.

Salus, Peter. 1994. A Quarter Century of UNIX. Reading Mass.: Addison-Wesley Pub. Co.

Thomas, Douglas. 2002. Hacker Culture. Minneapolis: University of Minnesota Press.

Turner, Fred. 2006. From Counterculture to Cyberculture : Stewart Brand, the Whole Earth Network, and the Rise of Digital Utopianism. Chicago: University of Chicago Press.

Weber, Steve. 2004. The Success of Open Source. Cambridge MA: Harvard University Press.

== Anarchism ==

Bakunin, Mikhail Alexandrovich. 2009. God and the State. Cosimo, Inc.

Bey, Hakim. 2003. T.A.Z. Autonomedia.

Berkman, Alexander. 2011. Life of an Anarchist: The Alexander Berkman Reader. Seven Stories Press.

Bookchin, Murray. 2007. Social Ecology and Communalism. AK Press.

Pateman, Barry. 2010. Chomsky on Anarchism. AK Press.

Guérin, Daniel. 1970. Anarchism; from Theory to Practice. Monthly Review Press.

———. 2005. No Gods, No Masters. AK Press.

Graeber, David. 2009. Direct Action: An Ethnography. AK Press.

Illich, Ivan. 1983. Deschooling Society. Harper & Row.

Kropotkin, Petr Alekseevich. 1910. Mutual Aid: A Factor of Evolution. William Heinemann.

Lafargue, Paul. 1907. The Right to Be Lazy: And Other Studies. C. H. Kerr & company.

Magón, Ricardo Flores, and Charles Bufe. 2005. Dreams of Freedom: A Ricardo Flores Magón Reader. AK Press.

M, P. 2011. Bolo’Bolo. Autonomedia.

Proudhon, Pierre-Joseph. 2011. Property Is Theft!: A Pierre-Joseph Proudhon Reader. AK Press.

Aaron Swartz Memorial Hackathon

2013-01-25T01:30:07Z

108.85.224.67: /* Who's going? */

In memory of [http://en.wikipedia.org/wiki/Aaron_Swartz Aaron Swartz], and in coordination with a [[Worldwide Aaron Swartz Memorial Hackathons|world-wide effort]], Noisebridge will be hosting a hackathon starting '''Friday, January 25th''', and continuing through '''Sunday, January 27th'''.

== Intro ==

Aaron was a hacktivist and friend of many in our community. He helped create RSS 1.0; contributed to Creative Commons; was an early builder of Reddit, where he's often acknowledged as a co-founder; created the [http://webpy.org/ web.py] framework; and more recently, became a data liberator, first with PACER and then with scholarly articles from JSTOR, both of which got him into trouble with the law.

Aaron's [http://demandprogress.org/ Demand Progress] project helped stop SOPA, the Stop Online Piracy Act in the US, which threatened to have far reaching unintended consequences.

Aaron Swartz committed suicide on Jan. 11, 2013, but his work on making the world a better place should not die with him. Join us for two days of understanding his work and contributing to keep his memory and projects alive.

(This section adapted with permission from the [http://hacknight.in/hasgeek/aaronsw-memorial Bangalore hackathon].)

== Event Details ==

'''When''': 7pm Jan. 25 - 7pm Jan. 27

'''What''': Come learn new skills and work together on projects that Aaron would have liked. Themes include open information access, sharing and preserving human knowledge, hacking for social/political justice, and techno-activism.

'''Organizers''': [[user:yan | yan]], [[user:Turkshead | shannon]], [[user:Mct| mct]]

'''Remote collab''': [https://groups.google.com/group/science-liberation-front mailing list]

The event is free, but we'll have donation boxes for purchasing food and project supplies. BYO-snacks-and-energy-drinks.

== Projects ==

There are a bunch of project ideas [https://docs.google.com/spreadsheet/ccc?key=0Ai2JAMm86EJbdFg1TW5tenNJSUt3X2dVVmQ3M08xSlE#gid=1 here]. Most of them need someone to volunteer to be the point of contact.

== Schedule ==

Talks are relatively informal.

Scheduled talks/demos (tentative):

'''Friday'''
*7 pm: Hackathon starts, Yan probably says some words and asks for money
*8 pm: Keynote talk on Aaron's life and work by [https://en.wikipedia.org/wiki/Danny_O'Brien Danny O'Brien]

'''Saturday'''
*4 pm: ''Data hacking: Machine learning + NLP'', [https://twitter.com/turian Joseph Turian]. I will answer questions about machine learning, NLP, scraping, data hacking etc.
*5 pm: ''Hacktivism: On social justice movements'', [http://www.linkedin.com/in/djabbour Daniel Jabbour]. A brief history of social justice movements, and my own experience with policy reform and hacktivism.
*6 pm: ''Principles of Low Power Design'', [http://dolemite.wuli.nu/ Alex Newman]. Hardware you have never heard of for more low power.
*7 pm: ''Improving the Scientific Process through Software'', [http://www.hertzfoundation.org/dx/fellows/fellow_profile.aspx?d=1205 Jacob Steinhardt]. Learn about existing open source projects to improve science, and others that should exist but don't.

'''Sunday'''
*4 pm: ''Towards Open Access in the Sciences'', [https://web.mit.edu/open Yan Zhu]. Why open journal access is important for scientific progress and what we can do to facilitate it.
*5 pm: Closing remarks by Danny O'Brien
*5:15 pm - end: Project demos! Show us what you've worked on this weekend.

'''Unscheduled / Unconfirmed Events'''
*DJ set by [http://www.chromatest.net/ Chromatest J. Pantsmaker]
*Workshop on how to write letters for FOIA requests
*DIY Book Scanner workshop
*Field trip to look for hidden cameras in public places around the Mission

If you'd like to give a talk/workshop, add it to https://docs.google.com/spreadsheet/ccc?key=0Ai2JAMm86EJbdFg1TW5tenNJSUt3X2dVVmQ3M08xSlE#gid=2.

== Who's going? ==

(There's also a [https://www.facebook.com/events/119075571602113/ Facebook Event], if you are so inclined. Sadly, a Facebook login is required to access that page.)

[[user:yan | yan]]

[[user:Turkshead | shannon]]

[[user:Mct| mct]]

[[user:Davidme | davidme]]

[[user:judytuna | judytuna]]

[[user:Lizzard | Liz]]

[[user:zestyping | Ping]]

[[user:gardner | gardner!!]]

[[user:unixjazz | felipe]]