Menu

#35 MrzInfo doesn't comply with spesification for MRZ

v1.0_(example)
closed
1
2017-06-22
2017-06-22
Arnljot
No

I work for border patrol in Norway. We observe that JMRTD fails with MRZs that have only one name.

This is an anonymized example of such an MRZ:
P<MYSABC<DEFG<HIJKLMNOP<QRS<TUV<XYZABCDEFGHI
A984726053MYS8709125M2204134880811055050<<52

This happens consistantly with all one name MRZs from Malaysia.

This is legal according to the ICAO 9303 specification for name field in MRZ. The double filler can be absent from the name field, which means that the only name in MRZ is then the primary identifier, which again might be truncated if the last character isn't a filler.

These persons who we observe that crashes in JMRTD because MrzInfo complaints that there isn't a primary identifier present all have primary identifiers that are 39 characters or more.

Discussion

  • Martijn Oostdijk

    • assigned_to: Martijn Oostdijk
     
  • Martijn Oostdijk

    Looks like MRZInfo demands that "<<" occurs as a substring in the name field and throws an IllegalArgumentException if it doesn't.

     
  • Martijn Oostdijk

    Solved in commit 1671.

     
  • Martijn Oostdijk

    • status: open --> closed
     
  • Anonymous

    Anonymous - 2017-06-22

    @Martin, thanks! This was fast. :-)

     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB