In 2014, a Polish driver modified their license plate to also contain an SQL injection in effort to thwart speed cameras: https://hackaday.com/2014/04/04/sql-injection-fools-speed-tr...
https://en.wikipedia.org/wiki/Driving_licence_in_Poland#Mist...
https://en.wikipedia.org/wiki/European_driving_licence
The other thing is to list out the field names in all 27/30/33 languages and flag those for double checking. Theres probably few people named "drivers license". Finally, just take a photo of the whole ID so even if the wrong value is entered initially, the right value can be recovered later as necessary.
None of that is foolproof, but it doesn't have to be 100% foolproof, just not totally broken.
I still wonder how their DB was set up to accept this data in the first place. It makes sense to allow a person to be associated with multiple addresses - people move, sometimes a lot - but a person should not under any circumstances have multiple DoBs, should it?
(Unless I missed "Falsehoods programmers believe about personal data: People are born only once" or something)
Parents did not want the baby, so they left it at the door step, date of birth was not known, so some was assigned and used in some legal documents. Later, original parents changed their minds, real date of birth became known.
(For sanity sake, I would just say choose one or flip a coin and be done with it, but at the same time I could imagine that some layer could take my sanity into account)
And this: https://toppandigital.com/translation-blog/welsh-road-sign-d...
Dariusz Jakubowski x'; DROP TABLE users; SELECT '1
I am a bit proud.