Date: Sat, 06 Sep 2014 22:42:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193083] security/sslscan incompatible with new "no-ssl2" feature of security/openssl port Message-ID: <bug-193083-13-20JqhjH6AO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193083-13@https.bugs.freebsd.org/bugzilla/> References: <bug-193083-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193083 --- Comment #2 from Leif Velcro <velcroleaf@rocketmail.com> --- I emailed the maintainer before making the bug report and got no response. Should I create a report for openssl saying the change could affect other ports that depend on it? It would be more high profile, but again I don't think maintainers of those other ports would necessarily notice, and it's not the openssl maintainer's fault, is it? Spamming every port that uses openssl and might have a problem doesn't really sound useful either. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193083-13-20JqhjH6AO>