- User Since
- May 23 2015, 5:25 PM (181 w, 4 d)
Tue, Nov 13
Mon, Nov 12
Sat, Nov 10
Update after rP484599
Thu, Nov 8
Sun, Nov 4
Refresh diff after removal of security/openssl-devel
Sat, Nov 3
Thu, Nov 1
Wed, Oct 31
Tue, Oct 30
Mon, Oct 29
Sun, Oct 28
Can I go ahead and change this throughout the ports tree?
SHLIB versions in base were changed to avoid conflicts in rS339741: Update SHLIB_VERSION_NUMBER following the OpenSSL shared library
Sat, Oct 27
Subject: security/axTLSL: Removal of WITH_HTTP(S)_PORT
For security/axTLS it looks like it set the default https port. Probably I should include changes to that port here. Will contact maintainer.
For www/apache24 it has already been removed.
Thu, Oct 25
Wed, Oct 24
Tue, Oct 23
Thanks for reporting. I have this in my local repo already, and am running Weechat 2.3 from my modified port.
Sat, Oct 20
Fri, Oct 19
Oct 15 2018
Oct 14 2018
www/nextcloud: Fix fresh installs
Oct 11 2018
Oct 5 2018
Oct 1 2018
Sep 30 2018
Fix is needed for i386, not amd64
Sep 28 2018
Sep 26 2018
Abandoning this review. The main objective was to have an Apache that would work with OpenSSL 1.1 (and LibreSSL 2.7+) and support for TLSv1.3. Both these objectives have been/will be met by the 2.4 branch. As for the TLSv1.3 support, the discussions on apache httpd-dev mailing-list suggest that TLSv1.3 will land in a point-release of 2.4. Outlook on 2.6.x, for which 2.5 is the development branch, are that there won't be such a release soon.
2.4.x+TLSv1.3 branch (or git slave repo if you are so inclined)
Voting/discussion thread on http-dev mailing-list
Currently TLSv1.3 support is non-functional with released browsers, the browsers only support draft-13 and or 18. Testing requires BETA, nightly or canary builds. This will soon change.