• 0 Posts
  • 83 Comments
Joined 4 months ago
cake
Cake day: January 20th, 2026

help-circle









  • That “ready” is just typical political advertising speech. Could have been worded more carefully, but it’s forgivable. As long as the git repo and website correctly identify it as a demo/prototype, it seems fine to me. E.g. not using the security enclave is totally fine for a demo. It doesn’t affect the general protocol design. There’s a lot of hostility both to these initiatives as well as to the EU (often by different actors, there’s e.g other countries pushing for less privacy respecting mechanisms), so the clever criticism tends towards nitpicking. There’s actually merit in releasing such an ambitious project as open source and so early, which even with the nitpicking and negativity, is a good thing.







  • The government derives the token from the id, which it created and knows, so there’s no privacy loss there.

    Nothing is distributed to third parties, the third party just verifies the token with the government service and gets ok / not ok. It never sees any id data.

    In your example, how do you know that the third party is not storing the data when scanning it? And how do you deal with online services?

    The issues described in the article are serious, but not fundamental design flaws of the protocol, and it depends on how they’ve presented the app: did they say it can be used already? if it’s just a prototype it’s ok to e.g not store the token/pin in the security enclave yet. And the issues being easily found is facilitated by the project being released as open source, which is good. Not saying that everything is perfect, and there might be actual issues with the protocol, but this isn’t it. It’s in any case better than having to share your id with N third parties.