Check out my first novel, midnight's simulacra!
Lamport's Hash: Difference between revisions
From dankwiki
No edit summary |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
<blockquote>"Without public key cryptography, it's difficult to protect against both eavesdropping and server database reading with a single protocol, although is is easy to do one or another...an elegant protocol by [http://research.microsoft.com/users/lamport/ Leslie Lamport] can claim to accomplish this feat."</blockquote> | <blockquote>"Without public key cryptography, it's difficult to protect against both eavesdropping and server database reading with a single protocol, although is is easy to do one or another...an elegant protocol by [http://research.microsoft.com/users/lamport/ Leslie Lamport] can claim to accomplish this feat."</blockquote> | ||
[http://research.microsoft.com/users/lamport/pubs/password.pdf Published in 1981], implemented as S/KEY by [http://citeseer.ist.psu.edu/cache/papers/cs/5967/ftp:zSzzSzftp.mcc.ac.ukzSzpubzSzsecurityzSzPAPERSzSzPASSWORDzSzSKEY.pdf/haller94skey.pdf Haller et al in 1994], and standardized as RFC 1938 in 05-1996. | [http://research.microsoft.com/users/lamport/pubs/password.pdf Published in 1981], implemented as S/KEY by [http://citeseer.ist.psu.edu/cache/papers/cs/5967/ftp:zSzzSzftp.mcc.ac.ukzSzpubzSzsecurityzSzPAPERSzSzPASSWORDzSzSKEY.pdf/haller94skey.pdf Haller et al in 1994], and standardized as RFC 1938 in 05-1996. | ||
[[Category:Leslie Lamport Eponyms]] | |||
[[Category:Computer Science Eponyms]] | |||
Latest revision as of 23:39, 18 August 2009
From Network Security: Private Communication in a Public World 2nd Edition, p225:
"Without public key cryptography, it's difficult to protect against both eavesdropping and server database reading with a single protocol, although is is easy to do one or another...an elegant protocol by Leslie Lamport can claim to accomplish this feat."
Published in 1981, implemented as S/KEY by Haller et al in 1994, and standardized as RFC 1938 in 05-1996.
