From: | "Koshi Shibagaki (Fujitsu)" <shibagaki(dot)koshi(at)fujitsu(dot)com> |
---|---|
To: | 'Peter Eisentraut' <peter(at)eisentraut(dot)org>, "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | RE: Replace current implementations in crypt() and gen_salt() to OpenSSL |
Date: | 2024-02-16 11:32:44 |
Message-ID: | TYCPR01MB11684419DF410A56DE76A2CF4FA4C2@TYCPR01MB11684.jpnprd01.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Peter
Thanks for the replying
> 1. All the block ciphers currently supported by crypt() and gen_salt() are not
> FIPS-compliant.
>
> 2. The crypt() and gen_salt() methods built on top of them (modes of operation,
> kind of) are not FIPS-compliant.
>
> 3. The implementations (crypt-blowfish.c, crypt-des.c, etc.) are not structured
> in a way that OpenSSL calls can easily be patched in.
Indeed, all the algorithm could not be used in FIPS and huge engineering might
be needed for the replacement. If the benefit is smaller than the cost, we
should consider another way - e.g., prohibit to call these functions in FIPS
mode as in the pseudocode Daniel sent. Replacing OpenSSL is a way, the objective
is to eliminate the user's error in choosing an encryption algorithm.
-----------------------------------------------
Fujitsu Limited
Shibagaki Koshi
shibagaki(dot)koshi(at)fujitsu(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Koshi Shibagaki (Fujitsu) | 2024-02-16 11:35:41 | RE: Replace current implementations in crypt() and gen_salt() to OpenSSL |
Previous Message | Jim Jones | 2024-02-16 11:18:45 | Re: Psql meta-command conninfo+ |