It is in the #WarOnGeneralPurposeComputing that we find the cheapest and flimsiest rhetoric. Companies like Apple - and their apologists - insist that no one *wants* to use third-party app stores, or seek out independent repair depots - and then spend *millions* to make sure that it's illegal to jailbreak your phone or get it fixed outside of their own official channel:

https://doctorow.medium.com/apples-cement-overshoes-329856288d13

19/

The cognitive dissonance of "no one wants this," and "we must make it illegal to get this" is powerful, but motivated reasoning is more powerful. It is impossible to get Tim Cook to understand something when his $49 million paycheck depends on him not understanding it.

The War on General Purpose Computing has raged for decades. Computers, like the people who use them, stubbornly insist on being reality-based, and the reality of computers is that they *are* general purpose.

20/

Every computer is a #TuringComplete, universal #VonNeumannMachine, which means that it can run every valid program. There is no way to get a computer to be *almost* Turing Complete, only capable of running programs that don't upset your shareholders' fragile emotional state.

There is no such thing as a printer that will only run the "reject third-party ink" program. There is no such thing as a phone that will only run the "reject third-party apps" program.

21/

There are only laws, like the #Section1201 of the #DigitalMillenniumCopyrightAct, that make writing and distributing those programs a felony punishable by a five-year prison sentence and a $500,000 fine (for a first offense).

That is to say, the War On General Purpose Computing is only incidentally a *technical* fight: it is primarily a *legal* fight.

22/

When Apple says, "You can't install a third party app store on your phone," what they means is, "it's *illegal* to install that third party app store." It's not a *technical* countermeasure that stands between you and #TechnologicalSelfDetermination, it's a legal doctrine we can call "#FelonyContemptOfBusinessModel":

https://locusmag.com/2020/09/cory-doctorow-ip/

But the mighty US government will not step in to protect a company's business model unless it at least *gestures* towards the technical.

23/

To invoke #DMCA1201, a company must first add the thinnest skin of #DigitalRightsManagement to their product. Since 1201 makes removing #DRM illegal, a company can use this molecule-thick scrim of DRM to felonize any activity that the DRM prevents.

More than 20 years ago, technologists started to tinker with ways to combine the legal and technical to tame the wild general purpose computer.

24/

Starting with #Microsoft's #palladium they theorized a new "#SecureComputing" model for allowing companies to reach into your computer long after you had paid for it and brought it home, in order to discipline you for using it in ways that undermined its shareholders' interest.

Secure Computing began with the idea of shipping every computer with *two* CPUs. The first one was the normal CPU, the one you interacted with when you booted it up, loaded your OS, and ran programs.

25/

The second CPU would be a #TrustedPlatformModule, a brute-simple system-on-a-chip designed to be off-limits to modification, even by its owner (that is, you).

The #TPM would ship with a limited suite of simple programs it could run, each thoroughly audited for bugs, as well as secret cryptographic signing keys that you were not permitted to extract.

26/

The original plan called for some truly exotic physical security measures for that TPM, like an acid-filled cavity that would melt the chip if you tried to decap it or run it through an electron-tunneling microscope:

https://pluralistic.net/2020/12/05/trusting-trust/#thompsons-devil

27/

This second computer represented a crack in the otherwise perfectly smooth wall of a computer's general purposeness; and Trusted Computing proposed to hammer a piton into that crack and use it to anchor a whole superstructure that could observe - and limited - the activity of your computer.

This would start with observation: the TPM would observe every step of your computer's boot sequence, creating cryptographic hashes of each block of code as it loaded and executed.

28/

Each stage of the boot-up could be compared to "known good" versions of those programs. If your computer did something unexpected, the TPM could halt it in its tracks, blocking the boot cycle.

What kind of unexpected things do computers do during their boot cycle? Well, if your computer is infected with malware, it might load poisoned versions of its operating system.

29/

Once your OS is poisoned, it's very hard to detect its malicious conduct, since normal antivirus programs rely on the OS to faithfully report what your computer is doing. When the AV program asks the OS to tell it which programs are running, or which files are on the drive, it has no choice but to trust the OS's response. When the OS is compromised, it can feed a stream of lies to users' programs, assuring these apps that everything is fine.

30/

That's a very beneficial use for a TPM, but there's a sinister flipside: the TPM can also watch your boot sequence to make sure that there aren't *beneficial* modifications present in your operating system. If you modify your OS to let you do things the manufacturer wants to prevent - like loading apps from a third-party app-store - the TPM can spot this and block it.

