[hackerspaces] RFC: security alarm and access control systems in use

Daniel F buildtherobots at gmail.com
Tue Jun 16 16:01:44 CEST 2015


As much as rfid has inherent security issues, it makes giving people access
easy.

If it's a standard key then you have no idea who is coming in or out.
Getting another set cut is expensive and can be problematic, and if someone
looses their key or stops paying membership then I've got to replace the
locks and 30+ sets of keys.

With rfid, I know who's coming in when, new cards can be added for pennies
and little effort and it's extremely easy to disable a single members
access should it be needed.

Sent from a touchscreen; apologies for typos and berivity.
On 16 Jun 2015 01:47, "Brett Dikeman" <brett.dikeman at gmail.com> wrote:

> A hackerspace I belong to has probably hit the point of needing an alarm
> and access control system. I'm wondering what good solutions have been
> created - what the "state of the art" is in hackerspace security these days.
>
> https://wiki.hackerspaces.org/Doorlock
>
> It'd be awesome if that were updated with any new projects - and if some
> of the existing writeups could be updated or better documented; a number of
> them say "this writeup needs to get updated" or the writeup is super
> sparse. This is a very common and basic need, so more info/guidance would
> be very beneficial. Not just what people have made, but tradeoffs, lessons
> learned, mistakes made, etc.
>
> Also: why do so many of these hackerspace access control systems use RFID
> / proximity cards? Hackerspace people are among the most likely to know how
> laughable security is with them, yet so many hackerspaces use them?
> It's...weird.
>
> -B
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20150616/3adcc7eb/attachment.html>


More information about the Discuss mailing list