SiebenHeaven

Thanks for the pointer to your interesting paper.

My understanding is that TLS spec did not enforce non-repeating nonce, only suggested it and left it to implementers to decide which led to the vulnerabilities you explored.

This Samsung one here is in a way similar - the TEE API had a way for users of the API to set IV which it should not, TA should make sure the IV is not repeated.

Since you have done prior research in this area, is using a counter for IV still recommended even when IV is 12 byte? I assume chances of HW random number generator (which I assume exists on most phones today) colliding for 12 byte random number generation would be pretty low.

I am pretty surprised how they allowed reusing IV. Unique IV is explicitly mentioned to be an assumption for AES GCM (first sentence in security section of AES-GCM wikipedia page)

How could anyone design TA (i.e application whose whole point is security and hence it runs in the secure mode) and allow user to set IV in the API?

"We do not break the userland"

Great article, I'm bookmarking it so I can point to it if and when required ;p

Question is would we really get any benefits by this - compilation would take longer by some x amount which may or may not be less than the time linking step takes currently.

If you have looked at rust, you would understand that "Written in Rust" means something more than just the face value. Written in Rust means that there will be less memory/concurrency bugs due to the language itself ruling out classes of those bugs and that is a feature that I would definitely care about in any peice of software I use.

Most commonly used software such as browsers can abort on OOM, this isn't about those cases at all. In conditions that you do not want to abort, usually you can and would want to allocate pool before hand.

Ah yes, modern git for people using modern c++ If your plain old git works fine for you, there is no need to go looking for modern git IMHO.

Won't turning js off make you one of the few people in the world that do this and hence easier to fingerprint?

This is the real question. Especially for vaccines that mimic the spike protein to make another attenuated virus look like a coronavirus.

A ASUS phone (zenfone 2) had this hardware superresolution feature you are talking about

So ... Microsoft has a a threat modelling tool. Wonder if it existed and used when these designs were made.

Excellent example of why one should attempt to limit attack surface.

Why do you say that? (genuine question)