Re: Usage of the system truststore for SSL certificate validation
От
Bruce Momjian
Тема
Re: Usage of the system truststore for SSL certificate validation
Дата
Msg-id
20190928195900.GA1377@momjian.us
Ответ на
Список
Дерево обсуждения
Usage of the system truststore for SSL certificate validation Thomas Berger <thomas.berger@1und1.de>
Re: Usage of the system truststore for SSL certificate validation Ashutosh Sharma <ashu.coek88@gmail.com>
Re: Usage of the system truststore for SSL certificate validation Isaac Morland <isaac.morland@gmail.com>
Re: Usage of the system truststore for SSL certificate validation Bruce Momjian <bruce@momjian.us>
Re: Usage of the system truststore for SSL certificate validation Magnus Hagander <magnus@hagander.net>
Re: Usage of the system truststore for SSL certificate validation Isaac Morland <isaac.morland@gmail.com>
On Thu, Sep 19, 2019 at 12:26:27PM -0400, Isaac Morland wrote: > If we're going to open this up, can we add an option to say "this key is > allowed to log in to this account", SSH style? > > I like the idea of using keys rather than .pgpass, but I like the ~/.ssh/ > authorized_keys model and don't like the "set up an entire certificate > infrastructure" approach. This is actually a good question --- why does ssh do it that way and Postgres does it another, more like a web server/client. Maybe it is because ssh allows the user to create one key pair, and use it for several independent servers, while Postgres assumes the client will only connect to multiple related servers controlled by the same CA. With the Postgres approach, you can change the client certificate with no changes on the server, while with the ssh model, changing the client certificate requires sending the public key to the ssh server to be added to ~/.ssh/authorized_keys. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
В списке pgsql-hackers по дате отправления
От: Tomas Vondra
Дата: