Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 4de6e298 | 2020-10-07 16:54:18 | Mention TLSv1.3 server up front, then validator. Other minor tweaks. | ||
| 2200d29a | 2020-10-07 23:35:51 | Update ChangeLog | ||
| 77c7de8b | 2020-08-20 10:19:23 | disable some additional libtls-standalone bits | ||
| 381fc586 | 2020-08-20 09:53:08 | remove libtls-standalone, it's unmaintained libtls-standalone was originally intended to make something that could link to any other OpenSSL fork or OpenSSL itself, but I don't think there's anyone who is terribly interested in that after all, so let's clean this up. #610 may be the better solution anyway. | ||
| 8b1dc0df | 2020-10-06 01:20:25 | Fix typo :) | ||
| 3775a79f | 2020-09-20 13:37:52 | Link crypto and ssl object files directly instead of static library - Output object files list variable for libcrypto and libssl to .mk file. - Include object files list variable .mk from tls/Makefile - Link .lo files directly instead of static library for libtls. | ||
| 7b8b95a6 | 2020-08-20 09:30:21 | Configure libtls and nc(1) to statically link to libcrypto/ssl An issue that Reyk Floeter noted while building a Debian package for LibreSSL is that installing libtls along with OpenSSL causes linker issues since it will often pick up the wrong libcrypto/libssl. This change makes libtls statically link the object files it needs rather than relying on the shared libraries, effectively making libtls self-contained and able to be packaged independently. This should make it possible for other projects that also use libtls to be able to package support without requiring the target OS to ship libcrypto / libssl from LibreSSL. https://salsa.debian.org/reyk-guest/libressl/-/commit/678278df55ce866f2f363998ca690442fa786c66 | ||
| 0ef7d54f | 2020-10-05 17:08:47 | SSL_set1_host() is now documented. | ||
| 7608ded0 | 2020-10-05 17:06:19 | SSL_set1_host() is not yet exposed. | ||
| 5562731e | 2020-10-05 21:53:04 | Update ChangeLog |