Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft no longer signs Windows drivers for Process Hacker

borncity.com

Post reply on HN
Print view View original

131–140 of 543 posts

Re: Microsoft no longer signs Windows drivers for Process Hacker

#131

Post by vbezhenar »

amyjess wrote: 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.

Asymmetric cryptography is too simple to contain it. RSA is unbreakable and it's very simple to understand. It would be reinvented over and over by multiple people in multiple countries, you can't contain it.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#132

Post by FDSGSG »

nix23 wrote: post #30
eps wrote: post #25

In related news - ever wondered why Windows 11 can't be installed on "older computers"? You know, the ones that don't have a TPM chip? Now you know. Windows 11 completes the lock-up of the OS. That's why Windows 11 exists in the first place. All other changes are secondary. Microsoft knows they would've not been able to pull shit like this as a Windows 10 update, so they were effectively forced to do a version increa…

It's absolutely fascinating that an open OS like windows (not open as opensource, but open to run every program) takes that route. Microsoft really thinks they can compete with platforms like android or iOS, i have to say: Thank you Microsoft!! You accelerate the downfall of Windows! No one will need you in the future, Adobe on M1(Apple), Development on Linux, Gaming on Linux, Workstations Linux maybe some Apple.

Weird nerds like you that care about "open platforms" at the cost of security are a tiny minority. This will do nothing to accelerate the downfall of Windows.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#133

Post by canada_dry »

lordofgibbons wrote: post #9
Gargyle wrote: post #8

Earlier quoted context omitted.

Where did they actually do nice things? VSCode is still not entirely open source and the official builds have spyware included.

Thank you for saying this. For those who don't know about the open-source release of VSCode, check out https://vscodium.com/

Sadly, MS has locked-out the extremely useful and popular PlatformIO from being available in vscodium.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#134

Post by pjmlp »

gavinray wrote: post #50
pjmlp wrote: post #26

Earlier quoted context omitted.

But it will be built on top of WSL3 and all hackers will jump of joy with Windows/Linux.

Relevant tweets from self: https://twitter.com/GavinRayDev/status/1446459866059612162 https://twitter.com/GavinRayDev/status/1446460168389136395 WINE and the very popular/well maintained Linux distros have gotten so good in recent years that the scenario is nearly identical to Windows + WSL2, except with the DE reversed. And WINE is never going to run entirely as smooth/easy as regular Windows, though it's pretty dam…

If a full Windows/Linux ever happens, expect it to be as free beer as ChromeOS and Android are when not installed via official OEM distributions.

It will be the same driver dance and boot loader stories since Linux exists.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#135

Post by Gigachad »

smileybarry wrote: post #100
the_only_law wrote: post #4

Earlier quoted context omitted.

For drivers, I don’t think so. You can enable some boot settings that allow you to run unsigned drivers, for development purposes, but it will revert upon reboot, without anyway to enable it permanently.

It's one command and you're forever in test mode[1], i.e.: don't enforce driver signatures: bcdedit /set testsigning on You just have to disable Secure Boot in UEFI first. (And I can confirm Windows 11 doesn't actually require Secure Boot to boot, I've had it off for months as part of win11 certification testing.) I'm not sure but DRM might revert to lower levels (e.g.: 720p), but that also happens on macOS when you…

One thing to note is that game anti cheats will just lock you out if you are in this mode.

It’s the reason that game cheat makers look for exploits in random drivers to load their cheat in kernel space.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#136

Post by no_time »

FDSGSG wrote: post #122
eps wrote: post #25

In related news - ever wondered why Windows 11 can't be installed on "older computers"? You know, the ones that don't have a TPM chip? Now you know. Windows 11 completes the lock-up of the OS. That's why Windows 11 exists in the first place. All other changes are secondary. Microsoft knows they would've not been able to pull shit like this as a Windows 10 update, so they were effectively forced to do a version increa…

This reads exactly like the crazy conspiracy theory nonsense that FOSS-clowns were pushing out regarding Secure Boot. How did that end up? Well, turns out that they can now safely be called clowns.

The water is getting so hot the frog is having problems breathing from all the steam.

"Crazy conspiracy!" He yells between two heavy gasps for air.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#137

Post by pedro2 »

rzzzt wrote: post #20
alias_neo wrote: post #14

Earlier quoted context omitted.

I use VSCodium every day, and recommend it over VSCode to everyone, however, due to microsoft's locked down plugins, particulary the ones related to remote development and debug, there are certain things which can be done with VSCode and not VSCodium. It's worth bearing in mind for those considering switching.

SSH FS, a third-party extension seems to work well with VSCodium: https://github.com/SchoofsKelvin/vscode-sshfs

They mean Microsoft's plugins -- they just work with VSCode on purpose.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#138

Post by MrStonedOne »

From: https://github.com/processhacker/processhacker/discussions/7...

>The existing drivers are compatible with Win11 and haven't been blocked by Microsoft yet... The large majority of changes by Microsoft are limited to restricting the Windows API with signature checks that block competitors software (e.g. CreateWindowInBand, NtQuerySystemInformation, NtQueryInformationProcess to name a few) rather than directly targeting the drivers themselves.

>The signature checks added to those functions and classes only block third-parties and this includes signed binaries. We won't be able to implement the same functionality as Task Manager and Process Explorer because of those Microsoft-only signature checks even after we sort out the submission issue.

>Always-on-top, Auto-elevation, DPS statistics, Default taskmgr application preferences (Microsoft hardcoded taskmgr.exe blocking competitors), GPU statistics (deliberately broken on Win10 and Win11 recently) and the DirectUI framework are some examples of features that I want to implement and are currently implemented by Task Manager but are Microsoft-only signature restricted while newer more advanced security like PPL that we desperately need are also Microsoft-only signature restricted.

>The only certificate allowed to use these and other functionality is now limited to Microsoft Windows certificates - the same certificates used with Task Manager and Process Explorer - while SAC has even more powerful functionality than anything else (including Process Hacker) with absolutely no security whatsoever.

So, basically, for some reason, Microsoft wants to make it very hard for you to see whats running on your computer...

Re: Microsoft no longer signs Windows drivers for Process Hacker

#139

Post by maccolgan »

dTal wrote: post #57
throwuxiytayq wrote: post #2

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.

Quite a lot of community goodwill, unfairly granted. I've lost count of how many times I've read on this very forum, "calling it Micro$oft is childish, they're a changed company, Nadella is better than Ballmer, etc". They are as hostile to free software as they ever were. Why wouldn't they be? It's antithetical to their business model. The only thing that's changed is how sneaky they are about their time-honored tact…

EEE isn't obsolete, very far from obsolete in fact, they are just playing it (very) long.
Post reply on HN