Open lucas-it opened 2 years ago
In the light certificate only the Name, Last Name, birth date and validity of the light certificate are stored (for data protection), hence it should be impossible to use it for the 2G (no info about the type of certificate).
In the light certificate only the Name, Last Name, birth date and validity of the light certificate are stored (for data protection), hence it should be impossible to use it for the 2G (no info about the type of certificate).
Yes, I know. That's why I created an issue. I think it's possible to add a flag in the light certificate to know if it's a 2G or 3G certificate or something like this.
But that is conflicting with the scope of the light certificate, where no "sensitive" data should be stored...
But that is conflicting with the scope of the light certificate, where no "sensitive" data should be stored...
I don't know if a 2G or 3G flag is a sensitive data. But in the future, we will be forced to use the normal certificate which is even less secure to enter establishments that only accept 2G certs.
When adding a flag boolean is2G
to the light certificate and using this certificate in both 2G and 3G contexts the following problem arises: it exposes whether you are vaccinated/recovered or "only" tested.
Hiding/protecting this piece of information (alongside all the other details) is one of the advantages of the light certificate. On a social level, you could interpret this as preventing social stigma against tested persons in 3G contexts (and right now, 3G is still the default in most situations).
I hope that explains why a flag in the same certificate isn't compatible with data protection. Personally, I agree that some form of a "2G light certificate" would be nice. Unfortunately, I don't know if, how and when it might happen.
Will the light certificate be compatible with 2G ? Actually it's only compatible with 3G.