| ▲ | Sopel 4 hours ago | |||||||||||||
you're not gonna brute force an AES256 key if you have a bad password that's a user issue | ||||||||||||||
| ▲ | gruez 4 hours ago | parent | next [-] | |||||||||||||
You're not gonna remember a AES256 key either (or at least not many of them), not to mention the ergonomics associated with entering a AES256 key. The whole point of security chips like google's titan m2 or apple's secure enclave is to strengthen weak passwords (eg. 6 digit pins) so they offer comparable security to 256 bit keys, without having to enter 256 bit keys. | ||||||||||||||
| ||||||||||||||
| ▲ | SV_BubbleTime 4 hours ago | parent | prev | next [-] | |||||||||||||
>you're not gonna brute force an AES256 key There was a great article around last week about PDFs using randomly generated keys that ended up using non-secure random number generators and the effect was the only unique portion of the key is was 9bits, and obviously forceable. I wouldn’t even describe this between burrito bites activity as “brute”. The point being “AES” doesn’t mean secure. Secure through the whole implementation means secure. People fuck up crypto all day, calling out a specific cipher doesn’t mean much. | ||||||||||||||
| ▲ | 4 hours ago | parent | prev [-] | |||||||||||||
| [deleted] | ||||||||||||||