Login
You're viewing the functional.cafe public feed.
  • Oct 22, 2026, 3:57 PM

    @raito @agx Reference implementation requires server issuing digital ID to cryptographically verify you are running an iPhone or a Android device certified by Google (so not LineageOS, GrapheneOS, etc.)

    💬 1🔄 0⭐ 0

Replies

  • Oct 22, 2026, 4:17 PM

    @BucciaBuccia @agx i feel like there's a disconnect here: you are saying the server requires attestation, they are saying they don't want alternative OS for the ref impl, but they encourage independent impls

    unless I'm missing something, this means that they will allow attestation for the alternative impls as long as it fulfills (I assume) reasonable conditions around security and responsibility?

    💬 1🔄 0⭐ 0
  • Oct 22, 2026, 4:33 PM

    @raito @agx Most recently published document (threat model) explicitly mentions Google/Apple attestation, other documents say only when available, in other cases alternative attestation implementation are accepted, and in another one a member said it’s required. Quite a lot of contradictions in the github organization. Attestation is also embraced not so much for security but rather preventing bypasses.

    💬 1🔄 0⭐ 0
  • Oct 22, 2026, 4:48 PM

    @BucciaBuccia @raito @agx

    The answer "nothing prevents independent implementations that follow them" (i.e.
    the ARF) is factually wrong. The EU Commission backed Architecture and Reference Framework stipulates an Apple/Google lock in, apparently the Commission is really, really eager to cement this dependency on the Big Tech-duopoly. If the ARF were to change, sure, then there could be openness and diversity. But as it is today there's not only a lock-in in the reference implementation but in all live and real inplementations in all EU countries too.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0