OK, so the first part demonstrates that given a password, OpenSSL generates the symmetric keypair using MD5 and a salt. So what? That doesn't break AES since th

OK, so the first part demonstrates that given a password, OpenSSL generates the symmetric keypair using MD5 and a salt. So what? That doesn't break AES since the only secret thing in the system should be the password/key. The issue is that the entropy of the key is actually half what it is supposed to be. The second half of the key is derivable from the first half. OK, that's pretty bad but still not entirely broken. Next: padding oracle attack in OpenSSL. Reported on https://blog.cloudflare.com/yet-another-padding-oracle-in-openssl-cbc-ciphersuites/ https://blog.cloudflare.com/yet-another-padding-oracle-in-op... Looks like it is fixed now. There are various complaints about memory management, double free errors and "sloppy" programming. It isn't clear to me that these have any further security implications but I am by no means an expert. The last part talks about information being leaked when an attempt is made to decrypt using AES with a bad password. It isn't clear - neither to me nor to the author - that this information has any utility in narrowing down the search space for the key.