zlacker

[return to "Web Environment Integrity API Proposal"]
1. reacto+1[view] [source] 2023-07-21 18:09:43
>>reacto+(OP)
tl;dr: DRM for websites
◧◩
2. PaulHo+W2[view] [source] 2023-07-21 18:23:13
>>reacto+1
It looks very similar to the “secure boot” mechanisms in Windows and other commercial client OS.

Strikes me as very dangerous though on the web where there are so many paths for malware to get in and this could get in the way of plugging the holes.

◧◩◪
3. saurik+59[view] [source] 2023-07-21 18:50:01
>>PaulHo+W2
It was also dangerous for your PC: as soon as people ceded the ability to led their parties control what we run on our devices--such as by "only firmware signed by Apple can run on my phone"--we lost this war.
◧◩◪◨
4. cesarb+2g[view] [source] 2023-07-21 19:22:04
>>saurik+59
> It was also dangerous for your PC: as soon as people ceded the ability to led their parties control what we run on our devices--such as by "only firmware signed by Apple can run on my phone"--we lost this war.

If that's how "we lost this war", then it was lost before it even started. Even before Apple released their phones, it was already the case that phone firmware came only from the phone manufacturer. That is: phones come from a different lineage than PCs, and were never as open as general purpose computers ended up being.

◧◩◪◨⬒
5. saurik+WJ[view] [source] 2023-07-21 21:35:27
>>cesarb+2g
I mean, those were by and large fixed function devices and while phone calls are certainly a form of communication they aren't really networked devices. And... while it was technically possible to update the software on them, most people never did.

There were only a scant handful of years where there even existed phones where this could matter... but now this same mentality is being applied to every new category of device--all of which acting as general computing devices--based on these precedents.

[go to top]