Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Hacker Dojo's Open-Sourced Implementation

Received: by 10.14.14.162 with SMTP id d34mr74451eed.2.1291966486508;
        Thu, 09 Dec 2010 23:34:46 -0800 (PST)
X-BeenThere: opendoorhack-a-thon@googlegroups.com
Received: by 10.14.24.73 with SMTP id w49ls244154eew.4.p; Thu, 09 Dec 2010
 23:34:45 -0800 (PST)
Received: by 10.14.37.138 with SMTP id y10mr94317eea.4.1291966485606;
        Thu, 09 Dec 2010 23:34:45 -0800 (PST)
Received: by 10.14.37.138 with SMTP id y10mr94316eea.4.1291966485579;
        Thu, 09 Dec 2010 23:34:45 -0800 (PST)
Return-Path: <katylevin...@gmail.com>
Received: from mail-ey0-f178.google.com (mail-ey0-f178.google.com [209.85.215.178])
        by gmr-mx.google.com with ESMTP id t6si908210eeh.4.2010.12.09.23.34.44;
        Thu, 09 Dec 2010 23:34:44 -0800 (PST)
Received-SPF: pass (google.com: domain of katylevin...@gmail.com designates 209.85.215.178 as permitted sender) client-ip=209.85.215.178;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of katylevin...@gmail.com designates 209.85.215.178 as permitted sender) smtp.mail=katylevin...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by eyh5 with SMTP id 5so2316700eyh.23
        for <opendoorhack-a-thon@googlegroups.com>; Thu, 09 Dec 2010 23:34:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:date:message-id
         :subject:from:to:content-type;
        bh=Uy9EFKtYj2+YXgRDtcavV+Hc2yIjAzmVE0gF9JClCmw=;
        b=VMdIzZsAUEoQvdqCECvCJKhEQs0g4dRZalMTD5KJJmzslVO0H6+YBVprstM29F92Lj
         6F1m5qF14z+w7EJA3tRl/GRPHk1nq0mKZk2VvuVbnObDJICCTCSdemhzsu4yqOAr9gCF
         tigRpcLFRNAN9WzbPisg56/WfjEuvI2Uo4T+w=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=o60GrmbIbVk2Fcu/fqVcYpDL7fB13/uFzgthcs/Iz/fCkCxpFb07E8QMKnnrXAjhVy
         RD4WnIferB3Z0t4J0QJfddC1PY94jEjTxF8yuk7amIUkNRuQz5El7u5ahZtuIP9Ao30X
         rUHoorT65Z+ImyP6kKQFM0qlMbvEdsllE2IgE=
MIME-Version: 1.0
Received: by 10.14.127.206 with SMTP id d54mr395454eei.49.1291966484376; Thu,
 09 Dec 2010 23:34:44 -0800 (PST)
Received: by 10.14.48.16 with HTTP; Thu, 9 Dec 2010 23:34:44 -0800 (PST)
Date: Thu, 9 Dec 2010 23:34:44 -0800
Message-ID: <AANLkTinv0N7-MKXFBfRkdi0kWWd5Fn=3YPP3-U+mT...@mail.gmail.com>
Subject: Hacker Dojo's Open-Sourced Implementation
From: Katy Levinson <katylevin...@gmail.com>
To: opendoorhack-a-thon@googlegroups.com
Content-Type: multipart/alternative; boundary=90e6ba6151805cee4c0497096351

--90e6ba6151805cee4c0497096351
Content-Type: text/plain; charset=ISO-8859-1

Hey everybody,

I know everybody's really excited about making their own thing, but here is
Hacker Dojo's open-sourced implemented solution to this problem. We've been
running it for a few months now, and it has been working pretty well.  I
figured I'd throw it out there.

Here's a writeup of the bill of parts and shows the schematics
http://katylevinson.com/blog/?p=7

Here's the code we use to run the maglock computer
https://github.com/hackerdojo/hd-maglock

Here's the code which handles signup, billing, and RFID assignment and
tracking https://github.com/hackerdojo/hd-signup, it also controls which
users have rights to RFID keys and which do not.

