PSA: Do not reply to monero_badcaca’s admittedly abusive spamming of lengthy nonsense lists here. Just report them, as I already did before I saw this on his thread:
Full, unedited quote for reference:
I'm posting the daily report in Monero topic until they start moderating it.
I also observe that he is multi-posting. (And if he keeps up this arrant nonsense, I will start reporting it as a troll instead of replying.)
Yes it is, Monero community members have a tendency to spew uneducated bullshit. https://link.springer.com/chapter/10.1007%2F978-3-319-19962-7_3
I hope those defamatory remarks made you feel better, because they didn't make the IP leak go away.
You idiot, the biclique attack does not mean that AES is “broken”. I guessed the related-key attack, because in some versions, that would have much lower time complexity (it just requires, um, related keys).
All that you need to do is to read the abstract of the paper that you cited. You don’t even need to hop over to Sci-Hub and enter the DOI (https://doi.org/10.1007/978-3-319-19962-7_3) to read the full paper. Just at least read the abstract!
Yup:
Full, unedited quote for reference:
Monero lost its reputation a very long time ago. Just imagine people having your IP addresses along with which sites you visited or where specifically you purchased something is quite frightening for those that thought they were dealing with a privacy based coin. I checked the link (https://monero-badcaca.net/) it does not look good for Monero as a privacy coin and it does not look good for those 100 user details that will be published daily 
I'm posting the daily report in Monero topic until they start moderating it.
I also observe that he is multi-posting. (And if he keeps up this arrant nonsense, I will start reporting it as a troll instead of replying.)
Among other things, AES is broken!!
Yes it is, Monero community members have a tendency to spew uneducated bullshit. https://link.springer.com/chapter/10.1007%2F978-3-319-19962-7_3
The real reason why I decided to apply a double-barrelled shotgun to an ant is that (a) the monero_badcaca OP received a merit from a security-ignorant, technically inept admitted hallucinogenic drug user who, alas, is a DT with an unaccountably high reputation;
I hope those defamatory remarks made you feel better, because they didn't make the IP leak go away.
You idiot, the biclique attack does not mean that AES is “broken”. I guessed the related-key attack, because in some versions, that would have much lower time complexity (it just requires, um, related keys).
All that you need to do is to read the abstract of the paper that you cited. You don’t even need to hop over to Sci-Hub and enter the DOI (https://doi.org/10.1007/978-3-319-19962-7_3) to read the full paper. Just at least read the abstract!
Quote from: Tao B., Wu H. (2015) Improving the Biclique Cryptanalysis of AES.
Biclique attack is currently the only key-recovery attack on the full AES with a single key.... We have a biclique attack on each of the following AES versions:
Our results have the best time complexities among all the existing key-recovery attacks with data less than the entire code book.
- AES-128 with time complexity 2126.13 and data complexity 256,
- AES-128 with time complexity 2126.01 and data complexity 272,
- AES-192 with time complexity 2189.91 and data complexity 248, and
- AES-256 with time complexity 2254.27 and data complexity 240.
Our results have the best time complexities among all the existing key-recovery attacks with data less than the entire code book.
Yup:
I dearly wish that Monero were exactly as “broken” as AES!