Re: [openssl-dev] [openssl/openssl] ABI compatibility 1.0.0-->1.0.1-->1.0.2

On 02/26/2017 02:10 AM, Richard Levitte wrote: > In message on Fri, 27 Jan > 2017 10:54:35 -0600, Benjamin Kaduk via openssl-dev > said: > > openssl-dev> There was some discussion about 1.0.1 being EoL on a FreeBSD > list [0], > openssl-dev> and whether it would make sense to move to 1.0.2 on

Re: [openssl-dev] [openssl/openssl] ABI compatibility 1.0.0-->1.0.1-->1.0.2

On 02/26/2017 07:26 AM, Kurt Roeckx wrote: > It's normal that you might see some symbols removed if you compare > something like 1.0.1t against 1.0.2, but it shouldn't when compared > to 1.0.2k. I agree, and figured this out at some point after I sent the initial query. Given the low interest lev

[openssl-dev] Private key size in req output

Hello, Currently the req command prints key size before generating the private key. If the key size can't be determined from the specified parameters, it prints the default value. For some algorithms (e.g GOST ones) the key bits value is fixed and can't be extracted from the parameters. In such s

Re: [openssl-dev] Participate in Code Health Tuesday (tomorrow, Feb 28th)

I'd suggest prefixing the PR subject with "code-health:" or "[code-health]", just like work in progress is prefixed "WIP:" or "[WIP]" Cheers, Richard In message <9ecbf19a-3239-440c-b874-b959b6bb9...@akamai.com> on Mon, 27 Feb 2017 14:54:09 +, "Short, Todd" said: tshort> I’m not sure us mer

Re: [openssl-dev] Participate in Code Health Tuesday (tomorrow, Feb 28th)

Ah... Well, just add "Code Health" to your PR title, and we'll do the labeling. On Mon, Feb 27, 2017 at 3:54 PM Short, Todd wrote: > I’m not sure us mere mortals can add a label to a PR... > -- > -Todd Short > // tsh...@akamai.com > // "One if by land, two if by sea, three if by the Internet." >

Re: [openssl-dev] Participate in Code Health Tuesday (tomorrow, Feb 28th)

I’m not sure us mere mortals can add a label to a PR... -- -Todd Short // tsh...@akamai.com // "One if by land, two if by sea, three if by the Internet." On Feb 27, 2017, at 5:04 AM, Emilia Käsper mailto:emi...@openssl.org>> wrote: Hi OpenSSL developers! We’re always l

[openssl-dev] Participate in Code Health Tuesday (tomorrow, Feb 28th)

Hi OpenSSL developers! We’re always looking for ways to improve code quality and pay our technical debt. This week we thought we’d run a little experiment. We declare this Tuesday (Feb 28th) Code Health Tuesday. We’ll be setting some time aside to do cleanups in the codebase. The theme is “Delete