Semi-Private Keys
[Imported from Trac: page GSoCIdeas2010, version 38]
parent
1c2bd0c821
commit
0d37bb719c
|
@ -21,7 +21,8 @@
|
||||||
* HTTP proxy approach
|
* HTTP proxy approach
|
||||||
* Special scheme handling in browser add-ons
|
* Special scheme handling in browser add-ons
|
||||||
* [CAJA](http://code.google.com/p/google-caja) approach: Require all Javascript to pass the CAJA verifier in the Tahoe web frontend, then create an interface to the tahoe webapi which matches the intended capability semantics.
|
* [CAJA](http://code.google.com/p/google-caja) approach: Require all Javascript to pass the CAJA verifier in the Tahoe web frontend, then create an interface to the tahoe webapi which matches the intended capability semantics.
|
||||||
* Tahoe Cryptography Fu (Zooko: add specific projects here)
|
* Tahoe Cryptography:
|
||||||
|
* Write a paper proving the security of the "Semi-Private Keys" construction from <http://allmydata.org/~zooko/lafs.pdf> . Implement small, secure Tahoe capabilities based on Semi-Private Keys.
|
||||||
|
|
||||||
## Building Things On Top Of Tahoe
|
## Building Things On Top Of Tahoe
|
||||||
* an interactive tree browser web frontend in JavaScript (Nathan has written most of one -- what can it grow into?)
|
* an interactive tree browser web frontend in JavaScript (Nathan has written most of one -- what can it grow into?)
|
||||||
|
|
Loading…
Reference in a new issue