3 ms·
Start burning. Destroy all private data, don't store logs, only identify by hashed data. Keep your user's data on your user's devices.
by ransom1538 6y ago
Start burning. Destroy all private data, don't store logs, only identify by hashed data. Keep your user's data on your user's devices.
- pyinstallwoes 6y agoIsn't hashed data based on belief of cryptographic security? I know there's cryptographic hashes and non-cryptographic but given a sophisticated enough state-actor it seems they'd find how to find a key collision. Is there a hashing mechanism/or similar technique that wouldn't be at risk to hash-collision attacks?
- DethNinja 6y agoUse casino dice to generate the entropy, don’t trust the hardware. This is how I handle C-level authority keys in my company. Security is mostly about reducing the feasibility of the attack, there is no way to make your systems 100% secure but you can design it in a way that your 500k USD worth of system requires attacker to spend 5 million USD to breach it.
- pyinstallwoes 6y agoIf you had to have a unique address for every atom in the solar system (I avoided the Universe), what technique would you use? Still hash and casino dice for each one? I'm pretty serious with this question given contemplation of designing a future-inclusive Operating System.
- DethNinja 6y agoIf you really need so many cryptographic keys and won’t trust hardware then you have to build it yourself from commonly available parts and connect it to an offline raspberry pi to take out the automatically generated keys. An example on hand built entropy generator: https://github.com/nategri/chernobyl_dice https://github.com/nategri/chernobyl_dice You can do something like this for I guess 1000 dollars but it won’t be useable for real-time systems.
- pyinstallwoes 6y agoThank you for sharing your knowledge