Microsoft: we accidentally did `chmod 777 /etc/skel` and 2 months later we have no idea how to fix it. Just Windows things ¯\_(ツ)_/¯https://twitter.com/BeingSysAdmin/status/891905855788126208 …
-
-
Replying to @marcan42
And yes, on my Win10 1703 install, "C:\User\Default\AppData\Roaming\Microsoft\Start Menu" is writable by all users. Lovely.
3 replies 37 retweets 56 likes -
Replying to @marcan42
Apparently Microsoft's response to a trivial privilege escalation in domain environments is "eh, we might fix it next year, maybe" ¯\_(ツ)_/¯
2 replies 10 retweets 30 likes -
Replying to @marcan42
It's too bad systemd already got the "lamest vendor response" pwnie award; this one is worse.
1 reply 4 retweets 29 likes -
Replying to @marcan42
Eh, systemd had 5 worse-than-ignored CVEs, not just one. So it was still a well deserved win.
1 reply 0 retweets 2 likes -
Plus, Microsoft hasn't responded with open hostility, nor have they outright said they WILL NOT fix it.
1 reply 0 retweets 0 likes
But systemd had a "under convoluted circumstances admin might slip up" bug. Windows has a "lololol APTs are going to love this" bug.
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.