Re: Follow-up on OpenSSL "engines" and "providers"

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Bear Giles <bgiles(at)coyotesong(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Follow-up on OpenSSL "engines" and "providers"
Date: 2026-02-13 11:42:29
Message-ID: 285A986D-C9A4-40DF-9061-B084ADA2C61E@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 29 Jan 2026, at 18:15, Bear Giles <bgiles(at)coyotesong(dot)com> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2026-02-13 11:45:30 Re: Speed up COPY FROM text/CSV parsing using SIMD
Previous Message shveta malik 2026-02-13 11:41:08 Re: Skipping schema changes in publication