full-disclosure - Re: [FD] Master Lock random key code generation/distribution Fails

Open Source and information security mailing list archives

Date: Thu, 27 Mar 2014 12:41:19 -0400
From: Deviant Ollam <deviant@...iating.net>
To: fulldisclosure@...lists.org
Subject: Re: [FD] Master Lock random key code generation/distribution Fails

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There are a variety of security concerns with the Smart Key system,
addressed by Shane Lawson (valanx) in some con talks at ShmooCon and
elsewhere.  Also documented in (self-citation alert) my second book.

If the list supports attached photos i could drop in some documentation
of all of this... but instead i might just pop them up on a web gallery
and link to them in a future email this weekend.

- - dev

On 2014-03-26 22:26, Jeff Kell wrote:
> On 3/26/2014 6:38 PM, Richard Chycoski wrote:
>> For my current house I keyed it differently. There is a master key
>> that opens everything. There is a front-door-outside key that only
>> opens that one lock, so that if someone (read - some kid :-) ) loses
>> that key I only have one lock to change.
> 
> I got the Kwikset Smartkey locks last time around.  You can "re-key"
> them on the fly as long as you still have an original key, and the
> replacement key you want to use in the future.
> 
> Jeff
> 
> 
> _______________________________________________
> Sent through the Full Disclosure mailing list
> http://nmap.org/mailman/listinfo/fulldisclosure
> Web Archives & RSS: http://seclists.org/fulldisclosure/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJTNFSvAAoJEN75XzxIvP0oBWMP/iwEHtYQkfHyRIm+JReRxva7
iKiH6rSbIE6X9Z2LLCgSARHvUmsEnEgn6hvHFX3lGO7Bh8wXk8ORHgOXJHmG1ZY2
ZBTZfexDD8RIcCpatTsdBrkatbbRhhAl4yEzyTKelXz3gjVgG/oxXWaRYmc0NqG8
SGLVvz8QIF07EQwG3Q/Nr0Ne/SzXIIHvkgxww+YvT34q+fpU3XpxVrqkRBpvpeX8
wD5DNJZaPJDGV4LpNVvF+fwBpR5MfStDn+6f442WNDG4RjSuItXYq67zn3XvlwZZ
1dC0JEwFTnxYL7c0+CUd1ZQryhgFKYTq6MdZqanI8XWPkqLGnH+SZDM1kyfP3fRH
0ekOFe620dxSWif0j9zr9FNrsY2Y9CG2hIAevbMXjMpbuh3Z1c7mJsB56FENqt5J
uh6uGrOU9H30HxQq8njvtsKssoaeVCletvXRrPz35bmObjPjrIUpUc6FRhuIgUTV
tee0oqlHp8uI7iFBAjp4ZgnKuZMxdWtAgKAdy3aeKye5jmBdwQ5nGLNYHE/09vBb
w4ngoO+eEJ9MK6iPKkIDfOY6zdKIpID3EqfSyKd1PXk3nLLJhTx5ZyC8BI1c3uDD
sVCnwIuiln8JYYM0RA+7no7eNSJqBnwtn9klEzwenQ/j/cXCmv5ca7coWymMN+bO
l9r2XY4AcGCjzXHuc9Ll
=TTxU
-----END PGP SIGNATURE-----

_______________________________________________
Sent through the Full Disclosure mailing list
http://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives