mmobder
Is there any particular reason you're bringing up an issue that has nothing to do with Element x
ummmm, yeah, Element X uses Matrix so it's vulnerable to the attacks on the Element X AND Matrix -- see example.
They love to talk about hypothetical attacks that don’t apply to the way anyone practically uses a system
With all due respect, this is what analysing the vulnerabilities in the crypto stack sometimes is about. The depths of the technical analysis and having many of his reports patched by vendors should be enough of a proof.
Example of the technical analysis: Practically-exploitable Cryptographic Vulnerabilities in Matrix.
[...] that don’t apply to the way anyone practically uses a system
So apart of enumerating/pointing at the practical, tangible, immediate risks he points at the theoretical ones, and this somehow invalidates the former?
Can you point at the specific app/protocol/network where only HYPOTHETICAL attacks (ie: stemming from something no sane user or clever 'hacker' would do)? Just so we're on one side.
And finally if you can provide similar level of expertise in this field as them, see for example this category or this article , I'll gladly consider your opinion as a valuable assessment of soatok's professional capabilities, otherwise regretfully your opinion is just that.... - your opinion.
Similarly the person you are quoting in a way that's supposed to refute the claims from my link¹ doesn't seem to have relevant expertise, seeing as his blog is mostly about programming and bicycles and not cryptography or computer security, so seriously, do you raise THIS as your rebuke?
¹which includes prominent retraction from one of the original claims, with added context.
:)