Ticket on LibreSSL was closed as "won't fix", saying if system is 32bit it's unsafe to deal with year after 2038...
Year 2038 bug on LibreSSL 32bit regression between 2.2.x and 2.3.x · Issue #207 · libressl-portable/portable · GitHub
Any plans to switch back to OpenSSL then?
Raspberry Pi2 is a 32bit only system... So with OpenVPN server providers generating certificates valid for 30 years, we are stuck...
I have to keep a LibreELEC version from April 2016 for now...
You have certificate that is valid for more than 20 years?
Some VPN providers create OpenVPN certificates valid by default for 30 years.
I'm running:
LibreELEC (community) Version: devel-20160704210656-#0704-g822942e
on a Raspberry Pi2.
# openssl version
LibreSSL 2.3.5
I use OpenVPN, and after that version jump in April 2016, I noticed new LibreSSL 32bit version used (2.3.x) is having a year 2038 bug:
Update libressl by Kwiboo · Pull Request #204 · LibreELEC/LibreELEC.tv · GitHub
I also opened a ticket with LibreSSL:
Year 2038 bug on LibreSSL 32bit regression between 2.2.x and 2.3.x · Issue #207 · libressl-portable/portable · GitHub
Not sure what is the plan on LibreELEC side if it's a confirmed bug on LibreSSL side, either wait for a fix on LibreSSL? or maybe downgrade to latest 2.2.x?
