From: Bernd Helmle <mailings@oopsware.de>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Modern SHA2- based password hashes for pgcrypto
Date: Thu, 02 Jan 2025 16:17:40 +0100
Message-ID: <aac1015d45ec98b2cf0ed1fdd2e05a2ee7b07736.camel@oopsware.de> (raw)
In-Reply-To: <EB28D69B-3EA2-4A75-9ED0-7C8604941383@yesql.se>
References: <c763235a2757e2f5f9e3e27268b9028349cef659.camel@oopsware.de>
<EB28D69B-3EA2-4A75-9ED0-7C8604941383@yesql.se>
Am Donnerstag, dem 02.01.2025 um 15:57 +0100 schrieb Daniel Gustafsson:
> > I adapted the code from the publicly available reference
> > implementation
> > at [1]. It's based on our existing OpenSSL infrastructure in
> > pgcrypto
> > and produces compatible password hashes with crypt() and "openssl
> > passwd" with "-5" and "-6" switches.
>
> Potentially daft question, but since we require OpenSSL to build
> pgcrypto, why
> do we need to include sha2 code instead of using the sha2
> implementation in
> libcrypto? How complicated would it be to use the OpenSSL API
> instead?
Not sure i got you, but i use OpenSSL and the SHA2 implementation
there. See the pgcrypto px_* API (px.h and openssl.c respectively) i am
using to create the digests.
Thanks,
Bernd
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: mailings@oopsware.de, daniel@yesql.se
Subject: Re: Modern SHA2- based password hashes for pgcrypto
In-Reply-To: <aac1015d45ec98b2cf0ed1fdd2e05a2ee7b07736.camel@oopsware.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