Anyone saying secureboot "brings absolutely nothing" clearly doesn't understand how secure boot works (or is just arguing in bad faith). Secure boot has issues (see key revocation issue & vulnerable UEFI program used by malware to install bootkit) but it does address a real security issue.
People might not like who holds the commonly preinstalled keys (Microsoft and motherboard OEMs) but even then you can add your own keys and sign your own images if you want (there was just a post yesterday about doing this for raspberry pis),
> People might not like who holds the commonly preinstalled keys (Microsoft and motherboard OEMs) but even then you can add your own keys and sign your own images if you want (there was just a post yesterday about doing this for raspberry pis),
I like SecureBoot, and I like that I can select my keys to sign things the UEFI will run, but I don't like that I can't replace the UEFI itself since it's protected by bootguard.
Now if I can edit the UEFI, that's a gamechanger: I could have my signed UEFI payloads check the UEFI firmware has the parts I want (or don't want) and refuse to keep booting if it doesn't
I don't think its absurd at all. It isn't required in anyway (opt in), lets you use your own keys (no preinstalled microsoft or other bigcorp keys), and isn't possible for someone to modify what keys you installed.
Of course if you lose your keys you can't sign anything else and that would make it basically ewaste, but most things end up as waste when you take actions that are reckless and can't be reversed (which is what losing the keys would be). Plus tech tends to ends up as ewaste after less than a decade anyways. Like sure you could still be using an AMD steamroller CPU but realistically after 10 years you'd be better off using a cheaper more power efficient chip anyways.
> Plus tech tends to ends up as ewaste after less than a decade anyways. Like sure you could still be using an AMD steamroller CPU but realistically after 10 years you'd be better off using a cheaper more power efficient chip anyways.
I'm not sure what you are trying to argue but people routinely buy used computers on market place. Rasperry pies with locked keys are essentially paper weights once the owner doesn't want to use them anymore.
And realistically, the biggest ewaste generators are especially smartphones nowadays which are too locked to be reused well.
> I'm not sure what you are trying to argue but people routinely buy used computers on market place. Rasperry pies with locked keys are essentially paper weights once the owner doesn't want to use them anymore.
Why can't the owner who wants to sell their locked Pi give the buyer the key?
I honestly don't understand why people act like this. Wanting to be able to ensure firmware isn't maliciously modified is a good thing. Open firmware is also a good idea obviously but there has to be a way to ensure firmware is signed either by OEM or your own keys like secure boot.
As for games, lots of people play games and want good anticheat. If you don't like that you don't have to play those games but no need to act like the way you are because other people want decent anticheat.
>honestly don't understand why people act like this.
Because it’s social pressure to compromise your computer to a gaming company to get to play a game.
People don’t care about the anticheat on their computer, they want it foisted on everyone else who plays, which is a sucky proposition for privacy and security minded people.
It’s like advocating for the TSA to be controlling access to the grocery store because you want to feel safe there and don’t mind the privacy violation.
>People don’t care about the anticheat on their computer, they want it foisted on everyone else who plays, which is a sucky proposition for privacy and security minded people.
No they want games without hackers. Which kernel based anticheats helps with. Can it also impact privacy and security? Yes no doubt but so can any program running on the computer even in userspace. Remember we are talking about kernel anticheats on windows lol.
If you are really worried about it you could dual boot like many people. Either way this whole argument seems silly to me.
You say “no” but then repeat what I said worded differently. When the current market for “games without hackers” is filled with kernel modules, it sucks.
It's worth reminding that we already had a solution to the games with hackers problem: smaller community-run servers where people can get to know each other. But game companies want the centralized model so that they can stay in control of how the game is used to continuously monetize it and to forcefully retire it once they want to push a newer one.
Hackers are mainly only problem for anonymous ranked matchmaking. That's not to say cheaters don't exist without it but they are a) much less disruptive b) have much smaller reach and therefore c) are less motivated.
Like most ills being used to push anti-user technology, cheating is primarily a problem created by the industry itself.
It's a bit of a stretch, but maybe we as a society should be considering the social pressure as being the problem. Why do we allow ourselves to be 'controlled' in this way by others? Especially young people? If we could learn to move past this?
What do you mean by this? As the user you are intending to have the game and its anticheat run. Having to download and run a game on your computer isn't compromising your computer either. Maybe the only thing which doesn't give the game company power to run potentially malicious code on your machine is cloud gaming. That also solves the cheating problem at least.
>You're advocating for installing a kernel module that you don't even know what it does exactly when running a random game.
You don't know what the game will do either. It requires trusting Riot even if there isn't an anticheat.
Also most users will never know what the other kernel level drivers do.
>Would you also support a full cavity search each time you decide to fly a plane?
I don't see how this is related?
>The kernel module has full access to your hardware, you don't know what it does exactly.
The same can be said about any other kernel level driver and even about Windows itself.
>People got so complacent in recent years, and this is on a technology forum no less.
What Riot wants to do is not possible with a user level anticheat. Once Windows eventually gets its security improved such that apps can query the integrity of the system Riot would likely be able to get away with a less privileged anticheat.
>I guess today the Sony rootkit[1] would be totally acceptable.
If it didn't try and hide itself I would agree with you.
Sure, isolation exists except for Riot Games (and any other company that adds similar mandatory modules, which eventually will be all). Oh yeah, assuming there also won't be any vulnerabilities, but that's impossible, because we all know about the high quality software coming from gaming industry.
2. All it actually does is keep users trapped in Windows. God forbid anyone actually use Linux, or even a VM!
The only actually effective anti-cheat is the original: moderation.
Now that users aren't able to host their own servers, they can't do moderation. Game studios don't want to do moderation themselves, so they keep trying (and failing) to replace it with automated anticheat systems.
This here. Cheaters will always find ways to cheat. Theres already cheats that run on completely separate machine so they cant be detected. Legimate customers keep getting screwed.
Game companies want the centralized model so that they can stay in control of how the game is used to continuously monetize it and to forcefully retire it once they want to push a newer one.
Because people prefer to pay 10x as much to have apple/google/etc host it for them. It's still a thing for people who know what they're doing and the experience is vastly better and more private and secure.
> As for games, lots of people play games and want good anticheat
Great, let's install a backdoor in every computer so that some people can play games and watch movies. No. Computer is a thing for computing numbers not a replacement for a TV.
I can't take people like you seriously. The anticheat isn't a backdoor. It doesn't ship with the operating system or come preinstalled in anyway. You opt into it when you play the game. Literally nothing is forcing you to use it or have it installed on your computer.
I understand this is the internet and being super dramatic is part of it but can we please be for real for one moment?
What's wrong with people being upset that in order to play the game they have to install low level kernel modules? It's flawed software that hits an ant with a sledgehammer. Adding to injury, tons of reports online of people getting BSODs and other security features not working while the module is enabled. It's invasive and it's silly to be as dismissive as you are around peoples' concerns.
I meant things like Microsoft's signing keys embedded inside BIOS, Microsoft Pluton CPU, secure enclaves inside CPU (now deprecated though) and things made for Secure Boot and DRM.
> Wanting to be able to ensure firmware isn't maliciously modified is a good thing.
I'm not sure it's a good thing at its core. The intent seems legit on the surface, but digging into the implementation you'll always end up having an adversarial relation with your user's security and device ownership.
On games, I kinda see this as an argument for preserving a special status for consoles, where the maker keep a right to secure everything to insane levels. Doing the same on general purpose computing platform isn't acceptable. Banking and digital currencies are morr of a blurry line, but games definitely shouldn't be accessing the utter most secure system of the platform.
If anything, opening the door to a whole community to hack the base security of your computing life when litteral life and death applications also rely on those shouldn't be allowed.
But how will this provide the game company with continous revenue streams from selling you database entries that you can show of to complete strangers.
Intel gave it to MSI, but I may have been incorrect before. Apparently the keys was shared across multiple OEMs (at least that is how I read this below)
>The leaked private keys affect Intel’s 11th, 12th, and 13th generation processors and were distributed to various OEMs, including Intel itself, Lenovo, and Supermicro.
...isn't such signing usually done the other way around? Intel would hold the signing keys, MSI (or any other OEM manufacturer) then sends (over a secure channel) their firmware to Intel, Intel signs it and sends the signature back.
The processor has to verify the signature, which means the public key needs to be embedded in the processor. It makes sense that the processor manufacturer creates the keys and distributes them. If it was the other way around, then a) fifty motherboard manufacturers would make their own keys and the processor would need space to embed fifty of them, and b) a new fifty-first motherboard manufacturer coming into the market would be unable to support any existing CPUs. It would also explain why the same key was used for signing multiple motherboard manufacturers' firmware.
Why distribute the keys themselves instead of having some way for the motherboard manufacturers to upload an unsigned firmware and then download a signed one? That is probably laziness.
If this is the Intel key that's burned on the CPU (or PCH, I forgot) e-fuses, and that manufacturers use to sign their own BIOS and UEFI payloads, do you think this will enable us editing the manufacturer bioses to tweak variables, resign some of their EFI payloads or just remove some of these payloads? (like the ones involved in checking the PCI or USB ids is on an approved whitelist of WWAN and WLAN cards cards)
I ask because this would enable a lot more security: I could mod my bios, and add a extras EFI module signed with my key that wouldn't trigger bootguard: then later during the boot, an encrypted grub or whatever could check them, say with a TPM enrolled key having their hashes: this could make the computer refuse to boot further if say the MAC address of the network card (or the CPU serial, or the NVME serial) doesn't match what I added.
Yes, an evil maid attack could do the same to me (by removing these checks I've added and replacing them say by nops), but that would alter their hash.
And if the secure boot payloads signed with my own key first check the existence of these modules, and then verifies that their signature (kept inside my signed payloads matches) my versions (and not the evil maid or the manufacturer original) I'd still get the benefits of secureboot - just with my own keys all the way down.
It's because tpms are small and have small storage. The outrageous "its a secret cabal" voices are a prime example of what people cook up when faced with something they cant explain due to ignorance but feel the need to have an answer. Its as outrageous as a Republican saying "Q did it."
Wondering if something was requested by law enforcement isn't implying a cabal, chill.
Also a couple kilobytes of flash costs basically nothing. And you could hash keys over a certain length, which is much better than having such a short limit on a human-typed string.
A couple of kilobytes of flash also doesn't come with the protections the tpm offers (or at least is supposed to offer, considering the article in the OP)
If you'd like to provide schemata, open standards and source code for them, then don't keep the class waiting.
Don't/can't? Then you're a fool trusting someone else to do something you yourself cannot inspect. Then again, most people seem to be oddly fine with that. I am not of that number.
>to allow the British secret service to eavesdrop more easily. The British proposed a key length of 48 bits, while the West Germans wanted stronger encryption to protect against East German spying, so the compromise became a key length of 54 bits
>Documents leaked by Edward Snowden in 2013 state that the NSA "can process encrypted A5/1"
Why? The FBI pitched a fit over access to a shooter’s phone in the press a few years ago, then stopped.
Now, you have a multiple products on the market that can crack passcodes by utilizing flaws that allow you to brute force PINs, which are by default 6 digit numbers. (Despite most guidance demanding 8)
I have no idea if anyone has covered it. It's industry knowledge. Source: me
I figured it would be generally known at this point, especially with the whole perceptual hash debacle (intended to satisfy LEAs despite the plan to finally enable image encryption). I'm not sure what the internal politics looked like after the perceptual hash snitch got axed - my friends who would know quit Apple by then.
Any key strength limitation is mandated by... certain forces. This is not a secret (anymore). "If anything in consumer tech can be weakened, make sure it is".
It can work yes but AMD chips didn't get GMET until Zen2 so if you leave virtualization based protection on you might see a performance hit.
From Microsoft's website:
>Memory integrity works better with Intel Kabylake and higher processors with Mode-Based Execution Control, and AMD Zen 2 and higher processors with Guest Mode Execute Trap capabilities. Older processors rely on an emulation of these features, called Restricted User Mode, and will have a bigger impact on performance.
IIRC it has more to do with that series of chip not having GMET (AMD Guest-Mode Execute Trap for NPT) which is used in Windows 10/11s virtualization based protection. Microsoft requires this option for all new PCs from their partners but you can install windows 11 and run it fine without this CPU feature (there is a performance hit if you leave virtualization based protection on though since it has to be done in software).
There is a legal difference between a state banning it and a city. States have far more powers that cities don't (unless the state delegates that power which they often do)
In this case it would not matter, the ruling says it's pre-empted by federal law.
It would still be pre-empted by federal law even if the state did it.
> If people are not allowed to transfer money anonymously, why allow them communicate anonymously?
You can do that in the US though with cash. There might be some transactions that you can't do in physical cash but that is more of a practical/convince limitation and not a legal one.