1994-07-26 - Hotel locks (was:Radio-activated locks, RESCUE…)

Header Data

From: baum@apple.com (Allen J. Baum)
To: cypherpunks@toad.com
Message Hash: 18bf6f184106d8d45c6ab79a525a7678e255efd55f9773a4ffe737306789a0cc
Message ID: <9407261643.AA12460@newton.apple.com>
Reply To: N/A
UTC Datetime: 1994-07-26 16:44:24 UTC
Raw Date: Tue, 26 Jul 94 09:44:24 PDT

Raw message

From: baum@apple.com (Allen J. Baum)
Date: Tue, 26 Jul 94 09:44:24 PDT
To: cypherpunks@toad.com
Subject: Hotel locks (was:Radio-activated locks, RESCUE...)
Message-ID: <9407261643.AA12460@newton.apple.com>
MIME-Version: 1.0
Content-Type: text/plain


> I understand the
>electronic lock folks (card locks, hotels, etc.) have crypto expertise
>of varying extents (and bluntly, probably more than most of us have)
>and they certainly have the expertise in other areas.

I've been told that the way that hotel locks work is simple LFSR type
technology.

The chip recognizes some key pattern, and generates a sucessor key.
If a card is inserted that doesn't match the primary key, it checks the
sucessor key. If that matches, the successor becomes the primary, and a new
successor is generated.

The machine at the front desk knows where in the sequence the a particular
lock is, and simply generates a sucessor whenever a new key is asked for.
So, there doesn't need to be any communication between the desk and the
lock when a new key is generated. Note that after you get a new key, the
old one will still work until the new key is used.

Note that there is more than one primary key; there are 'master' keys for
the staff, and presumably that can be used to reset the key if the sequence
gets
lost. Of course, who knows what happens if the master sequence get lost to
a battery burp- maybe a separate ID number/lock? (as opposed to the huge
back door of a permanent, single, masterkey...)

Clever little system, yes?

**************************************************
* Allen J. Baum              tel. (408)974-3385  *
* Apple Computer, MS/305-3B                      *
* 1 Infinite Loop                                *
* Cupertino, CA 95014        baum@apple.com      *
**************************************************







Thread