German 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.
What if I don’t have a smartphone?
German implementation of eIDAS will require an Apple/Google account to function
171–180 of 674 posts
Re: German implementation of eIDAS will require an Apple/Google account to function
#172Earlier quoted context omitted.
The current policy trend in the EU is definitely not based on the principle of each user evaluating their own risk. On the contrary, service providers like financial institutes and identity providers have the responsibility to keep users safe, and more and more regulation will be made. The natural consequence is restricting which platforms are supported.
> The current policy trend in the EU is definitely not based on the principle of each user evaluating their own risk. Yes and if you look back this is not new. Just look at the extraordinary restrictions that apply to: - What houses you can build, - What vehicle you can drive, - What food you can grow and sell. The result is real estate has become unaffordable for younger people, our car industry is being annihilated…
Austria's courts also ruled ages ago that rooting your own device cannot be a legal reason for OEMs like Samsung to refuse warranty coverage, since you can run whatever software you want on hardware you bought.
Maybe your country sucks? Don't blame it on the EU.
Re: German implementation of eIDAS will require an Apple/Google account to function
#173Earlier quoted context omitted.
Germany is distracted with its version of “the gun debate” aka speed limits. Like every school shooting, every energy crisis brings opportunity to saturate the airwaves with shallow noise that gets people overly upset and they’ll ignore everything else. Every player on both sides is abusing this mechanic for all eternity.
Imagine we had real democracy where people vote on issues. Speed limits? Vote once every 7 years or so on it and be done with it. Same for abortion laws, drug laws, gambling laws. Have a debate, vote, come back to it in 7 years if there is public interest. Preferably vote locally on issues that can be applied locally (like speed limits/enforcement etc.). Public debate and assessing politicians and parties would be so…
So far the best modern improvement I’ve seen (and it could be further improved of course) is the increasing use of citizens assemblies.
Re: German implementation of eIDAS will require an Apple/Google account to function
#174Earlier quoted context omitted.
This feels like arguing that people wouldn't object to having a shock collar padlocked around their neck because it's not currently shocking them. You don't have to see very many moves ahead to guess what happens if you don't object. Whereas if the collar is touted as fashionable and the lock is hidden until it's engaged, now your problem is not that people don't care , it's that they don't know , which is different.
I don't think this analogy comes even close to holding water.
Re: German implementation of eIDAS will require an Apple/Google account to function
#175German 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.
What if I don’t have a smartphone?
Companies and providers (like banks) have to support it, but use is voluntary.
Check out the spec and legal framework, it actually makes sense and is open to different implementations, though you might need to certify it.
Re: German implementation of eIDAS will require an Apple/Google account to function
#176German 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.
Re: German implementation of eIDAS will require an Apple/Google account to function
#177German 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.
Why is a trusted device chain needed? It will put more trust in the potential Chinese device maker and American software companies than the user who's id is shown?
Re: German implementation of eIDAS will require an Apple/Google account to function
#178Earlier quoted context omitted.
What if I don’t have a smartphone?
You're screwed. This has been the way for a while now. You cannot exist in society without a smart phone and it's only going to get worse.
Re: German implementation of eIDAS will require an Apple/Google account to function
#179German 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.
Google has banned many accounts of genuine users. What is your fallback for such an important vital service?
Edit: but as pointed out elsewhere in the thread, Play Integrity is not the only way to do hardware attestation on Android. GrapheneOS devs have a guide: https://grapheneos.org/articles/attestation-compatibility-gu...
So avoiding proprietary Google stuff altogether is possible and we should encourage it.
Re: German implementation of eIDAS will require an Apple/Google account to function
#180German 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.