From: | Radoslaw Stachowiak <radek(at)alter(dot)pl> |
---|---|
To: | postgresql <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: SSL Mode |
Date: | 2002-12-23 18:59:11 |
Message-ID: | 20021223185911.GE3728@blue.alter.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
*** Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> [13:42 Mon 23.Dec]:
> > > > -rw-r--r-- 1 postgres postgres 3223 Dec 18 17:10 server.crt
> > > > -rw-r--r-- 1 postgres postgres 887 Dec 18 17:10 server.key
> > >
> > > I think it wants the private key file to be mode 600 or less --- a
> > > world-readable private key isn't very private, hmm?
> >
> > Is this a good candidate for error message improvement?
>
> Yes. I will take care of it.
and one more suggestion, as this feature is a little bit to strong IMHO.
Common practice for such files (private keys) is to make them owned by
root user and postgres group with 640 mode. Root is an example of user
which has right to change keys. group readable flag is necesary for
postgres for accessing it, while write permission is not.
its not possible to use such protection schema with current pgsql, while
protection level is the same with both solution.
.radek.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-12-23 19:31:47 | Re: locking a table |
Previous Message | Bruce Momjian | 2002-12-23 18:42:27 | Re: SSL Mode |