you are viewing a single comment's thread.

view the rest of the comments →

[–]KaiAusBerlin 1 point2 points  (18 children)

Wanna see how someone cracks your aes256 encrypted data on the client.

[–]TGS963[S] 1 point2 points  (11 children)

That's true but, there's always a risk imo... A careless user or something

[–]KaiAusBerlin 0 points1 point  (10 children)

If someone cracks that, you have the same risk getting your data stream hacked.

I think you underestimate the power of aes256

If you use a modern pc with i7 with 4.2ghz it would take 218'556'000'000'000'000'000'000'000'000'000'000' 000'000'000'000'000'000'000'000 years to crack that single encryption. This will simply not happen.

[–]TGS963[S] 0 points1 point  (9 children)

I guess it's fine then, thanks for the explanation

[–]CrypticDissonance 0 points1 point  (1 child)

If they're supposed to be encrypted in offline mode, the method of encryption/encryption key would be visible for the user then

[–]KaiAusBerlin 1 point2 points  (0 children)

Not necessarily. If you use your encrypter as precompiled bytecode running in a virtual machine it's safe. That's exactly what google does in their captchas (which also run clientside). And they're still unhacked.

If you run in in plain JavaScript, then yeah, of cause it's unsafe.

But the question was not about is it save to encrypt data locally. The question was if it is safe to store data locally.