Live data from Hacker News

Microsoft no longer signs Windows drivers for Process Hacker

borncity.com

411–420 of 543 posts

Re: Microsoft no longer signs Windows drivers for Process Hacker

#411

Earlier quoted context omitted.

That's just game fault that it saves data in game files instead of user directory.

No, Steam puts stuff like steam cloud in the programfiles dir as well. It's totally under their control where it goes.

Steam Cloud files location is also specified by game developer: https://partner.steamgames.com/doc/features/cloud

Re: Microsoft no longer signs Windows drivers for Process Hacker

#412
post #246

Earlier quoted context omitted.

> Spyware is NOT the same as gathering Telemetry data. Telemetry and spyware differ only in the way collected data is used.

> Telemetry and spyware differ only in the way collected data is used. No, they first and foremost differ in the kind of data is collected. Spying is not spying if you anonymously collect information about how frequently a feature/future/option is used only.

Would it be OK if the NSA required it? No? Well, it's not OK for your OS vendor to require it, either.

And the illusion that it will always be possible to disable telemetry is just that, an illusion.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#413
post #55
post #37

Earlier quoted context omitted.

Very informative. And presumably on OSX none of this applies because it's all BSD underneath? Or is OSX different again to just running BSD out of the box?

On macOS, you have those options: - SIP off (totally, or just driver signature enforcement) - kernel driver (deprecated, Apple doesn’t issue new certs anymore it seems) - system extension (user-mode driver, explicitly intended for device compatibility)

And as far as I understand, disabling AMFI disables code signing support and enforcement completely.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#414
post #31

Earlier quoted context omitted.

Not sure, I'm quoting directly from the article.

The same question has been answered in the linked GitHub issue, though the comment was marked as off topic. It's special administrative console, more in depth info what that actually is in the comment. https://github.com/processhacker/processhacker/discussions/7...

The highlighted comment has been marked as off-topic and requires logging in to view, which I'm disinclined to do from mobile. Is there a summary elsewhere?

Re: Microsoft no longer signs Windows drivers for Process Hacker

#415

> Windows owns the market for the simple reason it's not some locked down garbage controlled system How did you come to THAT conclusion?

That used to be true. But clearly Windows is going in the same direction as Android and macOS.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#416
post #55

Earlier quoted context omitted.

On macOS, you have those options: - SIP off (totally, or just driver signature enforcement) - kernel driver (deprecated, Apple doesn’t issue new certs anymore it seems) - system extension (user-mode driver, explicitly intended for device compatibility)

And as far as I understand, disabling AMFI disables code signing support and enforcement completely.

Disabling AMFI is a whole other level of a hammer, that I do not recommend at all on a system that you might actively use.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#417

Earlier quoted context omitted.

I saw the writing on the wall the moment they could sloppily justify the TPM requirement. Then I got into arguments with people proclaiming that it's just Microsoft enforcing it for the casual user's safety, and that I'm a Microsoft hater. Who? Me, whose first programming language was C#, who worked as an Windows server administrator for years, and my operating systems have been nothing than Windows for 2 decades. An…

I genuinely miss the days of playing with DOS, Windows 9x and then all the excitement of Windows XP. All on my own hardware, which was whatever I could scrape from parents, savings, neighbours. I could do what I wanted with these old PCs. There was an openness that existed in the world of computing. Despite all that was said of Microsoft back then, and much of the complaints about proprietary software were true then…

And I increasingly wonder, were we freer back then because there was still some empathy towards customer needs at Microsoft, or because they were simply stifled from their real intentions by technological limitations?

They've been slowly cooking the frog in the background for a while now with the "trusted computing" stuff. It's over a decade old at this point. Back then the userbase was more technical and likely to smell BS, and DRM was definitely not liked even by the general public.

https://www.cl.cam.ac.uk/~rja14/tcpa

https://www.cl.cam.ac.uk/~rja14/tcpa-faq-1.0.html

...but then they eventually found out that people could be scared into doing anything by justifications of "security" (regardless of what's being secured, who it's being secured by, and who it's being secured from), and here we are today.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#418

Earlier quoted context omitted.

I have a theory that this seismic shift is the result a demographic shift of PC users. It gradually went from engineers, businessmen and hackers to a much wider audience including younger people who have trouble grasping concepts such as folders[0] This by itself is not bad, problems arise when companies use this to justify deny control even from those who can be responsible with it. [0]: https://www.pcgamer.com/stud…

The problem arises when there is no way to differentiate between the user classes. And while I enjoy computing freedom, I’m not exactly proclaiming its value when I have to deal with a DDoS or hear about people getting ransomwared. I know things like Mirai also exist, and that user error isn’t the only ransomware vector, but poor computing habits absolutely fuel such problems and they cause pain for society as a whol…

And while I enjoy computing freedom, I’m not exactly proclaiming its value when I have to deal with a DDoS or hear about people getting ransomwared.

"We are not truly free if we don't have the freedom to make mistakes."

It's nice to hear about cyberattacks and such continuing, because it means freedom still exists.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#419

An immensly powerful and useful tool. Can't live without it. Hopefully the situation resolves soon. What is it with MS these past few months? It's like they're trying to throw away the little community goodwill they managed to build up over the years.

What goodwill?

Re: Microsoft no longer signs Windows drivers for Process Hacker

#420
post #29

Because of things like this, I'm at the point where I consider the invention of public-key encryption to be the worst thing that's ever happened to the world. If governments had _immediately_ preemptively classified anything related to assymetric encryption—and actively enforced the classified status—as soon as the first research into it started appearing, the world would be a much better place than it is now.

Governments did classify encryption as munitions for a long time, and some of the regulations from that era still exist. But it's hard to ban maths.

On the other hand, contrary to all the downvotes you're getting, it's good to see some other people who have taken the same critical view of encryption that governments have/had --- because it can be used against them.

Post reply on HN