public inbox for [email protected]
help / color / mirror / Atom feedFrom: Daniel Gustafsson <[email protected]>
To: Bear Giles <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Follow-up on OpenSSL "engines" and "providers"
Date: Fri, 13 Feb 2026 12:42:29 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALBNtw6tVo+WekdeaZdcXFqUPGSse_NkFT-eMyKMGs4ezu+tqQ@mail.gmail.com>
References: <CALBNtw6tVo+WekdeaZdcXFqUPGSse_NkFT-eMyKMGs4ezu+tqQ@mail.gmail.com>
> On 29 Jan 2026, at 18:15, Bear Giles <[email protected]> wrote:
> Most importantly - giving them a way to avoid knowing their private keys. They can't expose what they don't have.
FWIW there has been discussion among those of us who regularly dip our toes in
the OpenSSL support code to add some form of integration with vaults (like
vault from Hashicorp, ipa/idm from Redhat, Keychain from Apple etc) for storing
secrets. AFAIK there are no concrete patches to look at (yet?), but there is
interest and it will most likely be discussed at PGConf.dev in case you are
thinking of attending.
--
Daniel Gustafsson
view thread (4+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Follow-up on OpenSSL "engines" and "providers"
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox