Live data from Hacker News

Microsoft no longer signs Windows drivers for Process Hacker

borncity.com

481–490 of 543 posts

Re: Microsoft no longer signs Windows drivers for Process Hacker

#481
post #433

Earlier quoted context omitted.

That would be oppressive but at least the unfree activities are restricted to the parts of our life where we must deal with authorities. We are still free to do whatever we want with our free computers in all other cases. > Or even worse, what would happen if gov regulations started requiring ISPs to stop working with non-compliant hardware? I.e. something like requiring network devices to attest they are "oficially"…

Ad-hoc radio mesh networks are constrained by physics and math as far as throughput goes, they are not competitive with normal networks. Governments have also shown the ability to regulate radio usage very well the world over.

> they are not competitive with normal networks

It doesn't have to be. The main goal is a free uncensorable network, if we must pay a price in performance for that, so be it. People use extremely old ThinkPads with libreboot because they're the last processors without Intel Management Engine.

> Governments have also shown the ability to regulate radio usage very well the world over.

Yes, because usually it's only a few people at a time who are interfering in radio communications. Easy to respond to a few isolated incidents. What if it was everyone at the same time?

What if every smartphone in the world could create and maintain its own mesh network? In some places there wouldn't even be a need for ISPs. They'd be needed for long distance connections only.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#482

Earlier quoted context omitted.

Did he enable a boot pin or are the drives just encrypted?

The drives are encrypted without a boot PIN. If I could exploit a vulnerability in the OS I could get the data. There will probably be a vulnerability discovered, at some point, that will allow access. I'd advised my friend's widow to hold onto the computers for the time being.

Please also advise her to power it on every 2 or 3 months or so (and leave it running for a bit), so that SSDs continue keeping the data, and HDDs don't get "stuck".

Re: Microsoft no longer signs Windows drivers for Process Hacker

#483
post #393

Earlier quoted context omitted.

In Brazil, we have a Java application that works on any system with a JVM. It's pretty nice. Why exclude citizens based on their choice of operating systems?

Note also that this was not always the case. Originally, it was a DOS-only application, then a Windows-only application, then for a while we had both the Windows-only application and the Java application, and then finally the Windows-only application was retired. I believe that the creation of the Java version of that application was due to complaints from Linux users, so this is AFAIK a case where citizens used to b…

> the creation of the Java version of that application was due to complaints from Linux users

Is this a fact? I too remember something along these lines but I wasn't sure. If that's the case, it's amazing. Those Linux users are still citizens and they pay taxes too, they absolutely deserve to be supported even if they are 0.1% of the population. The government has nor should have any profitability excuse.

> for a while, most banks required the use of an horribly invasive "security plugin" for the browser

Yes, the Warsaw plugin. It's even on the AUR.

https://aur.archlinux.org/packages/warsaw/

I HATE that thing. I tried to reverse engineer it once to see what it does and why it slows everything down so much. I caught it intercepting every single network connection. I actually switched banks to get away from this stupid software. Literally malware.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#484

Earlier quoted context omitted.

In a future where laws mandate signed software, the only way out is to somehow make our own hardware. We'll never be truly free unless we can manufacture free computers at home just like we can write free software at home. There is no software freedom if the processor refuses to run our code. Right now the chip fabs require billions of dollars in investments in order to make our processors. They are single points of…

In a future where laws mandate signed software "If you outlaw freedom, only outlaws will have freedom."

Correct. That's why we need the ability to manufacture hardware at home. So we can be the outlaws with the illegal computers that run software not signed by the government.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#485
post #36

Earlier quoted context omitted.

What’s the difference between a small sender and a spam host?

do you mean you never received spam from @gmail.com? Lucky you!

With a proper rspamd setup, gmail is the only source of delivered spam for me.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#486
post #23

The article mentions Process Explorer. Since Sysinternals were bought by Microsoft many years ago and the tools are distributed directly via Microsoft, such tools are unlikely to have an issue being signed. A brief history of the process for those not following it. Originally for kernel-mode drivers, you needed a code signing certificate cross signed by Microsoft's root . This means that the certificate follows a cha…

> So on the one hand, they're being quite friendly to open source.

This is surely not how I would interpret this behavior, even if regarding malware to a disproportionate degree.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#487
post #58
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.

It's honestly weird to see "Telemetry" labeled as "Spyware" by a technical people that, quite frankly, should know better. Spyware is NOT the same as gathering Telemetry data. You can also just turn off Telemetry in VSCode in the settings. I think a vast majority of people on HN gather data on customer usage of the products that they build. Because it ultimately makes us able to tailor the products better for our cus…

If it is unwanted, it is spyware in any case. Have an option to disable it and you would have a case. Otherwise you do spy on the behavior of people.

We don't collect customer data, we ask for feedback directly.

Re: Microsoft no longer signs Windows drivers for Process Hacker

#488
post #5

Earlier quoted context omitted.

you would have to automate that somehow if it becomes an issue

All Microsoft has to do to stop that from being a problem is to tell Defender to block that automation from running on Windows, for example, by refusing to run anything signed with the automation developer's certificates.

yeah thats true, you can get around some stuff with modified keyboards, accessiblity access, automated mouse but then you are just hacking things together at that point

Re: Microsoft no longer signs Windows drivers for Process Hacker

#489

Earlier quoted context omitted.

What did you expect? Microsoft labeling their data collection actions as "spyware" themselves? "Spyware" is a term used by people who oppose data collection, they didn't ask for. "Telemetry" is an euphemism by the ones that build this data collection into their apps.

I expect professionals to be able to distinguish between the two instead of being suckered into some sort of hive-mind thinking of "all data gathering bad hurr durr". I'm absolutely all for privacy and limiting unnecessary gathering of data. But there's nuances to this discussion and labeling everything that has any amount of telemetry as "Spyware" does not do anyone any good.

It isn't professional to find fitting euphemisms. Either the user has control over the data collection or he doesn't.

"hurr durr" strawmen on the other hand...

Re: Microsoft no longer signs Windows drivers for Process Hacker

#490
post #399
post #397

Earlier quoted context omitted.

So whilst three is different aren’t the analogues on Windows for 1) and 2) 1) Test signing - do what you want 2) Kernel driver - still possible, needs EV cert?

1) on Windows entails a significant security downgrade, as you cannot just pick custom kernel extension only, with validation by the user. That might however not be important, depending on your threat model. For 2), it’s borderline impossible to get a driver signing cert for macOS nowadays for individuals, it’s easier on Windows.

Ah yes, that is true, SIP is more granular than testsigning on Windows...
Post reply on HN