Noisebridge - User contributions [en]

Classrooms

2012-06-10T01:39:41Z

146.185.23.179:

Noisebridge has two future changing rooms.

===Turing===
The Turing room is set up for software development and hacking. It is named after [http://en.wikipedia.org/wiki/Alan_Turing Alan Turing].

===Church===
The Church room is in the back and slightly larger than Turing. It is named after [http://en.wikipedia.org/wiki/Alonzo_Church Alonzo Church].

Intro Poster

2012-03-30T23:00:54Z

146.185.23.179: lmftfy

Soon this will have lots of explanatory text, and then it will get turned into a camera-ready PDF and printed all pretty-like and posted on the wall.

Here's some text I had for an orientation packet, for starters:

<blockquote>
Noisebridge Orientation Packet 
https://noisebridge.net 
2169 Mission St., 3rd floor 
San Francisco, CA 94110-1219 
 
'''Noisebridge''' is a physical space open and welcoming to all, providing infrastructure and collaboration opportunities for anyone interested in programming, hardware, crafts, science, food, robotics, art, and technology. We teach, we learn, we share. With no leaders, we have one rule: "Be excellent to each other". 
 
'''Our Name:''' A "noise bridge" is a piece of electronic test equipment that injects noise into a system to see how it responds, so you can fix or improve it. Such a device is often used in RF electronics. 
 
'''Getting Here:''' Noisebridge is close to the 16th & Mission BART station, and the 14 Mission, 33 Stanyan, and 49 Van Ness-Mission Muni buses. The 22 Fillmore and 12 Folsom Muni buses are within a couple blocks. 
 
'''Do I need to be a member?''' Noisebridge is open to all, however Noisebridge runs off of membership dues and donations. Membership is $80 a month (or a $40 “starving hacker” rate) and allows you to vote at meetings. If you aren’t a member but use the space, please drop off a few dollars in the donation bin, or set up a regular monthly donation for a smaller amount. 
 
'''Meetings''' are every Tuesday at 8pm at the 2169 Mission space. Meetings are mostly for organizational purposes. 
 
Any time is a good time to '''introduce yourself'''. Come on up and have a refreshment, tell others about your interests, or ask people what projects they are working on. 
 
'''Where can I find out more?''' The wiki is at https://www.noisebridge.net. The “Noisebridge-discuss” email list (and other lists) at https://www.noisebridge.net/mailman/listinfo 
 
'''What can I do here?''' Meet techie, arty, and crafty folks, take a class, teach a class, use the power tools and electronic labs, build something out of stuff on the hack shelves, use our library, surf the web, cook up something in the kitchen, and so on. 
 
'''Events, workshops, classes!''' Every week there are lots of activities at Noisebridge, planned and otherwise. Check the wiki for upcoming events, workshops, and classes. And feel free to add your own! 
 
Noisebridge is a fairly '''open and permissive space''', and the equipment (unless otherwise marked, or on a member shelf) is open for public use. Safety first! Feel free to come to Noisebridge to work and play on your project, or help others with theirs. 
 
Noisebridge has '''lots of space''' available as a community resource for individuals and organizations to use -- please use it! 
 
'''Can I leave my stuff here?''' Noisebridge is open to the public, so use your judgment when leaving valuables here. Noisebridge is not responsible for lost or stolen items. Please label your boxes left here with your name, email, and the date. Avoid leaving your bicycle here overnight. 
The daily storage shelves provide a space to leave your things for the day. The lost and found box is located on top of the shelves. 
Members can leave items on their labeled member shelf for an extended period. 
</blockquote>

Keycode Access

2012-02-16T09:33:56Z

146.185.23.179: /* Team */ leak team keycode's alter-egos

==Contact & Info==
Feel free to add yourself here if you plan to work on the project. There will be some email-based discussion and record keeping for this project, and that info will be added here if you just want to lurk and complain.

===Team===
*[https://twitter.com/DBAHULK Hurtstotouchfire]
*[https://twitter.com/DRUNKHULK Tom]
*[https://twitter.com/Real_Hulk Jake]
*[https://twitter.com/securityhulk SuperQ]
*[https://twitter.com/FilmCritHULK Terry]
*[https://twitter.com/feministhulk FEMINIST HULK]

==Keycode System Features==
*Numberpad on front door
*Database of codes... on pony? With notes? Probably we need a basic schema for what info we do and don't want to log.
**Tom wants it to be a text file with a pin or rfid code per line and comments delimited by hash marks
*Logging keycodes (necessary to be able to shut off problem codes)
**keycodes not formally associated with individuals
**member keycodes differentiable in some way
**keep logs for 7 days
**require 2 users to access logs (cryptographically)
*Keycode Generation
*Distribution
**how to distribute without leaving electronic records associating code with individual?
**the most paranoid users will not trust the system anyway
*Disabling keycodes
**presumably not a feature needed immediately.

==Hardware==
There are 3 components to a doorlock system:

# A code entry box (physical hardware)
# Security controller (computer) (we already have minotaur which controls the doorlatch)
# Electronic doorlatch (i.e. buzzer [may be silent])

Commercial door control systems usually have a central controller which is physically located inside the building and cannot be accessed from the entry box. The code entry box is connected to the controller via hard wires (usually serial). The controller can activate the doorlatch via the existing [[Getting In | Noisegate]] relay.

===Potential Products===
*Jake has volunteered to design and make serially-accessed codepads, one for the gate and one for inside.
*[https://www.noisebridge.net/pipermail/noisebridge-discuss/2012-February/028485.html The fucking doorkeypad is finished]

*[http://www.hidglobal.com/prod_detail.php?prod_id=8 HID prox reader] - Supports RS422 and Wiegand
*[http://www.hidglobal.com/prod_detail.php?prod_id=347 HID keypad with 125KHz (prox) + 13.56MHz (iClass)] - Only supports Wiegand

*Will may need a Wiegand interface:
** http://en.wikipedia.org/wiki/Wiegand_interface
** Cost is about $100-150

*Talked to [http://www.sanfordpc.com/ Terry] tonight who says he has a friend who has a bunch of access system gear that we could get donated. linuxman2001@gmail -- [[User:Hurtstotouchfire]]

===Implementation Considerations===
*Should we buy or build the controller?
*Shannon wants to replace the current keypad system with something fancy
*Jake thinks we should just add the keypad onto the gate with U-bolts
**we would need to talk to the landlord to do this (unless we can do it without drilling?)
**at present, we plan to just add an additional keypad and only replace the button system if the keypad is successful