1
$\begingroup$

Using web crypto API and it won't let me store an AES key in the indexeddb (it requires a public/private key).

Does anyone have suggestions on how to do this? Should I/could I create a public/private key, store it in the indexeddb and use it to secure the AES key?

The idea is to have shared workspaces for messages and documents, all encrypted with AES. The AES key is generated client side by the person creating the workspace and then distributed to each member. The server should never be able to access the key (needs to be zero knowledge).

$\endgroup$
  • $\begingroup$ E2EE - don't want the server (or db ) knowing anything about the key. The key is generated client side, then secured , stored and then has to be shared with every other member in the workspace so they can encrypt/decrypt. $\endgroup$ – kaboom Feb 19 at 15:43
  • $\begingroup$ Why don't you use existing solutions like sparkleshare $\endgroup$ – kelalaka Feb 19 at 16:25
  • $\begingroup$ because this is way more than just a file share. The product already exists but we're just moving from server side to client side encryption and looking for the most secure implementation. thanks $\endgroup$ – kaboom Feb 19 at 17:01
  • $\begingroup$ Is it unique AES key for each document or there is only one AES key? $\endgroup$ – kelalaka Feb 19 at 17:51
  • $\begingroup$ One key per channel, multiple conversations and documents in the channel. We have all this part working - it's encrypting/decrypting on the client - just trying to figure out the best way to secure the AES key in the browser. $\endgroup$ – kaboom Feb 19 at 18:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.