And yet nobody found ROCA. Even though that code stank. Audits are largely useless, because they often just verify that you do what you say you do, not that you're actually secure. "Yes, we have these mitigations (which stop one variant of an attack but not another)".
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
If they can't audit software properly I'm not going to assume they can audit hardware properly.
1 reply 0 retweets 0 likes -
It sounds like a bad faith debate... Roca is concerning, but: - Even if CC are not perfect, they are just the best framework to ensure high level of security - CC labs are clearly better auditing security than any other org - Roca remains complex, took several years of research
1 reply 0 retweets 0 likes -
At the end, the vendor patched it. Impacted products were known since they went through certification, devices on the field have been recalled and replaced...
1 reply 0 retweets 0 likes -
ROCA took several years of research because the source code was closed and unauditable to third parties. There are plenty of cryptographers who would've raised an eyebrow at that code, and RSA keygen is one of the first things you look at for problems.
1 reply 0 retweets 0 likes -
ROCA was so obvious once the finger was pointed at the problem area that I had friends who reverse engineered it through key analysis and guessed at what the bad code was doing, before the official research paper was published.
1 reply 0 retweets 0 likes -
This is an endemic problem in parts of the industry, where half-competent people are the ones doing the audits, while access is denied to those who could actually find problems quicker (but might not work for a big auditing firm).
2 replies 1 retweet 1 like -
Big auditing firms excel at filing a lot of paperwork and certifying a lot of PowerPoint bullet points. They do not excel at finding actual problems. They might find some, but not nearly as many as would be found if the product were auditable at large.
1 reply 0 retweets 0 likes
I have experienced this problem myself, when I was brought in to do a black-box audit for a vendor, and immediately identified a risk area, requested access to do a white-box audit, and was denied (and there was insufficient time to get that access myself via attacks).
-
-
Months later it turned out there was a problem that I would've absolutely found in a few hours tops, had I had access to the binary (not even source code!). Not trusting more people to audit your stuff just leads to insecure garbage.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.