[stunnel-users] Could stunnel encryption be responsible for rendering the year as "4019" instead of "2019"?
A.Birchall at mdx.ac.uk
Wed Jan 9 11:03:09 CET 2019
This may be stupid question, but I'll pose it anyway!
We use stunnel to encrypt communications between library self-service kiosks and a cloud-based library system. Since switching to this cloud-based library system, the self-service kiosks have been rendering the year in item due dates as "4019" instead of "2019" printed and emailed patron library account statements. Items will actually have been checked out to the correct due date in library system, with the year displayed correctly, which library staff and patrons can see is so when they access the system directly.
We have fixed the problem with a work-around by configuring the kiosk software to only display the last two digits of the year.
So could it be the stunnel encryption algorithms that are causing "2019" to display as "4019"?
Library Systems Manager
The Sheppard Library
London NW4 4BT
Tel: +44 (0)20 8411 5235
Mob: 07765 237 570
More information about the stunnel-users