[Noisebridge-discuss] RFID, TransLink/Clipper

Ian Atha thatha at thatha.org
Thu May 20 05:43:16 UTC 2010


If you can get it to read the encrypted payload and you know where the
encrypted ID starts and where it ends, chances are it's good enough
for identification purposes. That you can't decipher the ID is
irrelevant--you only need to associate the garbled data with a
positive identification.

On Wed, May 19, 2010 at 22:17, Jeffrey Malone <ieatlint at tehinterweb.com> wrote:
> On Wed, May 19, 2010 at 10:09 PM, Daniel Farina <drfarina at acm.org> wrote:
>> For example, would it make any sense to make a translink-card driven
>> door-(un)locking infrastructure? Or is that a silly idea?
>
> I thought about doing that for Noisebridge at one point, before I knew
> it worked on a 35mhz band.
> The way the card works, it is likely to have a publicly readable ATR
> -- sort of a provisioning number.  All the cards would have the same
> ATR, but it would identify them as translink cards.  The unique id
> should be encrypted like the rest of the data (if not, then seriously
> shame on them -- that would be a terrible security hole).
>
> So sadly, it is not too realistic to do a door lock using the
> translink cards.  I am still vaguely tempted to set something up
> though.  The bart ez rider cards use 13.5mhz, and so do many others
> (oyster cards, for instance, and I think Boston's charlie cards).
> Additionally, mifare cards cost ~$1, and can be purchased as small
> keychains.
> I have a 13.5mhz/125khz reader sitting around if you want to fuck with
> it though.  Let me know..
>
> Jeffrey
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>



More information about the Noisebridge-discuss mailing list