Something that scares me here--where is the awareness of emergent security errors arising from multi-threaded cryptography? As an example, consider a multithre

Something that scares me here--where is the awareness of emergent security errors arising from multi-threaded cryptography? As an example, consider a multithreaded streaming crypto API which consumes a symmetrically-encrypted data stream with an HMAC at the end. If multiple threads are simultaneously decrypting this stream, then how do they synchronize and verify their respective HMACs (let alone one shared one)? Frequently, in my experience, the answer is never--they just pass results blindly to an application thread which then operates on this data. By the time some last thread has belatedly realized that the entire stream was forged,the attacker has already been able to force the application to run malicious code.