I know this has popped up at different times, but I'd like to put it forward for discussion again.
There's a lot of value to be gained in a new keytype, a kind of 'reverse SSK'. Perhaps call this keytype 'PAK' - Privately Accessible Key. In other words: 1) Generate a public/private keypair 2) Trivial to convert the private key into a public key, but no way to convert public to private except by brute force against extreme orders of execution. 3) Insert under the pubkey - easy. 4) Requests using the pubkey fail - no data found 5) Requests using the privkey succeed - plain data comes back I still know stuff-all about the node internals, but I could envisage anything inserted under the pubkey being stored, heavily encrypted, under a CHK. The PAK could be an SSK variant. PAK at pubkey physically contains a redirect to this CHK. Upon request, the node converts PVK at privkey to PAK at pubkey to retrieve the key, then the privkey is used to decrypt the data. Uses? Secure email. Secure payments. And many more. Thoughts anyone? David -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20011006/47627a71/attachment.html>
