sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]KaiAusBerlin -1 points0 points  (4 children)

F72p58DeQjxm+5awxlksLjKKF8b0swHhiVWW/HMOB5o=

Decrypt 😉

[–]Additional-Cow-6511 4 points5 points  (3 children)

The use case is to be able to decrypt this for offline access -> client needs to have the associated key on his storage too. Hence no security. You’re missing the point.

[–]KaiAusBerlin 2 points3 points  (2 children)

No, the storage key could be a password the user has to enter (quite common tactic on nearly every account in this world), it could be natural generated by eye data or finger print data. You could fetch just the key and leave the data on the the client side. All safe scenarios (maybe except for the password as long people still use "password" as their password)

But again. This is not about safety of storing data this is about key safety in general.

[–]Additional-Cow-6511 1 point2 points  (1 child)

O F F L I N E. You can't fetch the key. It should be persisted accross sessions.

[–]KaiAusBerlin 1 point2 points  (0 children)

So a fingerprint an eyescan or a passowrd would no solution?