Earlier quoted context omitted.
Relying on open protocols to make all the difference is much more potent hopium than what GP wrote. Open protocols are kind of thing techies do when in cooperative mode, when industry isn't looking. But this is not this kind of problem - this is an economic, geopolitical problem. It's not about your local school moving off Windows to Linux, it's about the European corporations moving off Azure to some other cloud sol…
> It's not about your local school moving off Windows to Linux, it's about the European corporations moving off Azure to some other cloud solution offered by European corporations (do we even have any?). But why is it about that? Why isn't it about e.g. governments in Europe funding the development of Linux virtualization so that it's simple to buy some hardware, put it in the back office and have an interface to it…
German implementation of eIDAS will require an Apple/Google account to function
651–660 of 674 posts
Re: German implementation of eIDAS will require an Apple/Google account to function
#652Earlier quoted context omitted.
Government services are going to drop support for the old scheme the minute they start supporting the new one.
Sure, that's why they stopped receiving paper letters for tax declarations once they setup Elster. Oh, wait, they didn't, my bad. You can still declare your taxes with good old paper. The only people that can't are self employed, and that's because they have a different set of obligations with higher demands
Your comment compares a paper-based, non-digital process with a digital one. My criticism, however, is about abandoning an old digital (but vendor-neutral and inclusionary) process in favor of a new (and discriminatory) one.
Re: German implementation of eIDAS will require an Apple/Google account to function
#653Earlier quoted context omitted.
It's an EU thing, overcomplicated an not sovereign: https://ec.europa.eu/digital-building-blocks/sites/spaces/EB...
Oh dear, web 3.0, blockchain. Do we get our sovereign monkey NFT too?
Re: German implementation of eIDAS will require an Apple/Google account to function
#654ISO7816 (smartcard) has existed for nearly 4 decades as the standard secure identity card, widely used by the banking industry among others. Very unintrusive and not hostile beyond needing to carry a little chip. If governments want a national ID, they could just give everyone one of those.
Re: German implementation of eIDAS will require an Apple/Google account to function
#655Earlier quoted context omitted.
> An app should have absolutely no way of knowing what kind of device it’s running on or what changes the user has made to the system. and therefore the app cannot give a reasonable guarantee that it is not running in an adversarial environment that actively tries to break the app's integrity. Thus, the app cannot be used as a verified ID with governmental level of trust.
If your app needs to be protected from harm, it cannot protect the user from said harm. I hoped software engineering culture was lucky to not have the same precepts that make lockpicking a crime in the real world, that we successfully make it into common knowledge that you can't grant any trust to the client, but it seems "trusted computing" is making some of us unlearn that lesson.
"common knowledge that you can't grant any trust to the client" is the exact reason it annoys me so much when peoples solution to cheaters in video games is basically just "Rootkit my pc please"
As long as the anticheat is Client sided, you shouldnt put trust in it.
Re: German implementation of eIDAS will require an Apple/Google account to function
#656Re: German implementation of eIDAS will require an Apple/Google account to function
#657Earlier quoted context omitted.
Why not just have the Secure Enclave in the ID card and use NFC to communicate with it? Think about it, you literally have dozens of computers between you and the provider. Routers, middleboxes, load balancers, servers etc, all insecure or untrusted, but somehow my device needs to have their special rootkit and hardware DRM. A separate device that can be provisioned with ID is the least to ask. If the government does…
This is exactly what the ID cards I'm talking about are. You tap them to the phone or a desktop reader and it works. You just invented something that already exists. eIDAS just takes this one step further and gives you an option to not have to carry your card with you. But if you refuse to have an attested phone, then you pay those 20EUR to get the ID card (which you probably need for other uses as well) and move on…
Great, thanks for clarifying. Please be mindful not everyone are domain experts and we’re all (hopefully) trying to learn.
Now, do you know whether ID cards will work with the proposed German system for e2e online ID verification? My understanding from comments was that it doesn’t, and providers are free to require the app-based version.
In Sweden we have an app-based system now (BankID), and afaik there are no alternatives that work reliably. You have to buy an American phone every few years to participate in basic societal functions. However, the government is ”looking into” decoupling digital identity from (1) banks and (2) mandatory hardware manufacturers (iOS/Android).
Re: German implementation of eIDAS will require an Apple/Google account to function
#658German implementer here. We have to use some kind of attestation mechanism per the eIDAS implementing acts. That doesn't work without operating system support. The initial limitation to Google/Android is not great, we know that, and we have support for other OSs on our list (like, e.g., GrapheneOS). It is simply a matter of where we focus our energy at the moment, not that we don't see the issues.