On Wed, 2 Mar 2016, Peter Tribble wrote:
IIRC, 1.1.0 has this change already. That's fine, as it's a new release and is
allowed
to make incompatible changes.
Yes, that is why I mentioned it.
Perhaps it is possible to tweak the library (or config file) so that
SSLv2 won't acutally be
On Wed, Mar 2, 2016 at 12:08 AM, Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> On Tue, 1 Mar 2016, Dan McDonald wrote:
>
>>
>> Bloody's fate remains up in the air. I'm contemplating removing SSLv2
>> support from bloody, and when it ships, r151018. This will require,
>> however, some g
On Tue, 1 Mar 2016, Dan McDonald wrote:
Bloody's fate remains up in the air. I'm contemplating removing
SSLv2 support from bloody, and when it ships, r151018. This will
require, however, some godawful bootstrapping, akin to the gcc
version change I did for r151015/6. Anyone who's a fan of b
In message <15079dc7-d6c8-45d1-9ca5-b7be5cb18...@omniti.com>, Dan McDonald writ
es:
>First off, I apologize for breaking pkg(5) and who-know-what else. I honestly
> didn't think SSLv2 would still be used, even just by software autoconf'ed to
>detect it.
I hit this recently with a modern Perl mod
On Tue, 1 Mar 2016 18:06:26 -0500
Dan McDonald wrote:
> Those also demonstrate pkg(5) working with latest OpenSSL. :)
>
I can confirm this working on r151014.
Thanks Dan - you deserve your good nights sleep;-)
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen
