[Bug 193083] security/sslscan incompatible with new "no-ssl2" feature of security/openssl port

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193083

--- Comment #3 from Kubilay Kocak <koobs at FreeBSD.org> ---
Leif, 

I'd suggest opening an issue report specifically for security/openssl,
proposing at least an update to the SSLv2 OPTION description, perhaps warning
the user that it may break dependent ports.

If it were me, I'd also report the issue to sslscan authors, to get support for
the lack of SSLv2 upstream.

Ultimately I believe these kinds of issues will become more prevalent and
upstream projects will end up needing to support it in the long term.

You're right in your assessment that creating in-advance issues here for every
port that is affected is probably a bit too much at the moment.

In the meantime, let's try our best to nip as much of it in the bud at the root
as we can (security/openssl)

-- 
You are receiving this mail because:
You are the assignee for the bug.