Keycode Access

From Noisebridge
(Difference between revisions)
Jump to: navigation, search
(moving to access control page)
(adding notes from policy wonks discussion of access)
Line 8: Line 8:
 
*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.
**Door usage logged by keycode
+
*Logging keycodes
 
**keycodes not formally associated with individuals
 
**keycodes not formally associated with individuals
***how to distribute without leaving electronic records associating code with individual?
 
 
**member keycodes differentiable in some way
 
**member keycodes differentiable in some way
*Method of keycode generation?
+
**keep logs for 7 days
*Method of keycode disabling?
+
**require 2 users to access logs (cryptographically)
 +
*Keycode Generation
 +
*Distribution
 +
**how to distribute without leaving electronic records associating code with individual?
 +
*Disabling keycodes
 
**presumably not a feature needed immediately.
 
**presumably not a feature needed immediately.
  
 
==Hardware==
 
==Hardware==
 +
There are 3 components to a doorlock system:
 +
 +
# A code entry box (physical hardware)
 +
# Security controller (computer)
 +
# 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===
 +
*[http://www.hidglobal.com/prod_detail.php?prod_id=8 HID prox reader]
 +
 +
===Implementation Considerations===
 +
*Shannon wants to replace the current keypad system with something fancy
 +
**we would need to talk to the landlord to do this
 +
**at present, we plan to just add an additional keypad and only replace the button system if the keypad is successful

Revision as of 20:00, 11 February 2012

Contents

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

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.
  • Logging keycodes
    • 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?
  • Disabling keycodes
    • presumably not a feature needed immediately.

Hardware

There are 3 components to a doorlock system:

  1. A code entry box (physical hardware)
  2. Security controller (computer)
  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

Implementation Considerations

  • Shannon wants to replace the current keypad system with something fancy
    • we would need to talk to the landlord to do this
    • at present, we plan to just add an additional keypad and only replace the button system if the keypad is successful
Personal tools