Hacker Newsnew | past | comments | ask | show | jobs | submit | rstat1's commentslogin

Here’s the PR explaining why they disabled this function

https://github.com/tailscale/tailscale/pull/18336

Seems like it caused tons of problems due to the variability of TPM quality among other things


and also source 1


Its WILD to me seeing Techrights described as "well-established, respected and trusted"


You can still care about forthcoming invasions of one's privacy and while still understanding that the 1st Amendment to the US Constitution is only intended to prevent state and federal governments from censoring you. Not corporations.

Semantics are very important when it comes to legal matters.


VBS is also in Windows 10 and has no problem working on CPUs that aren't "supported" in Windows 11


This is incorrect. Not all CPUs supported by Windows 10 supported the VBS feature.

Microsoft is making the VBS mandatory for OEMs, hence the CPU needs support, hence the ~7 year old minimum requirement for CPUs in what Microsoft supports for Windows.

Yes, you can disable it during setup as a workaround, but it's exactly that. And why you'd want to make your system less secure, well I'll leave that to the exercise of the reader when they'll turn around two weeks from now and complain about Windows security.


Most of the requirements for that feature are UEFI features or a TPM, and have nothing to do with the CPU

The actual CPU requirements are VMX, SLAT, IOMMU and being 64 bit, which have all been available on the Intel side at least, since at least 2008, with some coming available even before that.

The CPU requirement was just an attempt to force people to buy new hardware they didn't need. Nothing more.

A perfect example of this is the Ryzen 5 1600. Its not officially supported but meets every single one of the requirements and had no trouble enabling the feature in the run up to the release of Win11 (before it was blocked for no reason). I know this because I did it.

Also they marked all but one 7th Intel Core CPU as unsupported, and the one they did add just so happens to be the one they were shipping in one of their Surface products. No way you can tell me this list was based fact and not the whims of some random PM when they do stuff like that.


> and why you'd want to make your system less secure,

I'd offer that the likely goal here is the most usable system possible, working with what one has. If folks are here, there's usually a lot of necessity factors in play.


That they presently have no problems doing without this crap, so proving that they don't need it.


They've had plenty of opportunity to do this and haven't, so would find it incredibly unlikely they would magically start to have a problem now

Not to mention doing would basically kill game as one of the biggest reason people even still play Minecraft is the modding scene, not the minimum viable effort that have been the official updates for last number of years.


don't think they could do it previously because the code is not open and any names are a result of deobfuscation so clashes are accidental


And we all know those laws are never abused and are absolutely only used to target criminals.


No, there is definitely abuse of lawful interception.

But, in a jurisdiction with a functioning rule of law, these abuses can be spotted and remedied.

Doing the same for mass surveillance (such as ChatControl) or state-sponsored malware is much harder.

I'm advocating against ChatControl and malware, and proposing existing lawful interception frameworks as an alternative. But, apparently it's not my day :)


ChatControl is just lawful interception under a different name, but worse.


Malware has existed nearly since the dawn of computing. Making the world even less secure under the guise of combating w/e today's latest bogeyman is is not gonna solve that. And having secure private communications is not gonna make it worse.

That anyone thinks this blatantly obvious attack on free speech is actually going to be used only for law enforcement is wild to me.


Fire OS was an Android fork. Best I can tell from the stuff I've seen in the news about it, is that Vega OS is not Android at all, and is completely custom (well minus the Linux kernel)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: