News for hackers. Stuff that matters.
Re:Windows 10 Debloat Script by kabdib on Saturday July 20, 2019 @03:57PM (#20487955)
The biggest WTF was Cortana . . . running by default on Windows Server.

I have no idea what they were thinking. Yes, you can disable it with a policy editing. For a server product, you shouldn't have to.

Re:Windows 10 Debloat Script by jniedrauer on Saturday July 20, 2019 @04:11PM (#20488039)
It's unsurprising to me that *nix systems are the majority on Azure. It is surprising to me that enterprise shops still commission new Windows servers at all in $current_year.
Re:Windows 10 Debloat Script by technion on Saturday July 20, 2019 @09:45PM (#20489459)
In supporting the enterprise, pretty much every application I deal with is unfortunately "Windows Only". Accounts tends to be managed by MYOB, Quickbooks or in the large firms, Accountants Office (also a MYOB product). All these ship with Windows services, Attache being particularly offensive as it has "known issues" with clients on Windows 8.1 or higher. Pay is often Payglobal or NAV, which again is Windows.

The closest I had was a LexisNexis product that used to run on a Linux server - until our account manager told us they were dropping Linux because, and I quote, "Linux has too many security problems". I've supported two different EMR (medical) products, and at least five different POS products, all Windows only. Even when we get a SaaS product running in a web browser, half the time it's "IE only".

I'd give a lot to live in the type of organisation without this legacy.

Re:Windows 10 Debloat Script by noir_lord on Saturday July 20, 2019 @04:06PM (#20488009)
Wow, that seems like an insane choice as the default.

I'm curious what the rationale was behind that choice.

Re:Windows 10 Debloat Script by JudgeWapner on Saturday July 20, 2019 @10:49PM (#20489689)
Tinfoil theory incoming: NSA pressures windows to have the largest attack surface possible by default. With the hope that any given targeted system will have at least one piece of default bloatware still running, presumably they have 0-days for most all of them.
Re:Windows 10 Debloat Script by IntelMiner on Sunday July 21, 2019 @03:32AM (#20490354)
Even putting aside the tinfoil hat. The NSA would never pressure anyone to have a larger attack surface, that would just make it easier for competing nations and attackers to discover flaws, which would render their own efforts moot
Re:Windows 10 Debloat Script by nitrogen on Sunday July 21, 2019 @03:54AM (#20490404)
They have compromised crypto standards in the past, but we can't use that to justify every conspiracy theory without evidence.
Re:Windows 10 Debloat Script by JudgeWapner on Sunday July 21, 2019 @01:30PM (#20492467)
if Russia discovers how to hack Cortana and keeps it private, that in no way impinges on NSA's ability to use the same hack to compromise, say, an Iranian system. The more possible avenues for attack, the better (for attackers).
Re:Windows 10 Debloat Script by jankotek on Saturday July 20, 2019 @08:52PM (#20489271)
Windows 2003 Server had sound system disabled in default installation. How things change...
Re:Windows 10 Debloat Script by kabdib on Saturday July 20, 2019 @11:27PM (#20489804)
Server 2012 had touch screen support. I can think of many things I'd rather have than touch screen support.

How about decent support for two-factor domain login?

Priorities, guys. (Please don't get me started about the special circle of hell that is deploying Windows. It truly is a misery).

Re:Windows 10 Debloat Script by jankiehodgpodge on Sunday July 21, 2019 @06:19AM (#20490695)
Server 2019 also has the sound service disabled and doesn't come with Cortana either, just windows search.