MIME-Version: 1.0
In-Reply-To: <29710.1425087618@sss.pgh.pa.us>
References: <54C8156E.1080500@BlueTreble.com>
 <CAJrrPGcFk9_svvipFJeLBrVJYOmq6uNy38NsT8jtfo6Bks5RYw@mail.gmail.com>
 <54C95C4B.2080901@BlueTreble.com> <54F09D68.2090700@2ndquadrant.com>
 <20150227165950.GP29780@tamriel.snowman.net>
 <CAFj8pRBo6n4gEQV8J72R0_iXiCa-kZ+j1Ecwk+LrjZRJFN4PhQ@mail.gmail.com>
 <20150227183236.GQ29780@tamriel.snowman.net>
 <CAFj8pRD0GmDAf-4M8U=JyuDRUn5n1W3HCbL2oaKDbasLKwU4zw@mail.gmail.com>
 <20150227195529.GS29780@tamriel.snowman.net> <12545.1425072391@sss.pgh.pa.us>
 <20150228003749.GU29780@tamriel.snowman.net> <29710.1425087618@sss.pgh.pa.us>
From: Pavel Stehule <pavel.stehule@gmail.com>
Date: Sat, 28 Feb 2015 06:27:50 +0100
Message-ID: 
 <CAFj8pRAC4m45eCupqBLG9T4o393DviFb8fcE45BPVDDmdp=LOg@mail.gmail.com>
Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>,
 Tomas Vondra <tomas.vondra@2ndquadrant.com>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary=001a11339a1c6cf8de05101f416f
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

--001a11339a1c6cf8de05101f416f
Content-Type: text/plain; charset=UTF-8

2015-02-28 2:40 GMT+01:00 Tom Lane <tgl@sss.pgh.pa.us>:

> Stephen Frost <sfrost@snowman.net> writes:
> > I understand that there may be objections to that on the basis that it's
> > work that's (other than for this case) basically useless,
>
> Got it in one.
>
> I'm also not terribly happy about leaving security-relevant data sitting
> around in backend memory 100% of the time.  We have had bugs that exposed
> backend memory contents for reading without also granting the ability to
> execute arbitrary code, so I think doing this does represent a
> quantifiable decrease in the security of pg_hba.conf.
>

The Stephen's proposal changes nothing in security. These data are in
memory now. The only one difference is, so these data will be fresh.

Regards

Pavel


>
>                         regards, tom lane
>

--001a11339a1c6cf8de05101f416f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">2015-02-28 2:40 GMT+01:00 Tom Lane <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:tgl@sss.pgh.pa.us" target=3D"_blank">tgl@sss.pgh.pa.us</a>&gt;</span>:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><span class=3D"">Stephen Frost &lt;<a hre=
f=3D"mailto:sfrost@snowman.net">sfrost@snowman.net</a>&gt; writes:<br>
&gt; I understand that there may be objections to that on the basis that it=
&#39;s<br>
&gt; work that&#39;s (other than for this case) basically useless,<br>
<br>
</span>Got it in one.<br>
<br>
I&#39;m also not terribly happy about leaving security-relevant data sittin=
g<br>
around in backend memory 100% of the time.=C2=A0 We have had bugs that expo=
sed<br>
backend memory contents for reading without also granting the ability to<br=
>
execute arbitrary code, so I think doing this does represent a<br>
quantifiable decrease in the security of pg_hba.conf.<br></blockquote><div>=
<br></div><div>The Stephen&#39;s proposal changes nothing in security. Thes=
e data are in memory now. The only one difference is, so these data will be=
 fresh.<br><br></div><div>Regards<br><br></div><div>Pavel<br></div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 regards, tom lane<br>
</blockquote></div><br></div></div>

--001a11339a1c6cf8de05101f416f--