Por si con TLS no hubiera bastante confusión... IE dice que la firma de un EXE está dañada (usa sha1) pero Win no.pic.twitter.com/s4Ts3hTPuR
@ssantosv @Seifreed Yeap, noticed this also recently - it's apparently since 1 Jan 2016, see: http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx …
-
-
@bartblaze@Seifreed Yes, I'm aware. But Chrome is doing the same using periods to "ban" SHA1 in TLS & it makes it all confusing for users. -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.