Re: Replace current implementations in crypt() and gen_salt() to OpenSSL

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Replace current implementations in crypt() and gen_salt() to OpenSSL
Дата
Msg-id CA+TgmobcvL66gFiVtdRfetRH4vR=VYk4d6k3oAxZuQfSUDa2pg@mail.gmail.com
обсуждение исходный текст
Ответ на Replace current implementations in crypt() and gen_salt() to OpenSSL  ("Koshi Shibagaki (Fujitsu)" <shibagaki.koshi@fujitsu.com>)
Ответы Re: Replace current implementations in crypt() and gen_salt() to OpenSSL
Список pgsql-hackers
On Wed, Dec 4, 2024 at 8:54 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> Looking over this again I realized it's a bit silly to fall back on FIPS_mode()
> when EVP_default_properties_is_fips_enabled isn't available since that would
> only be OpenSSL versions before 3.0 (and since we don't support 1.0.2 then no
> such version can have FIPS).  Sharing back a v3 which is what I think we should
> go with.

The comment suggests to me that if the user happened to be using
OpenSSL 1.1.1 and CheckLegacyCryptoMode() was called, the expected
outcome would be an error, but it will just return.

Am I confused?

--
Robert Haas
EDB: http://www.enterprisedb.com



В списке pgsql-hackers по дате отправления: