Windows 10 initially shipped with a way to turn-off forced app installs, but they removed it in the Anniversary Update, to force businesses to purchase Windows 10 Enterprise licenses.
-
Show this thread
-
Which comes with the underlying implication that Microsoft believes home users aren't even worth asking for consent from, because they don't have money.
11 replies 33 retweets 206 likesShow this thread -
Replying to @SwiftOnSecurity
There's a much better way they could achieve the same result AND protect home users: disable the ability to add custom root CAs except in Enterprise.
2 replies 0 retweets 3 likes -
Is it, though? What about people accessing intranets via VPN, what abou BYOD?
1 reply 0 retweets 1 like -
BYOD is bad too (& usually abusive). Employers should not be offering or requiring it. Corporate data should never be on personal machines and vice versa.
1 reply 0 retweets 0 likes -
Even if that weren't magical thinking (I agree on desirability, but it's entirely unlikely to happen), what about volunteers at smaller NGOs?
1 reply 0 retweets 0 likes -
NGOs have no reason to be MITM'ing their volunteers or employees. Custom root CA support is needed purely for nefarious corporate asset-control/employee-policing purposes.
2 replies 0 retweets 1 like -
Uh... no? PKI has pretty extensive theoretical uses, it's just most people don't bother because of complexity. Sure, I'm somewhat eccentric for having a 'personal CA' for my private network, but I've seen at least 2 NGOs use their own CA/PKI for internal authentication purposes.
2 replies 0 retweets 0 likes
A "personal CA" or "company CA" is fine if it's only authorized to sign for domains you own. It's not ok if it's a root CA and can sign for arbitrary domains.
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.