Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2
От
Michael Paquier
Тема
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2
Дата
Msg-id
X8XW0rMv6FP2eFrr@paquier.xyz
Ответ на
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 (Daniel Gustafsson)
Список
Дерево обсуждения
scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
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 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Tom Lane <tgl@sss.pgh.pa.us>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
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 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Robert Haas <robertmhaas@gmail.com>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Daniel Gustafsson <daniel@yesql.se>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Tom Lane <tgl@sss.pgh.pa.us>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Michael Paquier <michael@paquier.xyz>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Bruce Momjian <bruce@momjian.us>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 John Scalia <jayknowsunix@gmail.com>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 Bruce Momjian <bruce@momjian.us>
Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 John Scalia <jayknowsunix@gmail.com>
On Mon, Nov 30, 2020 at 02:29:29PM +0100, Daniel Gustafsson wrote: > Yeah, that's along the lines of what I was thinking of. Hmm. I have looked at that, and thought first about having directly a reference to the resowner directly in pg_cryptohash_ctx, but that's not a good plan for two reasons: - common/cryptohash.h would get knowledge of that, requiring bundling in a bunch of dependencies. - There is no need for that in the non-OpenSSL case. So, instead, I have been thinking about using an extra context layer only for cryptohash_openssl.c with a structure saved as pg_cryptohash_context->data that stores the information about EVP_MD_CTX* and the resource owner. Then, I was thinking about storing directly pg_cryptohash_ctx in the resowner EVP array and just call pg_cryptohash_free() from resowner.c without the need of an extra routine. I have not tested this idea but that should work. What's your take? In parallel, I have spent more time today polishing and reviewing 0001 (indented, adjusted a couple of areas and added also brackets and extra comments as you suggested) and tested it on Linux and Windows, with and without OpenSSL down to 1.0.1, the oldest version supported on HEAD. So I'd like to apply the attached first and sort out the resowner stuff in a next step. -- Michael
В списке pgsql-hackers по дате отправления
От: Fujii Masao
Дата:
От: tsunakawa.takay@fujitsu.com
Дата: