public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Question regarding OpenSSL 1.1.1b package configuration against OpenSSL 1.0.2r
Date: Mon, 03 Jun 2019 20:35:00 -0000	[thread overview]
Message-ID: <d1f44f95-0ec4-bdce-7f84-fd98a4372c84@SystematicSw.ab.ca> (raw)
In-Reply-To: <CABTpe59pFoH-MsGKKa4oNdFTs42opV64motaSFpeijJCq0Dqcw@mail.gmail.com>

On 2019-06-03 06:09, Benjamin Baratte wrote:
> I would like to understand why the OpenSSL 1.1.1b package only includes the
> NIST EC curves support ?
> I'm basically try to use brainpool curves and I have noticed that the
> package 1.1.1b does not includes these curves and more generally only
> includes NIST curves

> From what I have found in Google, the cygwin OpenSSL 1.1.1b package is
> bound to the fedora package spec which is deactivating brainpool curves.
> 
> I'm a bit surprised by the differences in the 2 OpenSSL packages. But I
> need to use Brainpool curves.
> 
> On top of that, the installer is proposing the OpenSSL 1.1.1b-1 package as
> the newest one prevailing to OpenSSL 1.0.2r-1 package. Is it possible to
> get back the brainpool curves into the OpenSSL 1.1.1b-1 package ?
> if not, could please explain to me why only NIST curves are now supported
> in the official package ?

I have seen comments about legal liability, poor performance limited by choice
of random keys, small size of random keys, another model specific Intel FP bug:

https://github.com/openssl/openssl/blob/master/CHANGES
"Montgomery multiplication may produce incorrect results

     There is a carry propagating bug in the Broadwell-specific Montgomery
     multiplication procedure that handles input lengths divisible by, but
     longer than 256 bits. ... Otherwise the bug can manifest itself as
     transient authentication and key negotiation failures or reproducible
     erroneous outcome of public-key operations with specially crafted input.
     Among EC algorithms only Brainpool P-512 curves are affected and one
     presumably can attack ECDH key negotiation. ...

     This issue was publicly reported as transient failures and was not
     initially recognized as a security issue. Thanks to Richard Morgan for
     providing reproducible case.
     (CVE-2016-7055)
     [Andy Polyakov]"

You can easily rebuild the package yourself with the cygport utility, to check
that works, then change the build config to include the Brainpool ECs, and
rebuild the way you want it.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-06-03 20:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 12:09 Benjamin Baratte
2019-06-03 20:35 ` Brian Inglis [this message]
2019-06-03 22:36   ` Steven Penny
2019-06-04 14:32     ` Benjamin Baratte
2019-06-04 15:25     ` Brian Inglis
2019-06-04 22:56       ` Steven Penny
2019-06-05  3:04         ` Vince Rice
2019-06-05  4:12           ` Steven Penny
2019-06-05  4:26           ` Houder
2019-06-05  6:24             ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d1f44f95-0ec4-bdce-7f84-fd98a4372c84@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).