Hi Simon,
> First off, Thanks for all your ideas!
Your idea inspired me. I’m assuming this is a hobby project, as you probably
gathered.
> The only problems with Kerberos are
> 1) it requires the user to have internet on his phone
There are many ways of bypassing that…
- you could use Blueto
Hi,
First off, Thanks for all your ideas!
The only problems with Kerberos are
1) it requires the user to have internet on his phone
2) the phone must contact the server and obtain tickets every time it wants
to lock/unlock the door which adds delay (not sure how much). A solution
would be to have
Hello again,
I had a few more thoughts on this idea of yours to use Kerberos for
your door locks:
* When you apply cross-realm tactics (which we are working on for
Kerberos, http://realm-xover.arpa2.net/kerberos.html ) you have an
identification of your visitors, even when they are granted access
I think this is brilliant, especially if you separate 'who you are' from
'which lock do you have access to' with LDAP, and then you can just point
your door lock at your home 'data furnace' Microsoft Active Directory
server if you want to make it easy for home users, or to a cloud service,
or if y
Hi all,
I’m working on a electronics project to lock and unlock my door via my
phone (with Bluetooth). It works well but it’s unsafe since I just send the
lock and unlock command in cleartext, without authentication or encryption.
I would like to add authentication to this so that only I can enter
Hi Simon,
First off, Kerberos-enabled front doors sound really cool to me.
It would be a lovely showcase of the protocol, and although it’s
not mainstream thinking it may turn out to be a genius idea.
But you and your visitors would need to setup a KDC link, get a
TGT and then a service ticket.
