> > Just a quick comment: OpenSSL's libs under ".openssl/" isn't a > result of OpenSSL's behaviour, but rather a result of "make > install" nginx calls (and the ".openssl" install prefix it > instructs OpenSSL to use). >
maybe we can have a --with-libressl=/path/to/libressl or something more generic soon? i think libressl/boringssl are here to stay > > # Summary > > > > It works. > > > > While it is not recommended to substitude OpenSSL with LibreSSL in > this > > early stage, i wanted to test if it is possible. And it is. There > are no > > functional or performance-issues, as far as i can test, and building > nginx + > > libressl is easy, once you figured out how to do it. The advantages > of using > > LibreSSL in the long run, from my point of view: > > > > - cleaner code > > Good luck! :) mission accomplished, hehe :) regards, mex Posted at Nginx Forum: http://forum.nginx.org/read.php?2,251718,251752#msg-251752 _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
