Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2
Дата
Msg-id b13ac74d-7321-711d-b438-c68850922b45@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2  (Heikki Linnakangas <hlinnaka@iki.fi>)
Ответы Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2
Список pgsql-hackers
On 2020-09-24 18:21, Heikki Linnakangas wrote:
> That would technically work, but wouldn't it make the product as whole
> not FIPS compliant? I'm not a FIPS lawyer, but as I understand it the
> point of FIPS is that all the crypto code is encapsulated in a certified
> module. Having your own SHA-256 implementation would defeat that.

Depends on what one considers to be covered by FIPS.  The entire rest of 
SCRAM is custom code, so running it on top of the world's greatest 
SHA-256 implementation isn't going to make the end product any more 
trustworthy.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: proposal: possibility to read dumped table's name from file
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Custom options for building extensions with --with--llvm