I have had to try and work with Authenticode in the past. It is a bear! Things like security catalogs instead of just embedding the signature makes an already difficult thing to implement even harder. The APIs don't even work right on Windows XP... Microsoft invented the damn thing, if they can't implement it how can I be expected to? Anyway, since I was familiar with the problem, it was a good time to toss out a comment.Our antivirus apparently can't understand security catalogs and just flagged a Windows system file as suspicious because no authenticode.— SwiftOnSecurity (@SwiftOnSecurity) August 12, 2016
After tossing out that line I just continued reading Twitter until...@SwiftOnSecurity As a past developer: security catalogs make validating authenticode signing a pain. But such a problem shouldn't go AV live— Cyber Pathologist (@SecsAndCyber) August 12, 2016
Well, this seemed like a big deal at the time.
— Cyber Pathologist (@SecsAndCyber) August 12, 2016It wasn't until the next day I noticed what the SwiftOnSecurity bump had done to my post views.
Something changed. Guess which day had the retweet |
No comments:
Post a Comment