No, completely false, your distro can work with secure boot using MS's shim because you the user are too slack to use the feature properly and correctly.

You do not need any involvement from MS to securely boot Linux. In fact you shouldn't. The keys used for secure boot are under user control and user modifiable. Just follow some step by step instructions online to sign your bootloader and load your custom keys into UEFI. You can then proceed to delete Microsoft's keys rendering their shim useless.

The fun part about this, you can even do this in Windows. Yes, that's right, you can secure boot windows with your own key and delete Microsoft's from your motherboard (well partially delete, MS's key remains present for factory reset purposes, but at least it won't boot anything).

Normally I'd agree, but in this case this is the hardware working precisely as you want. A "safe" store that allows a root user to modify individual keys in flight is not safe from any software running as root privileges, and we have countless examples of malware running with rights far more privileged than the user.

This is very much the same argument as to why you don't build an encryption backdoor into chat services. If you want the system to work *against* the user, you'd implement it the way you suggest, in a way that provides no security at all. May as well just save files to the disk then and change the file persmission.

It's not the feature's fault you don't understand basic security.

Your complaint is with the application, not the security system.

You've failed to understand the concept of a secure enclave.

And yet we've "cured" several sources of cancer preventatively because people are actively researching and producing such cures. I assume you're an anti-vaxxer and haven't heard of the HPV vaccine? Or the HepB/C vaccine which eliminates one of the most common causes of liver cancer? Your UID is low enough that presumably no one has shoved a camera in your arse yet, lucky you (or unlucky depending if you're into that), but colonoscopies have basically eliminated 90% of colorectal cancer in the west. All of this based on a history of medical research.

Sorry that your conspiracy doesn't line up with real life.

A good rule of thumb is 3m^2 of radiative area per kW, and that assumes you can heat that radiative surface to the same temperature. A NVIDIA B200 has 1.2kW to dissipate.

The JWST is 6.5m across and presented an incredible engineering feat. The sunshield is 21m across and completely flexible which a radiative surface cannot be. These were true engineering feats.

The ISS is a closer example of how you can build something large with brute force. It's actually a smidge over 100m on the longest dimension, and it took 40 dedicated individual launches and cost $60bn to assemble. You could build 60 hyperscale datacentres on earth for the cost of 1 small datacentre in space.

Very few people here are experts. But most people here did pass basic physics, and a few of us have an actual interest in development of equipment for space. Point is: heat is a big enough problem that I don't ever want to deal with it, period. I'll design electronics and thermal solutions for them down here thanks.

Oh by the way, why do we measure AI datacentres in MW again?

If you mean 1minute then sure yeah I am that impatient that I hate the idea of spending 1 minute looking at a logo. I've got places to be damnit!

No the problem is that *you* don't know how to access the information. Windows provides 3 distinct ways to clear all TPM data. Your UEFI provides ways to clear TPM data. It is under *YOUR* control. The idea of each app only having access to its own information is foundational to hardware security. The fact that a root user can't access information al-a-carte is foundational to the feature, and not DRM. You still have the ability to clear it.

Do you write your password on a post-it note and stick it under the desk? Because that sounds like the type of approach you take to understanding security.

It's been possible to identify CPU uniquely for decades, even before TPU existed. Also they don't just identify the CPU. The TPU side of things is irrelevant here.

Yes. Sorry was there a question there? Or do you think the requirement to use a password for Slashdot when you sign up is some secret Slashdot corporate agenda that is being forced on you for some reasons? TPM and Secure Boot are forced on users just like every security measure in the history of the PC was, mainly because users are fucking dumb if left to secure their own systems. Hell I still remember the good ol' days of being able to turn computers on and ending up on a Windows desktop, even though Microsoft gave users a *choice* of whether to put a password on their windows account. Users are too dumb to be presented with choices.

That I agree with, but again, it has zero to do with TPM or Secure Boot, neither of which are required for blacklisting. That said precisely zero people here are talking about something offline. Valorant cannot be played offline, it's an online-only game. And unfortunately dumb fucking users shat the bed there too. Online only games without anti-cheat are a cesspool. I don't like the idea of a game being able to ban me based on my hardware, but I do like the idea of it being applied to others. Unfortunately that position is unreconcilable.

Why are you trusting anything? It sounds like you don't know what TPM / Secure boot is or how it works. You are in full control over both. You get to decide what is in the TPM (and there are many ways to clear the TPM, Windows provides 3, your UEFI provides some too). TPM is nothing more than a place to store stuff. In the absence of TPM that stuff is still stored on your computer, just typically not in a secure place, i.e. as a file somewhere on your drive.

Secure boot? That's entirely in your control as well. UEFI gives you control over which keys are allowed to boot, you can delete Microsoft's default key, you can generate new keys for your Windows installation, just as you can for your Linux boot process. The fact you don't is your own fault and akin to leaving your house key under the door mat because that's where the previous owner kept it.

The lost case is the complete misinformation that is preventing people from using these things they themselves control properly. To play with your words: It is your choice but you're not being responsible with it at the moment.

TPM 2.0 can *in theory* be brute forced in 45 minutes. For that you need access to the hardware directly without any intermediate software doing something as simple as rate limiting queries. I'm happy for you that you recognise that they broke this 10+ years ago, but quite disappointed that you don't realise this security gap was effectively closed shortly after for anything that doesn't involve taking your computer to a specialised lab to attack your credentials.
*Hint: It's not sophisticated nation states most people are protecting against.

Absolutely false. It is in full control by YOU. YOU get to decide what keys are loaded in BIOS. YOU get to decide which keys are permitted to boot. YOU get to even generate custom keys for your Windows instance. The fact that YOU left secure boot settings at default with the MS provided key preloaded in your BIOS is YOUR failing.

The only person who gave Microsoft any control is you. I'm guessing your WiFi password is your router's MAC address as well? You probably also keep your house key under the door mat right? Because that sounds like the kind of security you seem to apply. Either that or you don't have a clue how TPM works. Take your pick.

At least you're half way there. When you figure out how they work, they'll be security measurements in practice too.

The flagging goes beyond CPU, it also flags the motherboard. Microsoft has been doing this to tie windows activation to components for decades now. A like for like CPU change would trigger a windows reactivation, and that was before you even learned to spell TPU.

Well shit it's almost like Microsoft themselves are now trolling rsilvergun with a perfectly timed Windows update: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.windowslatest.com%2F...

WTF? How is us (especially me) being a Musk hater related to climate change? I still drive a non-nazi EV just fine. One that I bought with capitalistic money. That same capitalism massively reduced the energy consumption of my house, that same capitalism is the driving force for solar and decarbonisation.

I am sorry I thought you were a climate denier. I now realise you have severe mental health issues and it was not my intention to pick on someone challenged such as you. I apologise.

for space... then we have zero problem using them here on earth. Space is cold but is also a vacuum so you lose all of your ability to convectively cool and are reliant on radiative cooling alone.