Does this standard prevent unsigned portions, a la Dropbox/Chrome telemetry with Authenticode? https://docs.microsoft.com/en-us/archive/blogs/ieinternals/cavea

Does this standard prevent unsigned portions, a la Dropbox/Chrome telemetry with Authenticode? https://docs.microsoft.com/en-us/archive/blogs/ieinternals/caveats-for-authenticode-code-signing#cheating-authenticode https://docs.microsoft.com/en-us/archive/blogs/ieinternals/c... > the signature blocks themselves can contain data. This data isn’t validated by the hash verification process, and while it isn’t code per-se, an executable with such data could examine itself, find the data, and make use of it https://news.ycombinator.com/item?id=8203164 https://news.ycombinator.com/item?id=8203164 (2014)