Hi, thanks for the note. I know a number of those issues have fixes pending upstream, many of them are due to checking of version number stuff that we really can't continue to support. - if we "pretend" to be OpenSSL we will cause more problems than we solve by getting software to test for LibreSSL, or not try to use the "version number" as any kind of indicator of features.
OpenSSH is I believe easiest solved as hanno noted by using arc4random from libressl's libcrypto - at least until OpenSSH releases a portable that will likely do the same (I expect they will simply check for arc4random existing in both libc and libcrypto, and if it is there, don't provide it, but I don't speak for the OpenSSH portable guys. You might want to check with the OpenBSD ports folks (ports@openbsd.org) who may have patches that have headed upstream for a lot of your build issues (as we have seen the same. ) On Sun, Jul 13, 2014 at 5:42 PM, hasufell <hasuf...@gentoo.org> wrote: > Just wanted to let you know that we are currently running some tests, > the results are here and are incomplete ofc: > > https://github.com/gentoo/libressl/wiki > > openssh and wget are probably the most important failures which could be > fixed by some dirty? hacks. > > Then there are a lot of 'undefined reference to RAND_egd' related failures. > > Further references (which you might already know about): > https://blog.hboeck.de/archives/851-LibreSSL-on-Gentoo.html > https://devsonacid.wordpress.com/2014/07/12/how-compatible-is-libressl/ > > will keep testing
