News for hackers. Stuff that matters.
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by userbinator on Saturday June 26, 2021 @08:20PM (#27647276)
The problem is that the TPM holds a secret that even the user cannot access despite being the owner.

This is a very significant win and critical to 'zero trust', which is now something the government is telling people to embrace.

If the government is really saying the equivalent of "trust us, but not the people you usually trust", that should a huge warning sign. The analogies to 1984 are disturbingly close.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Saturday June 26, 2021 @08:45PM (#27647440)
> The problem is that the TPM holds a secret that even the user cannot access despite being the owner.

Why is this a problem?

> If the government is really saying the equivalent of "trust us, but not the people you usually trust",

I don't understand what you're talking about here. There is no additional trust necessary.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by michaelmrose on Saturday June 26, 2021 @11:16PM (#27648234)
Let's say you don't want users to view foobar.com so you convince Microsoft to configure it's browser not to resolve foobar.com.

No problem the users install their own browser.

Now we ask Microsoft to limit software that is signed by it effectively granted permission to run some software but not others. The alternatively browser is right out.

The user installs his own OS now we ask Dell to only allow it's computers to boot software that implements the same restrictions as Microsoft has agreed to.

So the user gets his own computer. Now we simply ask your bank or better yet your ISP not to connect to "insecure" devices that don't follow the standards described.

Now you need a substantial unlatched vulnerability to be able to resolve foobar.com

At it's root to make a users own device effectively restrict what they are allowed to do you need something difficult to defeat that you control and they do not.

At one point a us senator wanted this used to allow music labels to remotely destroy users computers if they believed that you were pirating music and every other restriction described has been implemented or discussed using on user devices belonging to users and most implemented.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Sunday June 27, 2021 @12:10AM (#27648513)
You can access TPMs on Linux just fine so this entire "but then what if" chain kinda makes no sense. A TPM restricts nothing on its own, it's just a hardware crypto token.

I mean sure, if Microsoft decided that it wanted to do all of the things you said, and could convince all of the OEMs to help, and a bunch of services and ISPs or whatever, yes, that would suck. It's a totally fabricated hypothetical that would never play out, but sure.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by shadilay on Sunday June 27, 2021 @01:47AM (#27648934)
Linux is "insecure", Society^TM supports Windows only, please install Windows to continue using Bank^TM, School^TM, and irs.gov. 'Legacy' tax paying is now unsupported, please use new and improved windows.irs.gov
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by michaelmrose on Sunday June 27, 2021 @05:01AM (#27649854)
Worse Ubuntu is "insecure" please upgrade to Microsoft Linux 2024.
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by shadilay on Sunday June 27, 2021 @10:38AM (#27651913)
Worse, now that WSL2 exists why would you want to run Linux on baremetal anyways. EEE
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by michaelmrose on Sunday June 27, 2021 @02:56PM (#27654189)
When trusted computing was first discussed everything but the "trusted" browser blocking a particular website was discussed as a feature not a threat model and you can absolutely see how many consumer devices are currently locked down in just such a fashion.

Accessing the tpm doesn't mean what you think it means. You can't by design get the key out of the tpm nor necessarily control which keys are trusted by local software nor remote machines.

Control of what software is allowed to run is ultimately control over everything else because one kind of control gives you every other variety. The fact that you can disable secure boot or control which keys are trusted is a nicety that could be withdrawn next year along with your ability to run Linux.

Your vendor approved software can then implement any sort of restrictions it pleases and remotely attest to the efficacy of such restrictions.

Yes sir mr Amazon sir user id running trusted windows 11 and can't save or share this video as per your contract with Disney nor are they allowed to view any known pirate sites or sites that look like pirate sites according to our heuristics.

Alternatively. Please upgrade to a trusted windows 11 machine to view this content.

https://www.gnu.org/philosophy/can-you-trust.en.html

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Sunday June 27, 2021 @11:31PM (#27657812)
> You can't by design get the key out of the tpm nor necessarily control which keys are trusted by local software nor remote machines.

I know this... I've even repeatedly stated as such in this thread.

The rest of your post is just a silly hypothetical and frankly linking gnu is just discrediting.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by michaelmrose on Monday June 28, 2021 @12:22AM (#27658115)
It's not silly hypothetical there have already been devices that used secure boot to lock out alternative OS and allowing third parties a say in what software is run is literally the entire point of remote attestation.

The last sentence is particularly disappointing. The article's analysis is correct and not particularly complicated it stands on its own regardless of whatever bias you possess.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Monday June 28, 2021 @02:25AM (#27658695)
Let's not throw words like 'bias' around when linking to Stallman.

> allowing third parties a say in what software is run is literally the entire point of remote attestation

No it isn't.

We're clearly of two very different minds, there's no way we're finding common ground on this, and I've already done the work of explaining to many people what TPM technology is, so I feel like I've done my part.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by josefx on Sunday June 27, 2021 @03:08AM (#27649313)
There are quite a few computers already where Linux only runs as long as Microsoft provides a signed shim for the boot loader. There was quite a bit of a controversy because of this when secure boot came out.
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Sunday June 27, 2021 @04:02AM (#27649567)
Really? Which computers? I don't know of any. To my knowledge the entire secure boot thing was blown way out of proportion - Linux users still can install Linux, they can even sign their own bootloaders.
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by josefx on Sunday June 27, 2021 @12:31PM (#27652942)
At least HP sold some where it seemed to intentionally disable setup mode for consumer grade hardware[1]. Arm based Surface devices where locked down to WindowsRT using secure boot[2]. The WindowsRT case was basically the foundation of the outrage, not only did Microsoft claim to not abuse its position as only entity able to sign code that would run on nearly all secure boot enabled devices, it immediately released a secure boot enabled product that locked out Linux.

[1]https://superuser.com/questions/1024111/adding-keys-to-secur...

[2]https://www.mickaelwalter.fr/linux-on-surface-rt/

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Sunday June 27, 2021 @06:40PM (#27656147)
> not only did Microsoft claim to not abuse its position as only entity able to sign code that would run on nearly all secure boot enabled devices

???

And how is HP fucking their eufi up a Microsoft problem?

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by josefx on Monday June 28, 2021 @02:27AM (#27658702)
> And how is HP fucking their eufi up a Microsoft problem?

My claim was that there where computers where Linux only ran with Microsofts signature. I listed two systems (HP/Surface) where this is the case. Mainly because finding more is a pain, with support requests more likely to go off to nowhere instead of outright showing that no support for it exists.

One might make the case that Microsoft claimed it would require the ability to add alternative keys and conveniently failed to enforce that claim. If the goal was to blame Microsoft instead of just showing that Secure Boot can be easily used to lock users into one top down approved system.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by fomine3 on Monday June 28, 2021 @12:30AM (#27658143)
IIRC MS forced lock out for Windows RT ARM devices, but oppositely forced not to lock out for Windows 8 x86 devices.
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by michaelmrose on Sunday June 27, 2021 @03:01PM (#27654232)
Not to do the 2021 version of Godwining the discussion but this is like getting vaccinated and concluding covid was overblown.

There is absolutely at least some money to be made locking down machines and corporate America would sell our kidney's for a quarter if they could get away with it.

There would likely have been lawsuits against Microsoft if they had taken further steps on that road but that doesn't mean they won't be interested in boiling us all slowly now or in the future.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by michaelmrose on Sunday June 27, 2021 @04:43AM (#27649768)
It's a token and the ability to attest to others that you are running software signed with a key you don't control making it the root of any effective set of controls.

Without it how do you keep someone from running whatever they please and lying to the machine on the other side of the connection?

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by tehbeard on Sunday June 27, 2021 @01:51AM (#27648956)
So if it's just a hardware crypto token, how does it work with secure boot? Just the other chips on the mobo working in concert, no OS oversight?
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Sunday June 27, 2021 @04:03AM (#27649570)
It's unrelated to secure boot.
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by michaelmrose on Sunday June 27, 2021 @05:01AM (#27649862)
It's party of an overarching set of standards called Trusted Computing.
Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by Brian_K_White on Sunday June 27, 2021 @10:25AM (#27651807)
You absolutely have to trust whoever manufactured the tpm module not to have back doors.

You have to trust every manufacturer of every other chip the same way also, and we have in fact found incredible breaches of that trust already many times over, and so it's too late to suggest it's a crazy thing to worry about.

The only saving grace with other chips is thst they are generic and at least you usually have your choice of some range of suppliers.

Will I be able to buy a laptop with an intentionally defective or fake tpm if I want, which will allow me to use modern software without trusting anyone?

Probably not. Probably plenty of Chinese manufacturers would be willing to produce them, like all the HDCP defeating hdmi switches, but probably software vendors will have some way to detect and invalidate them.

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by staticassertion on Sunday June 27, 2021 @01:39PM (#27653490)
> You absolutely have to trust whoever manufactured the tpm module not to have back doors.

Why? What would a backdoor in the TPM do?

Re:Installing Windows 11 on Legacy BIOS Without Secure Boot by LinuxBender on Monday June 28, 2021 @08:51AM (#27661260)
That would depend on future implementations. For example, should Microsoft one day decide to tie session authentication caching to TPM, then a backdoor in the TPM adds a universal chain for a state actor to log into the OS. Worried about state actors? No, but they hire contractors that I probably don't trust to keep this stuff secure. The OS could of course already have a back door, but reversing their code and finding it is higher risk than a closed access chip. I could envision a mandate to relocate the lawful intercept code from the OS to the hardware.

Another implementation could be used to tie DRM to hardware and then brick any hardware that is in license violation. Actually I can think of many scenarios that have a unique identifier on the hardware could be used/abused by corporations.

It should be noted that I lived through a time when corporations wanted this same setup on televisions. Each TV would have a unique chip that would give corporations control over what a person could watch, or even brick their TV. This was called the V-Chip. [0] And then of course, there was also the Clipper-Chip [1]. In terms of boiling frogs [2], TPM could be the base framework to slowly reintroduce the Clipper-Chip under a different name. i.e. used to boot-strap the pieces of code required to watch movies, buy things, browse the web, anything you can imagine.

[0] - https://www.popularmechanics.com/culture/tv/a19408909/20-yea...

[1] - https://en.wikipedia.org/wiki/Clipper_chip

[2] - https://en.wikipedia.org/wiki/Boiling_frog