-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 support seems easy #31
Comments
Hi @drwetter , thanks for your request. The last time I tried a number of IPv6 patches for the openssl fork, and they all caused issues on the Windows platform. They weren't cross-platform compatible. Cheers, Peter |
Can't tell for Windows but FYI: Just did successfully on FreeBSD 9.3 a testssl.sh run (patch not yet committed) against ipv6.google.com -- with an older version of your tree and the FC IPv6 patch. |
Note: This branch is EXPERIMENTAL and does not compile/works on MSYS / Windows (yet).
Thx Peter! Any clues why it fails on your platform? No chance for one PM fork? ;-) Anecdote: I patched the FC patch myself before. As the rejects / compile errors came through the change of 1st RFC is almost 20 years ago, see https://tools.ietf.org/html/rfc1883 . |
Hi @PeterMosmans, to be honest: not yet. Any difference to the FC patch plus the fixes necessary because of the changes of the proxy option in SSL? The whole history of IPv6 in OpenSSL is sad. LibreSSL seems more advanced -- no wonder networking is higher valued of BSD folks. They do other things different though. BTW: Also an IPv6 proxy works there. Have only looked into the Linux/BSD tar ball of LibreSSL yet. They have a different one for windows. Will of course stay tuned whatever good happens in your fork ;-) Cheers, Dirk |
Hi Peter.,
there were several tries to get s_client and s_server fully(?) support Ipv6.
http://pkgs.fedoraproject.org/cgit/openssl.git/plain/openssl-1.0.2a-ipv6-apps.patch applies smoothly to your fork and I could connect e.g. to ipv6.google.com.
Cheers, Dirk
The text was updated successfully, but these errors were encountered: