Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL with SSL

From: Jose Berardo <joseberardo(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martin Münstermann <mmuenst(at)gmx(dot)de>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: PostgreSQL with SSL
Date: 2010-04-16 15:15:13
Message-ID: h2m9009a4451004160815v9e244b70u3e3bb71c5d01a986@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
Hello,



On Thu, Apr 15, 2010 at 6:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jose Berardo <joseberardo(at)gmail(dot)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
>

Thanks Tom. Your few words were a very elucidative explanation.
I thought that attacking the running server process was much more
difficult than just open a file, and the needs of someone to provide
the symmetric key which will open the private key was just a question
of trade-off (security vs availability).


-- 
Regards,

Jose Berardo
Especializa Treinamentos
www.especializa.com.br
+55 81 3465.0032

In response to

pgsql-admin by date

Next:From: Kevin GrittnerDate: 2010-04-16 16:05:32
Subject: Re: FW: More than 1 pg_database Entry for Database - Thread #2
Previous:From: Tom LaneDate: 2010-04-16 14:46:02
Subject: Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel & transaction "liberation"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group