summm

At least for DHL you need an account which is coupled to your real identity. What other kind of station do you mean that would work with fake names?

For any of those regulation attempts, the duopoly has been coming up with another countermeasure that delayed and nullified the main effect.

Remote attestation as a broadly used technology will in itself protect the duopoly. Without it, smaller competitors could just offer an alternative that is automatically compatible with the app or service ecosystem, implement compatibility layers or client software compatible to that services.

Now they can't, because even if they offered their own remote attestation service, they would need to convince every app supplier individually to explicitly support their system.

The only way to enable any kind of growing competition would be to outright abolish hostile technologies like remote attestation, bootloader lockdown and so on.

We have a mobile OS duopoly. There is nothing that can replace it in any forseeable future. Remote attestation is deeply anti-competitive, and also is exactly the mechanism used to ensure it stays this way.

yeah this is a bullshit excuse:

> The national EUDI Wallet does not need an account/login.

This is a straight lie.

> Users can use the wallet without creating any account/login. Independently of this, the App Store and Google Play Store require an account for the user to install any application.

This is not "independent". Their security architecture depends on this.

> We are aware that some users prefer alternative distribution methods. These are being looked into. Any such approach must meet the required security standards and must not compromise the integrity of the EUDI Wallet.

Their whole botched security architecture relies on remote attestation using Google Play Integrity and the Apple equivalent. And they lie straight in our face.

Of course the whole regulation was at least in Germany supported and influenced by people in a pseudo public research institute who then immediately founded the spin-off for-profit startup which got awarded the app development. It is unclear to me how deep that appearance of corruption goes, what part of the EU is in on it, and what part is just too naive.

Regarding 2. they seem to refer to this: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...

Another more important angle: GrapheneOS creates an appliance, where the user has no freedoms, in that freedom aspect not better than stock Android: The users cannot realistically change any aspect of the OS. Sure, technically they could edit the source, but then they need to compile the whole system, reset their device and lose all data, be cut off from easy updates, and additionally lose remote attestation (which GrapheneOS devs call anti-competitive when used against them, but then gladly provide a variant that inevitably will be used against users.) Users cannot wield any more power over their apps than the apps admit. They cannot patch a binary app that misbehaves. They cannot reroute the environment of that app. And so on. With AOSPs and Graphenes "security model" there is nothing in-between "dumbest user" and "full-blown developer who cannot even be a proper user of that development system". The user to "advanced user" to "power user" to "tinkerer" to dev pipeline is kept dry. Most of power-user's potential self-defense mechanisms against abusive and monopolist app and service providers are intentionally neutered by Android as well as GrapheneOS. And hopefully less so by "Linux Phones"

Gnunet was and is incredibly advanced technology, solving many problems better than most p2p systems that came after, who never bothered to even look at those ideas, and implemented worse concepts from scratch (IPFS, veilid, libp2p...) However, it is exclusively academic, and the authors let themselves be distracted too much. The system was mainly developed by grad students who mostly leave after they have completed a barely working proof of concept for their thesis. It never had enough functionality running smoothly enough to attract a meaningful community, which would have been a prerequisite for a p2p network. It is so sad.

Correction: GrapheneOS is concerned with their so called "Android security model" more than anything else, and where that security model gives guarantees to app developers and service providers that harms the user's security, they merrily side with the developer's security against the user, at best give some more or less questionable reasons why that unfortunately currently cannot be changed, and at worst insult you for suggesting anything else.

Which was not the point. Each one of these changes made it harder, not yet impossible to make a custom Android or Linux variant. The harder it is the more likely people will continue. At some point it might be too hard. Or, one of these changes will finally make all of that impossible.

Here, the Pixel 10, especially in more niche variants like Pro and with larger flash has almost disappeared from the market, or is as expensive as the equivalent Pixel 11 offers.

With direction Google has chosen to go with the Pixel 10, it might as well be that GrapheneOS will never be available on the Pixel 11. They started by not publishing device trees anymore, squashing commits in AOSP, publishing open source drivers as a tar ball dump only after the requester has entered personal data in a web form, instead of having them public in an version control system. I wonder what dumb ideas they come up with next in order to make the GrapheneOS people suffer even more.

Can you recommend some?