31/

Now, these beneficial and sinister uses can be teased apart. When the Palladium team first presented its research, my colleague #SethSchoen proposed an "#OwnerOverride": a modification of Trusted Computing that would let the computer's owner override the TPM:

https://web.archive.org/web/20021004125515/http://vitanuova.loyalty.org/2002-07-05.html

This override would introduce its own risks, of course.

32/

A user who was tricked into overriding the TPM might expose themselves to malicious software, which could harm that user, as well as attacking other computers on the user's network and the other users whose data were on the compromised computer's drive.

33/

But an override also provides serious benefits: it rules out the monopolistic abuse of a TPM to force users to run malicious code that the *manufacturer* insisted on - code that prevented the user from doing things that benefited the user, even if it harmed the manufacturer's shareholders. For example, with owner override, Microsoft couldn't force you to use its official MS Office programs rather than third-party compatible programs like #iwork #GoogleDocs or #LibreOffice.

34/

Owner override also completely changed the calculus for another, even more dangerous part of Trusted Computing: #RemoteAttestation.

35/

Remote Attestation is a way for third parties to request a reliable, cryptographically secured assurances about which operating system and programs your computer is running. In Remote Attestation, the TPM in your computer observes every stage of your computer's boot, gathers information about all the programs you're running, and cryptographically signs them, using the signing keys the manufacturer installed during fabrication.

36/

You can send this "attestation" to other people on the internet. If they trust that your computer's TPM is truly secure, then they know that you have sent them a true picture of your computer's working (the actual protocol is a little more complicated and involves the remote party sending you a random number to cryptographically hash with the attestation, to prevent out-of-date attestations).

37/

Now, this is *also* potentially beneficial. If you want to make sure that your technologically unsophisticated friend is running an uncompromised computer before you transmit sensitive data to it, you can ask them for an attestation that will tell you whether they've been infected with malware.

But it's also potentially *very* sinister. Your government can require all the computers in its borders to send attestations to confirm that you're still running mandatory spyware.

38/

Your abusive spouse - or abusive boss - can do the same for their own #DisciplinaryTechnologies. Such a tool could prevent you from connecting to a service using a #VPN, and make it impossible to use #TorBrowser to protect your privacy when interacting with someone who wishes you harm.

The thing is, it's *completely normal and good* for computers to lie to other computers on behalf of their owners.

39/

Like, if your #IoT ebike's manufacturer goes out of business and all their bikes get bricked because they can no longer talk to their servers, you can run an app that tricks the bike into thinking that it's still talking to the mothership:

https://nltimes.nl/2023/07/15/alternative-app-can-unlock-vanmoof-bikes-popular-amid-bankruptcy-fears

40/

Or if you're connecting to a webserver that tries to track you by fingerprinting you based on your computer's RAM, screen size, fonts, etc, you can order your browser to send random data about this stuff:

https://jshelter.org/fingerprinting/

Or if you're connecting to a site that wants to track you and nonconsensually cram ads into your eyeballs, you can run an #adblocker that doesn't show you the ads, but tells the site that it did:

https://www.eff.org/deeplinks/2019/07/adblocking-how-about-nah

41/

Owner override leaves some of the beneficial uses of remote attestation intact. If you're asking a friend to remotely confirm that your computer is secure, you're not going to use an override to send them bad data about about your computer's configuration.

42/

And owner override also sweeps *all* of the malicious uses of remote attestation off the board. With owner override, you can tell any lie about your computer to a webserver, a site, your boss, your abusive spouse, or your government, and they can't spot the lie.

But owner override also eliminates *some* beneficial uses of remote attestation.

43/

