|
|
|
|
|
by rektide
1481 days ago
|
|
I like the point here a lot. The exploration. Even if I disagree a bit about option #2 (giving keys short-term to servers) being a good way to do things. Being able to browse on the web & also have encrypted files is an interesting challenge. The option #2 here, of sending the key to the server but making it short lived, is hopeful. Ideally though, I guess I'd hope that the server would just send me a bunch of encrypted metadata, let my client decode it & browse the file tree, then requested encrypted chunks as it wanted. The Option #1, making the server oblivious, feels much better. Rather than trusting that the server will delete my key eventually. And #1 should allow #2 like systems... we should be able to make separate apps, apart from the storage system, that can intermediate, if we need to. |
|