I think Meneth was basically correct but a bit imprecise: Boot integrity itself is only user respectful as long as the user can freely decide and change the integrity reference values, without consequences to the latter usefulness of their system. But attestation (based on boot integrity) as a principle directly contradicts "respect user ownership". This is not a question of technical feasibility, but of principle. Attestation is directed against users. The main purpose of attestation is to make sure that the local user can be forced to use a specific software (and not run other software at the same time that could influence this specific software) to access a certain remote service. Remote attestation means by definition "vendor lock", in that the vendor and their contractual partners lock and control the device's software. Therefore an attestation model that fully respects the user simply cannot exist.

So now you have the choice between two approved ROMs. Not a lot of improvement? And as soon as GrapheneOS implements something beneficial to the users that the government does not like, the approval will be taken back. That's also why GrapheneOS will probably not even think about doing that. So you want some OS functionality neither Google nor Graphene offer, you're, again, out of luck. CA is something completely different, and much more limited in what can be centrally controlled. Everybody can go to a CA, get a certificate for their domain, and use it with any server software, even with software they compiled themselves.

No, this would just require a publicly verifyable signature of the software, and the user would just choose to have their operating system verify it. No remote attestation or other hand-over-your-controls necessary.

Nope. It is still not possible to give someone else (the government, or the bank) control over your phone while at the same time run software that you alone control with higher privileges. Please don't mix that up with "is practically hard to implement because of sloppy code. Also your attacker model is still "occasional evil government agency or evil private corporation wants to crack and read your messages", while what is discussed here is more fundamental "evil government or abusive corporation controls your phone in the first place, and can just remote control it you can't use really secure apps"

My opinion: Any kind of attestation that is delivered to a non-user-controlled server about the state of a user's end device that the user (possibly using means outside of the end device) cannot change will be abused, e.g for anti-competitve purposes. I am hearing lots of arguments that grapheneOS is more secure (it is) and should therefore be included in remote attestation.

The pinning you are proposing, does it imply that there is again some certification of the "official" GrapheneOS, versus e.g. the user's own fork of GrapheneOS?

How would any of the existing proponents of remote attestation agree to anything like this, given what we consider abuse is exactly their reason of implementing it in the first place? Here, VW wants to stop use of the API by anything else than their App, in order to stop hobbyists and sell API access to commercial middle men. If the user could pin their own software's attestation or even register an arbitrary public key to cover updates, then the user would as well be able to code his own API client that just emulates the attestation. Is there any write up or discussion of the pinning you propose?

I am really not yet convinced how you want to counter the inevitable abuse that app developers and service providers will subject the user to if the OS security model gives them that kind of power over the user's end device.

The GrapheneOS supporters are not on our sides, apparently. The seem to actually like remote attestation. They just don't like that they are not in on Play Integrity. But what is won if attestation includes official GrapheneOS releases but would still otherwise be exactly the same evil stuff that takes control of the user's device?

I still am hoping that at one point they understand the full consequences of remote attestation. There are some signs they start to notice, but it's slow...

Depends. In some sense EU companies are quite afraid of the GDPR. Privacy is used in a twisted way in that argument: if any privacy relevant data is exposed to another party, and there is any incident down the line, they fear they could be made responsible. So they to block you as a user to access your own data.

Of course, if that privacy risk came from them storing and selling your data, they happily accept that, you are right in that regard.

They already add cryptographic authentication to some CAN messages, so you can't change them. It is only a matter of time until they add encryption.

This is mostly a corporate problem of risk aversion in my opinion. Some department writes down a risk assessment with a list of miniscule risks, for example of some 3rd party app backend being hacked. Or just a headline "Tinkerer hacked his car to use with his home assistant" in the local press. This list circulates, and since nobody in the middle management wants to be responsible for anything, and there is no officially approved positive use case, draconian countermeasures are drafted and constructed one by one.

Only "open" in a twisted sense, and definitely not user-controlled: Remote attestation per definition means to accept only pre-approved operating systems. If anybody builds an implementation, regardless whether it is aosp-compliant or not, this will be excluded, until the App developer or someone in the chain explicitly approves that implementation. That is the whole purpose of that technology. Including GrapheneOS in that pre-approved list just shifts power from Google and the App Developer to GrapheneOS Developers and the App Developer. Nice for GraphenOS, still bad for users and devs of any other OS variant or platform.

Their security model requires remote attestation. So, open, user-controlled platforms cannot be used. Of course some other future locked-down linux-based OS might be usable.

Another "blog" that doesn't even offer an RSS or Atom feed...

Yeah but many devices still do not support it, and if they support it, then badly, or they hide it.

There is not even a USB-Bluetooth adapter that would enable LE Audio on Linux. (Besides the hacky ones that contain a full Bluetooth stack and present as USB-Audio, but those come with their own problems.)