temporary link to broken klog
[Imported from Trac: page OneHundredYearCryptography, version 23]
parent
ca00ecca17
commit
da2d859bde
|
@ -1,6 +1,6 @@
|
||||||
See also [NewCapDesign](NewCapDesign) and [Bibliography](Bibliography).
|
See also [NewCapDesign](NewCapDesign) and [Bibliography](Bibliography).
|
||||||
|
|
||||||
This describes a project to enhance Tahoe-LAFS's cryptographic system so that Tahoe shipped today/next year might remain safe from cryptographic attacks for a 100 years. The initial ideas were presented on a [post by Zooko on his klog](https://lafsgateway.zooko.com/uri/URI%3ADIR2-RO%3Ad73ap7mtjvv7y6qsmmwqwai4ii%3Atq5tqejzulg7yj4h7nxuurpiuuz5jsgvczmdamcalpk2rc6gmbsq/klog.html)#[[can%20we%20build%20a%20crypto%20system%20to%20last%20for%20a%20hundred%20years%3F%5D%5D.
|
This describes a project to enhance Tahoe-LAFS's cryptographic system so that Tahoe shipped today/next year might remain safe from cryptographic attacks for a 100 years. The initial ideas were presented on a [post by Zooko on his klog](https://tahoe-lafs.org/~zooko/backup_of_klog/blog.html)#[[can%20we%20build%20a%20crypto%20system%20to%20last%20for%20a%20hundred%20years%3F%5D%5D.
|
||||||
|
|
||||||
One idea is to combine two primitives, both thought to be safe, such that even if one of them fails catastrophically Tahoe-LAFS remains secure.
|
One idea is to combine two primitives, both thought to be safe, such that even if one of them fails catastrophically Tahoe-LAFS remains secure.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue