https://bugs.kde.org/show_bug.cgi?id=473325
Bug ID: 473325
Summary: Display QR code for UK RSP-6 tickets as-is on
itinerary
Classification: Applications
Product: KDE Itinerary
Version: unspecified
Platform: Android
OS: Android 12.x
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: vkra...@kde.org
Reporter: yogesh-...@tuta.io
Target Milestone: ---
Created attachment 160928
--> https://bugs.kde.org/attachment.cgi?id=160928&action=edit
Screenshot of QR decoder app showing contents of both Aztec codes
SUMMARY
The UK uses a custom rail ticket information encoding format RSP-6 which KDE
itinerary correctly decodes into passenger and travel information. However KDE
itinerary adds "aztec" in front of the ASCII contained in the Aztec 2D barcode
before it recodes the ASCII into an Aztec 2D barcode displayed on the app. This
makes ticket validations fail since the original QR code does not match with
the KDE itinerary generated QR code.
I used a qr code decoder app to compare the contents in both the original Aztec
and the one generated by itinerary. Screencast attached.
STEPS TO REPRODUCE
1. Scan a UK railway ticket from a booking app like "trainline".
2. Compare QR code from the app as well as KDE itinerary
3. Observe that they don't visually look the same and that their contents
differ
OBSERVED RESULT
Contents of the original Aztec code and the one displayed on KDE itinerary are
not identical. Contents in Aztec code displayed in KDE itinerary are prefixed
with the string "aztec"
EXPECTED RESULT
Contents of the original Aztec code and the one displayed on KDE itinerary must
be identical.
ADDITIONAL INFORMATION
Since the Contents of the Aztec code are actually a representation of
cryptographically signed information, they have to be reproduced exactly.
Screenshot attached
--
You are receiving this mail because:
You are watching all bug changes.
