<div dir="ltr">Don't forget to look into legal requirements when building or installing an access control system. If your space needs a Certificate of Occupancy you may have to meet legal requirements ( like UL listings, failsafe, etc etc etc).<div><br>It can be fun to roll your own, but consult with lawyers (or your insurance company) if need be.....</div><div><br></div><div>I am not a lawyer. Just offering a word of advice.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 16, 2015 at 1:31 PM, Arclight <span dir="ltr"><<a href="mailto:arclight@gmail.com" target="_blank">arclight@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">One of the issues with improving the hackerspace security stack is<br>
getting everything into a restful APIU. What is everyone doing for<br>
serial interfacing? Has anyone thought about using GPSD or another<br>
high-quality serial daemon's code as a bidrectional, event-driven<br>
serial handler?<br>
<span class="HOEnZb"><font color="#888888"><br>
Arclight<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Tue, Jun 16, 2015 at 10:20 AM, Jens <<a href="mailto:a.madman@gmail.com">a.madman@gmail.com</a>> wrote:<br>
> At MakeICT in Kansas, our makers/hackers built an RFID system that runs on a<br>
> Raspberry Pi and syncs with our member management software, Wild Apricot.<br>
> We have been pleased with it's capabilities and recently connected it to the<br>
> alarm system at our facility.<br>
><br>
> <a href="http://makeict.org/wiki/index.php/Electronic_Door_Entry" rel="noreferrer" target="_blank">http://makeict.org/wiki/index.php/Electronic_Door_Entry</a><br>
><br>
> (Can't edit the Wiki for some reason, sorry)<br>
><br>
> Jens<br>
> Treasurer, MakeICT<br>
><br>
> On Mon, Jun 15, 2015 at 7:47 PM, Brett Dikeman <<a href="mailto:brett.dikeman@gmail.com">brett.dikeman@gmail.com</a>><br>
> wrote:<br>
>><br>
>> A hackerspace I belong to has probably hit the point of needing an alarm<br>
>> and access control system. I'm wondering what good solutions have been<br>
>> created - what the "state of the art" is in hackerspace security these days.<br>
>><br>
>> <a href="https://wiki.hackerspaces.org/Doorlock" rel="noreferrer" target="_blank">https://wiki.hackerspaces.org/Doorlock</a><br>
>><br>
>> It'd be awesome if that were updated with any new projects - and if some<br>
>> of the existing writeups could be updated or better documented; a number of<br>
>> them say "this writeup needs to get updated" or the writeup is super sparse.<br>
>> This is a very common and basic need, so more info/guidance would be very<br>
>> beneficial. Not just what people have made, but tradeoffs, lessons learned,<br>
>> mistakes made, etc.<br>
>><br>
>> Also: why do so many of these hackerspace access control systems use RFID<br>
>> / proximity cards? Hackerspace people are among the most likely to know how<br>
>> laughable security is with them, yet so many hackerspaces use them?<br>
>> It's...weird.<br>
>><br>
>> -B<br>
>><br>
>> _______________________________________________<br>
>> Discuss mailing list<br>
>> <a href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a><br>
>> <a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a><br>
> <a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
><br>
_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br></div>