From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jose Berardo <joseberardo@gmail.com>
Cc: Martin Münstermann <mmuenst@gmx.de>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: PostgreSQL with SSL
Date: Thu, 15 Apr 2010 17:30:15 -0400
Message-ID: <24692.1271367015@sss.pgh.pa.us> (raw)
In-Reply-To: <j2o9009a4451004151422r4cde72f4o868d4e7017cfab5b@mail.gmail.com>
References: <201004150206.o3F26U427784@momjian.us>
<20100415074542.137300@gmx.net>
<j2o9009a4451004151422r4cde72f4o868d4e7017cfab5b@mail.gmail.com>
Jose Berardo <joseberardo@gmail.com> writes:
>>> - Is it possible to store the server.key in a ciphered file with
>> No.
> I believe that it may be a good idea, it may bring another security level,
Not really.
> Just saving the private key file inside the cluster with no privilegies for
> other users (the server suggests 0600 mask for it) is still sufficient to
> protected the key?
If someone can access that file, they can also attach to the running
server process and pull the decrypted key out of it. In any case,
providing the server with the key to decrypt the ssl key is not going
to be convenient in operation. You're not going to want to store that
key on disk are you? Do you want somebody around to manually provide
it every time the server restarts? That gets old pretty fast, when
all it's buying you is a largely-imaginary security gain.
regards, tom lane
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, joseberardo@gmail.com, mmuenst@gmx.de, bruce@momjian.us
Subject: Re: PostgreSQL with SSL
In-Reply-To: <24692.1271367015@sss.pgh.pa.us>
* 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