For example, owner override rules out remote attestation as a way for strangers to play multiplayer video games while confirming that none of them are using cheat programs (like #aimhack). It also means that you can't use remote attestation to verify the configuration of a cloud server you're renting in order to assure yourself that it's not stealing your data or serving malware to your users.

44/

This is a tradeoff, and it's a tradeoff that's similar to lots of other tradeoffs we make online, between the freedom to do something good and the freedom to do something bad. Participating anonymously, contributing to free software, distributing penetration testing tools, or providing a speech platform that's open to the public all represent the same tradeoff.

45/

We have lots of experience with making the tradeoff in favor of restrictions rather than freedom: powerful bad actors are happy to attach their names to their cruel speech and incitement to violence. Their victims are silenced for fear of that retaliation.

When we tell security researchers they can't disclose defects in software without the manufacturer's permission, the manufacturers use this as a club to silence their critics, not as a way to ensure orderly updates.

46/

When we let corporations decide who is allowed to speak, they act with a mixture of carelessness and self-interest, becoming off-the-books deputies of authoritarian regimes and corrupt, powerful elites.

Alas, we made the wrong tradeoff with Trusted Computing. For the past twenty years, Trusted Computing has been creeping into our devices, albeit in somewhat denatured form.

47/

The original vision of acid-filled secondary processors has been replaced with less exotic (and expensive) alternatives, like "#SecureEnclaves." With a secure enclave, the manufacturer saves on the expense of installing a whole second computer, and instead, they draw a notional rectangle around a region of your computer's main chip and try *really hard* to make sure that it can only perform a very constrained set of tasks.

48/

This gives us the worst of all worlds. When secure enclaves are compromised, we not only lose the benefit of cryptographic certainty, knowing for sure that our computers are only booting up trusted, unalterted versions of the OS, but those compromised enclaves run malicious software that is essentially *impossible* to detect or remove:

https://pluralistic.net/2022/07/28/descartes-was-an-optimist/#uh-oh

49/

But while Trusted Computing has wormed its way into boot-restrictions - preventing you from jailbreaking your computer so it will run the OS and apps of your choosing - there's been very little work on remote attestation...until now.

50/

#WebEnvironmentIntegrity is #Google's proposal to integrate remote attestation into everyday web-browsing. The idea is to allow web-servers to verify what OS, extensions, browser, and add-ons your computer is using before the server will communicate with you:

https://github.com/RupertBenWiser/Web-Environment-Integrity/blob/main/explainer.md

Even by the thin standards of the remote attestation imaginaries, there are precious few beneficial uses for this.

51/

The googlers behind the proposal have a couple of laughable suggestions, like, maybe if ad-supported sites can comprehensively refuse to serve ad-blocking browsers, they will invest the extra profits in making things you like. Or: letting websites block scriptable browsers will make it harder for bad people to auto-post fake reviews and comments, giving users more assurances about the products they buy.

52/

But foundationally, WEI is about compelling you to disclose true facts about yourself to people who you want to keep those facts from. It is a Real Names Policy *for your browser*. Google wants to add a new capability to the internet: the ability of people who have the power to force you to tell them things to know for sure that you're not lying.

53/

The fact that the authors assume this will be beneficial is just another "#FalsehoodProgrammersBelieve": there is no good reason to hide the truth from other people. Squint a little and we're back to McNealy's "Privacy is dead, get over it." Or Schmidt's "If you have something that you don't want anyone to know, maybe you shouldn't be doing it in the first place."

54/

And like those men, the programmers behind this harebrained scheme don't imagine that it will ever apply to them. As #ChrisPalmer - who worked on Chromium - points out, this is not compatible with normal developer tools or debuggers, which are "incalculably valuable and not really negotiable":

https://groups.google.com/a/chromium.org/g/blink-dev/c/Ux5h_kGO22g/m/5Lt5cnkLCwAJ

This proposal is still obscure in the mainstream, but in tech circles, it has precipitated a flood of righteous fury:

https://arstechnica.com/gadgets/2023/07/googles-web-integrity-api-sounds-like-drm-for-the-web/

55/

As I wrote last week, giving manufacturers the power to decide how your computer is configured, overriding your own choices, is a bad tradeoff - the *worst* tradeoff, a greased slide into terminal enshittification:

https://pluralistic.net/2023/07/24/rent-to-pwn/#kitt-is-a-demon

This is how you get #UnauthorizedBread:

https://arstechnica.com/gaming/2020/01/unauthorized-bread-a-near-future-tale-of-refugees-and-sinister-iot-appliances/

All of which leads to the question: what now? What should be done about WEI and remote attestation?

56/

Let me start by saying: I don't think it should be illegal for programmers to design and release these tools. #CodeIsSpeech, and we can't understand how this stuff works if we can't study it.

57/

But programmers *shouldn't* deploy it in production code, in the same way that programmers should be allowed to make pen-testing tools, but shouldn't use them to attack production systems and harm their users. Programmers who do this should be criticized and excluded from the society of their ethical, user-respecting peers.

58/