pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Büttner <frank.buettner@mdc-berlin.de>
To: tgl@sss.pgh.pa.us
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: [ext] Re: BUG #16815: Unable to use the X448 an X25519 elliptic curves.
Date: Mon, 11 Jan 2021 12:39:24 +0100
Message-ID: <de48d9a6-959b-83eb-6f3e-0fd91a8d2d10@mdc-berlin.de> (raw)
In-Reply-To: <339357.1610139459@sss.pgh.pa.us>
References: <16815-0fde6075fb21923a@postgresql.org>
	<339357.1610139459@sss.pgh.pa.us>

Hi Tom,

after looking in the API of openssl, I see, that this curves use another 
API part of openssl. They use the EVP_... calls of openssl.
See https://www.openssl.org/docs/manmaster/man7/X448.html for more.

This will be the reason, why the curve is know, but an key can't created.

Am 08.01.21 um 21:57 schrieb Tom Lane:
> PG Bug reporting form <noreply@postgresql.org> writes:
>> It looks like the curves with the upper X are known, but not correct
>> initialized.
> 
> BTW, as far as that goes, I looked into the source code and found
> 
>      nid = OBJ_sn2nid(SSLECDHCurve);
>      if (!nid)
>      {
>          ereport(isServerStart ? FATAL : LOG,
>                  (errcode(ERRCODE_CONFIG_FILE_ERROR),
>                   errmsg("ECDH: unrecognized curve name: %s", SSLECDHCurve)));
>          return false;
>      }
> 
>      ecdh = EC_KEY_new_by_curve_name(nid);
>      if (!ecdh)
>      {
>          ereport(isServerStart ? FATAL : LOG,
>                  (errcode(ERRCODE_CONFIG_FILE_ERROR),
>                   errmsg("ECDH: could not create key")));
>          return false;
>      }
> 
> So it would appear that "X448" and "X25519" are known as names for
> *some* sort of thing known to OpenSSL, but they aren't ECDH curves.
> 
> 			regards, tom lane
> 


-- 
*Frank Büttner*
IT

MDC Berlin-Buch
Max-Delbrück-Centrum für Molekulare Medizin in der Helmholtz-Gemeinschaft
Robert-Rössle-Straße 10
13125 Berlin

☎ +49 30 9406 2038
℻ +49 30 9406 2599
✉ frank.buettner@mdc-berlin.de

Attachments:

  smime.p7s (application/pkcs7-signature, 5.8K) download

view thread (4+ messages)

Message-ID: <de48d9a6-959b-83eb-6f3e-0fd91a8d2d10@mdc-berlin.de>
Permalink:  ../de48d9a6-959b-83eb-6f3e-0fd91a8d2d10@mdc-berlin.de/
Also on:    postgresql.org/message-id/de48d9a6-959b-83eb-6f3e-0fd91a8d2d10@mdc-berlin.de

 · 

reply

Reply instructions:

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

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: frank.buettner@mdc-berlin.de, tgl@sss.pgh.pa.us
  Subject: Re: [ext] Re: BUG #16815: Unable to use the X448 an X25519 elliptic curves.
  In-Reply-To: <de48d9a6-959b-83eb-6f3e-0fd91a8d2d10@mdc-berlin.de>
  References: <16815-0fde6075fb21923a@postgresql.org> <339357.1610139459@sss.pgh.pa.us> <de48d9a6-959b-83eb-6f3e-0fd91a8d2d10@mdc-berlin.de>

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

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox