On Thu, Mar 03, 2016 at 02:00:31PM -0500, Jeffrey Walton wrote:
> > Note that "no-comp" is a consequence of "zlib" and "zlib-dynamic"
> > not being enabled. You have to choose to turn compression on IIRC
> > by enabling one of these.
>
> no-comp disables compression independent of zlib. OPENSSL_
>> > By and large what should be off by default eventually or already
>> > is, but there can be some delay for backwards compatibility.
>> ...
>> > With these you're covered for no-ssl2 no-comp and no weak ciphers.
>>
>> We are using 1.0.2f, no-ssl2 and no-comp do not appear to be defaults in
>> th
On Thu, Mar 03, 2016 at 08:13:36AM -0500, Wall, Stephen wrote:
> > From: openssl-users [mailto:openssl-users-boun...@openssl.org] On
> > Behalf Of Viktor Dukhovni
> >
> > By and large what should be off by default eventually or already
> > is, but there can be some delay for backwards compatibili
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On
> Behalf Of Viktor Dukhovni
>
> By and large what should be off by default eventually or already
> is, but there can be some delay for backwards compatibility.
...
> With these you're covered for no-ssl2 no-comp and no weak cipher
On Wed, Mar 02, 2016 at 02:57:13PM -0500, Wall, Stephen wrote:
> Is there a set of recommended build options for openssl? For instance,
> "no-ssl2 no-comp -DOPENSSL_NO_HEARTBEATS no-md4 ..."
By and large what should be off by default eventually or already
is, but there can be some delay for back
Is there a set of recommended build options for openssl? For instance,
"no-ssl2 no-comp -DOPENSSL_NO_HEARTBEATS no-md4 ..."
Thanks
--
Stephen P. Wall
stephen_w...@redcom.com
(585) 924-7550
REDCOM Laboratories, Inc.
One Redcom Center
Victor, NY 14564 USA
--
openssl-users mailing list
To unsu
