Keycode Access: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
(adding notes from policy wonks discussion of access)
(Update URL for mailing list post about keypad being done)
 
(37 intermediate revisions by 18 users not shown)
Line 4: Line 4:
===Team===
===Team===
*[[User:Hurtstotouchfire|Hurtstotouchfire]]
*[[User:Hurtstotouchfire|Hurtstotouchfire]]
*[[User:Flamsmark|Tom]]
*[[User:Jake|Jake]]


==Keycode System Features==
==Keycode System Features==
*Numberpad on front door
*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.
*Database of codes... on pony? With notes? Probably we need a basic schema for what info we do and don't want to log.
*Logging keycodes
**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
**keycodes not formally associated with individuals
**member keycodes differentiable in some way
**member keycodes differentiable in some way
Line 16: Line 19:
*Distribution
*Distribution
**how to distribute without leaving electronic records associating code with individual?
**how to distribute without leaving electronic records associating code with individual?
**the most paranoid users will not trust the system anyway
*Disabling keycodes
*Disabling keycodes
**presumably not a feature needed immediately.
**presumably not a feature needed immediately.
Line 23: Line 27:


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


Line 29: Line 33:


===Potential Products===
===Potential Products===
*[http://www.hidglobal.com/prod_detail.php?prod_id=8 HID prox reader]
*Jake has volunteered to design and make serially-accessed codepads, one for the gate and one for inside.
*[https://web.archive.org/web/20150912061659/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===
===Implementation Considerations===
*Should we buy or build the controller?
*Shannon wants to replace the current keypad system with something fancy
*Shannon wants to replace the current keypad system with something fancy
**we would need to talk to the landlord to do this
*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
**at present, we plan to just add an additional keypad and only replace the button system if the keypad is successful

Latest revision as of 20:11, 30 September 2023

Contact & Info[edit]

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[edit]

Keycode System Features[edit]

  • 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[edit]

There are 3 components to a doorlock system:

  1. A code entry box (physical hardware)
  2. Security controller (computer) (we already have minotaur which controls the doorlatch)
  3. 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 Noisegate relay.

Potential Products[edit]

  • Talked to 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[edit]

  • 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