MastodonTech.de

The New OilHackers turn <a href="https://mastodon.thenewoil.org/tags/ScreenConnect" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenConnect</a> into <a href="https://mastodon.thenewoil.org/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> using <a href="https://mastodon.thenewoil.org/tags/Authenticode" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authenticode</a> stuffing<a href="https://www.bleepingcomputer.com/news/security/hackers-turn-screenconnect-into-malware-using-authenticode-stuffing/" rel="nofollow noopener" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/hackers-turn-screenconnect-into-malware-using-authenticode-stuffing/</a><a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://mastodon.thenewoil.org/tags/ConnectWise" class="mention hashtag" rel="nofollow noopener" target="_blank">#ConnectWise</a>

Sascha StumplerPowerShell-OpenAuthenticode <a href="http://dlvr.it/TJ0mZY" rel="nofollow noopener" translate="no" target="_blank">http://dlvr.it/TJ0mZY</a> via PlanetPowerShell <a href="https://hessen.social/tags/PowerShell" class="mention hashtag" rel="nofollow noopener" target="_blank">#PowerShell</a> <a href="https://hessen.social/tags/OpenAuthenticode" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenAuthenticode</a> <a href="https://hessen.social/tags/CrossPlatform" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrossPlatform</a> <a href="https://hessen.social/tags/Authenticode" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authenticode</a>

Simon TathamI've just renewed the <a href="https://hachyderm.io/tags/Authenticode" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authenticode</a> certificate I use to sign <a href="https://hachyderm.io/tags/PuTTY" class="mention hashtag" rel="nofollow noopener" target="_blank">#PuTTY</a>.Now <a href="https://hachyderm.io/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://hachyderm.io/tags/Defender" class="mention hashtag" rel="nofollow noopener" target="_blank">#Defender</a> gives me dire warnings about my own nightly builds. Apparently it thinks the new cert belongs to some previously unknown SW publisher, who might be a malware source for all it knows.Is there any way to reassure it? E.g. the old cert hasn't expired yet, so I could use each one to cross-sign a declaration that the other one belongs to the same person.Is there a standard procedure for this?

Morten LinderudSpent the past couple of days rewriting my old pkcs7/authenticode library stuff for go-uefi into the new cryptobytes API.So far quite happy with it and hopefully makes me sleep better at night.<a href="https://github.com/Foxboron/go-uefi/commit/1b4504c78072bbf10eb957028da159c1761f3494" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Foxboron/go-uefi/commit/1b4504c78072bbf10eb957028da159c1761f3494</a><a href="https://chaos.social/tags/Golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Golang</a> <a href="https://chaos.social/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UEFI</a> <a href="https://chaos.social/tags/Authenticode" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authenticode</a> <a href="https://chaos.social/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureBoot</a>

Richard HughesDoes anyone happen to know what COFF sections get included when using <a href="https://mastodon.social/tags/Authenticode" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authenticode</a> signatures?

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#authenticode