Login
You're viewing the functional.cafe public feed.

Replies

  • Oct 22, 2026, 4:14 PM

    As I'm getting several "But there is…" messages, thanks for the input! All very interesting developments, (seriously) - and let me add yivi.app/en/eidas2/ .

    I'm aware that it is theoretically possible to build an alternative wallet and such projects exist. My point is though that the EU must shift their defaults from "iOS and Google" is enough if we want to get anywhere.

    💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 22, 2026, 11:54 AM

    @agx The mindset is terrible here "Let's create a spec that will work well with iOS/Android" instead of "Let's create a spec iOS and Android will have to implement"

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 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
  • 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
  • Oct 22, 2026, 8:07 PM

    @agx Yivi is indeed very interesting.

    Unfortunately there is this closed issue:

    github.com/privacybydesign/irm

    "To address your specific request (a Librem 5 / Linux phone build, ideally as a Flatpak): unfortunately we don't have the funds to also support Linux desktop / Linux phone apps, and we have not done any research into the technical difficulties of running Flutter on Linux either."

    💬 1🔄 0⭐ 0
  • 💬 0🔄 1⭐ 0
  • Oct 23, 2026, 5:54 AM

    @agx totally agree: public and health care digital access must be implemented in an open, auditable, platform-independent way or else remain an option, not the norm.

    💬 0🔄 0⭐ 0
  • Oct 22, 2026, 5:42 PM

    @agx there is only one question :

    Does it depend on Remote Attestation?

    If yes, this is anticompetitive and unethical (and fundamentally incompatible with open source since it removes the freedom to modify). Then there is nothing we can do on the technical side, this is a political fight about democracy, freedom and competition. We must ban Remote Attestation (except for few internal use case like server-to-server attestations).

    If no, then it's all good we can always re-implement the spec

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