So take all those "digital sovereignity" with a grain of salt. It usually means: "We want you to lower your fees".
So take all those "digital sovereignity" with a grain of salt. It usually means: "We want you to lower your fees".
When I asked the IT staff at my university years ago, they said that there are still some very old routers without IPv6 support in use. And since everything seems to work with IPv4 for the university administration, there is no money for new ones.
Passports don't know the current time and thus can't tell whether the presented certificate is within its validity range (as in a malicious attacker could feed an expired certificate as well as a fake "current time" value to make it appear valid), so why are those certificates short-lived?
It's not perfect but if you started you trip in another country with such a system and where a more recent certificate was used, your passport will deny access.
It might be doing facial recognition, but it feels too reliable for the level of facial recognition I expect a consultancy could pull off in a government contract.
But I don't quite understand what this means for other/custom curves.
For example I'm often using brainpool curves. Currently I just set the CurveParams and I'm done.
They are part of a lot of official standards (especially in Europe/Germany but also for e.g. travel documents in the ICAO standard) so I can't get around them.
Do I have to implement everything for that curves myself? That would probably be more insecure than just using crypto/elliptic.
The decision to revert to a Microsoft Platform was taken in November 2017.