3 ms·
See steps 1 and 2 from the linked article: We are taking several steps to remove this risk: • First, today we released a Security Advisory outlining steps our
by recoiledsnake 14y ago
See steps 1 and 2 from the linked article:
We are taking several steps to remove this risk:
• First, today we released a Security Advisory outlining steps our customers can take to block software signed by these unauthorized certificates.
• Second, we released an update that automatically takes this step for our customers.
• Third, the Terminal Server Licensing Service no longer issues certificates that allow code to be signed.
- rbanffy 14y agoThanks, @recoiledsnake, but I did read the article. > we released a Security Advisory So sysadmins will have to do something. What about machines that are managed by their own users? > Second, we released an update that automatically takes this step for our customers. What happens to machines that aren't updated (such as machines controlling industrial/flight/medical systems? > Third, the Terminal Server Licensing Service no longer issues certificates that allow code to be signed. Doesn't it run on the Windows machines themselves? Why would someone who's using it for signing malware upgrade to the new, non-signing, version?