> I wouldn't go near deciding what "I don't care about". There is history to
> non-experts #ifdef'ing out code in the random number generator and it
> didn't go well. :-(
True :)
The parameter here is a user-supplied measure of the entropy being added. You
can fix it to an integral constant
On 8/11/2016 11:20 AM, Short, Todd wrote:
In such a case, I suggest #ifdef’ing out the code that you don’t care
about, and making it into a configuration option, the submitting a patch
for it.
I wouldn't go near deciding what "I don't care about". There is history
to non-experts #ifdef'ing
Commit 6f35f6deb5ca7daebe289f86477e061ce3ee5f46 in 1.0.1
--
Senior Architect, Akamai Technologies
IM: richs...@jabber.at Twitter: RichSalz
From: Scott Neugroschl [mailto:scot...@xypro.com]
Sent: Friday, August 12, 2016 3:11 PM
To: openssl-users@openssl.org
Subject: [openssl-users] CVE-2016-2177
CVE 2016-2177 notes that it applies to all versions up to 1.0.2h. Does this
mean that the fix is not applied to the 1.0.1 series (in particular 1.0.1t)?
---
Scott Neugroschl | XYPRO Technology Corporation
4100 Guardian Street | Suite 100 |Simi Valley, CA 93063 | Phone 805
583-2874|Fax 805
On 12/08/2016 07:02, Bhatt, Rakshesh 1. (Nokia - IN/Bangalore) wrote:
Hi OpenSSL team,
How can I find out if authorized_keys2 is read in Openssh version
4.x/5.x? I understand that this is deprecated from version 3.0
onwards, but release notes of version 3.0 just says that,”Future
releases
