| From: | Michael Nolan <htfoot(at)gmail(dot)com> |
|---|---|
| To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Trigger when user logs in |
| Date: | 2019-04-14 15:50:21 |
| Message-ID: | CAOzAquLkEpNcRitS5ZtBS1G0chsCUT+QYB9j23tsxFm2VLaqbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Apr 14, 2019 at 4:06 AM Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
>
> If you want to prevent a user from logging in (which is functionally
> equivalent but a bit stronger than "instantly kick off"), then this is
> definitely something that could and should be implemented via PAM (I'm
> not sure what information is passed to PAM, so you might get the IP
> address but not the application name (the latter can't be trusted
> anyway), for example).
>
> I think the only information you can reliably count on is the user name.
IP addresses may not be the true IP address of the user if there's some
kind of relay or cache in place.
Having been through the PCI compliance wringer a few times, I wish the OP
luck.
--
Mike Nolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laura Smith | 2019-04-14 19:09:57 | Where to find postgresql libs in the APT repo ? |
| Previous Message | Alastair McKinley | 2019-04-14 14:35:18 | Re: Planner can't seem to use partial function indexes with parameter from join |