2016-09-05, 12:56
Any project using current LibreSSL with Linux 32-bit is going to have this issue, which includes new OpenELEC builds. It's an issue for LibreSSL/Linux to sort out between themselves. Not using LibreSSL on Linux is of course an option, but not a decision we'll be taking overnight - there are sound reasons not to use OpenSSL anymore, and flip-flopping back and forth between LibreSSL and OpenSSL every time there's an issue is not really a workable solution.
Since Linux isn't going to change it's 32-bit ABI any time soon to support 64-bit time_t, the only solution is for LibreSSL to implement their own time routines (as OpenSSL already does) but I suspect a degree of anti-Linux/pro-OpenBSD developer ego is manifesting itself here.
Since Linux isn't going to change it's 32-bit ABI any time soon to support 64-bit time_t, the only solution is for LibreSSL to implement their own time routines (as OpenSSL already does) but I suspect a degree of anti-Linux/pro-OpenBSD developer ego is manifesting itself here.