I honestly googled what the "SAC" stands for, but couldn't find anything. Please, please people, don't assume everybody knows your acronyms.
Microsoft no longer signs Windows drivers for Process Hacker
361–370 of 543 posts
Re: Microsoft no longer signs Windows drivers for Process Hacker
#362Earlier 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.
What if you repeatedly fail to anonymize the information and also collect user-entered data like command line arguments?
Re: Microsoft no longer signs Windows drivers for Process Hacker
#363From: 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 tar…
> So, basically, for some reason, Microsoft wants to make it very hard for you to see whats running on your computer...
So they can run spyware. Nearly every user hostile policy or behavior can be explained by the insatiable lust for data.
Re: Microsoft no longer signs Windows drivers for Process Hacker
#364In 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…
Call me paranoid, but I am completely certain that TPM has a backdoor disguised as a very sophisticated bug for plausible deniability. I'll never trust BitLocker or anything that relies on TPM to encrypt any data I actually care about not being compromised (read: my very personal data, not work data).
I doubt it. A much more likely suspect is the Intel Management Engine, which unlike a TPM module, runs an entire operating system alongside your computer and hides it's outgoing traffic as encrypted TLS data. Yikes.
A much more likely explanation for TPM is that it can enforce weak and vulnerable cryptography at a hardware level. It's an open secret by this point that the NSA weakens elliptic keypairs to make them vulnerable to differential cryptanalysis. With TPM, software can now be forced to use hardware crypto, which is almost always weaker than the programmable software crypto we had before.
Re: Microsoft no longer signs Windows drivers for Process Hacker
#365From: 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 tar…
> So, basically, for some reason, Microsoft wants to make it very hard for you to see whats running on your computer... So they can run spyware. Nearly every user hostile policy or behavior can be explained by the insatiable lust for data.
They wanted feature parity with MacOS' ability to hide processes from the user.
Re: Microsoft no longer signs Windows drivers for Process Hacker
#366Earlier quoted context omitted.
I find it interesting that, one one hand they are implementing features "in the name of security" that limit the owner of a computer what he/she can do with it and on the other hand they are adding backdoors so that government agencies (or anyone with right information) can spy on citizen that use this "secure" OS.
I will personally pay you twenty thousand US dollars (in the cryptocurrency of your choice, bank transfer, western union, whatever) if you can prove beyond reasonable doubt that Microsoft has ever secretly shipped a backdoor in their OS so government agencies could spy on their users. Perhaps you will be the first person to actually prove the existence of the NSAKEY backdoor? (I doubt it.)
Who needs a backdoor when you can just exploit the print spooler from 1999???
Re: Microsoft no longer signs Windows drivers for Process Hacker
#367In 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…
We notice the Microsoft front. Microsoft has marched through the "open" source institutions and employs a sufficient number of OSS people. In Python, Microsoft employees (who don't develop much ...) have two seats in the Steering Council and GvR, who still seems to pull strings. Opposition on the mailing lists is shut down ruthlessly and is censored. The new "JIT" project has all the hallmarks of NIH and will end in…
Can you elaborate on the problems with JIT implementation in Python? I'm far from Python development, but it seems intresting
Re: Microsoft no longer signs Windows drivers for Process Hacker
#368> Windows owns the market for the simple reason it's not some locked down garbage controlled system
How did you come to THAT conclusion?
Re: Microsoft no longer signs Windows drivers for Process Hacker
#369Earlier quoted context omitted.
Stallman was ALMOST right. The fight is not about which programs the user can run, but who controls the user data
No, Stallman was right about pretty much everything. It's impressive how far into the future he saw, much earlier than many of us, including myself. There is no computing freedom without software freedom, and there is no software freedom without hardware freedom. Control of data is a related problem. It's absolutely relevant but it's not in any way opposed to computing freedom. In fact, they are aligned. Computing fr…
Exactly right.
The move to ARM will highlight the hardware freedom in a big way.
People are used to ARM being different and are that much more likely to forget open, general purpose computing right along with that "old" x86...
Heh, I always disliked x86. But now? I look at it fondly.
Strange times.
Edit: It is the IBM PC lineage I speak of here, not just the ISA.
Re: Microsoft no longer signs Windows drivers for Process Hacker
#370Earlier quoted context omitted.
> 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.
What if you repeatedly fail to anonymize the information and also collect user-entered data like command line arguments? https://github.com/dotnet/sdk/issues/6145
Well, you make my point. What you linked to is definitely not telemetry.