From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: What are best practices wrt passwords? |
Date: | 2024-10-16 21:37:19 |
Message-ID: | ZxAyD07sVAE7gu1j@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 16, 2024 at 11:27:15PM +0200, Peter J. Holzer wrote:
> On 2024-10-16 09:50:41 -0700, Christophe Pettus wrote:
> > > On Oct 16, 2024, at 09:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > > I believe it depends on your platform --- some BSDen are pretty
> > > permissive about this, if memory serves. On a Linux box it seems
> > > to work for processes owned by yourself even if you're not superuser.
> >
> > I just tried it on an (admittedly kind of old) Ubuntu system and MacOS
> > 14, and it looks like shows everything owned by everyone, even from a
> > non-sudoer user.
>
> On Linux, unprivileged users can only see the environment of their own
> processes since a *very* long time ago. Possibly even before Ubuntu even
> existed. So I'm somewhat sceptical about that. Some other Unixes were
> more permissive. I don't know what camp MacOS falls into.
Yes, I thought this was fixed long ago.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2024-10-16 21:48:47 | Re: Backup |
Previous Message | Peter J. Holzer | 2024-10-16 21:36:10 | Re: Query performance issue |