The relevant interfaces are as follows: the RFID reader is a simple USB
keyboard input, and the relay which controls the door is set by the
ready-to-send pin on an RS232 controller, schematic is included.  The
computer pulls the authorised membership list from the server via JSON.  The
membership accounts are just Google accounts for the @hackerdojo.com domain,
so we piggyback on all their security/user managament/administration
systems.  System tolerates network outages (of course new members authorised
while the network outage is going on won't be admitted), and tolerates a
building power failure of about 6 hours before intentionally failing open.
Emergency open button is a hard break, no computer in the loop, for fire
safety.  Entire system costs about $250 USD to make, and keys are about 60
cents.  System can be installed in a weekend.

We are excited to see what you all come up with, but I figured I would throw
this into the ring to let other teams look it over.  We really would
appreciate your feedback (or better yet, code patches!)

Thanks,
Katy

PS: This system also works with our login system,
http://www.youtube.com/watch?v=KPRKC8VD9K0 which you can have too
https://github.com/hackerdojo/hd-signin  As a matter of fact, feel free to
take all our code, use it in your space, and submit many many bug patches
https://github.com/hackerdojo/

--90e6ba6151805cee4c0497096351
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey everybody,<br><br>I know everybody&#39;s really excited about making th=
eir own thing, but here is Hacker Dojo&#39;s open-sourced implemented solut=
ion to this problem. We&#39;ve been running it for a few months now, and it=
 has been working pretty well.=A0 I figured I&#39;d throw it out there.<br>
<br>Here&#39;s a writeup of the bill of parts and shows the schematics <a h=
ref=3D"http://katylevinson.com/blog/?p=3D7">http://katylevinson.com/blog/?p=
=3D7</a><br><br>Here&#39;s the code we use to run the maglock computer <a h=
ref=3D"https://github.com/hackerdojo/hd-maglock">https://github.com/hackerd=
ojo/hd-maglock</a><br>
<br>Here&#39;s the code which handles signup, billing, and RFID assignment =
and tracking <a href=3D"https://github.com/hackerdojo/hd-signup">https://gi=
thub.com/hackerdojo/hd-signup</a>, it also controls which users have rights=
 to RFID keys and which do not.<br>
<br>The relevant interfaces are as follows: the RFID reader is a simple USB=
 keyboard input, and the relay which controls the door is set by the ready-=
to-send pin on an RS232 controller, schematic is included.=A0 The computer =
pulls the authorised membership list from the server via JSON.=A0 The membe=
rship accounts are just Google accounts for the @<a href=3D"http://hackerdo=
jo.com">hackerdojo.com</a> domain, so we piggyback on all their security/us=
er managament/administration systems.=A0 System tolerates network outages (=
of course new members authorised while the network outage is going on won&#=
39;t be admitted), and tolerates a building power failure of about 6 hours =
before intentionally failing open.=A0 Emergency open button is a hard break=
, no computer in the loop, for fire safety.=A0 Entire system costs about $2=
50 USD to make, and keys are about 60 cents.=A0 System can be installed in =
a weekend.<br>
<br>We are excited to see what you all come up with, but I figured I would =
throw this into the ring to let other teams look it over.=A0 We really woul=
d appreciate your feedback (or better yet, code patches!)<br><br>Thanks,<br=
>
Katy<br><br>PS: This system also works with our login system, <a href=3D"ht=
tp://www.youtube.com/watch?v=3DKPRKC8VD9K0">http://www.youtube.com/watch?v=
=3DKPRKC8VD9K0</a> which you can have too <a href=3D"https://github.com/hac=
kerdojo/hd-signin">https://github.com/hackerdojo/hd-signin</a>=A0 As a matt=
er of fact, feel free to take all our code, use it in your space, and submi=
t many many bug patches <a href=3D"https://github.com/hackerdojo/">https://=
github.com/hackerdojo/</a><br>

--90e6ba6151805cee4c0497096351--