Re: [v9.1] Add security hook on initialization of instance

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [v9.1] Add security hook on initialization of instance
Date: 2010-07-09 14:52:22
Message-ID: 20100709145222.GS21875@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Stephen Frost (sfrost(at)snowman(dot)net) wrote:
> Guess my first thought was that you'd have a database-level label that
> would be used by SELinux to validate a connection. A second thought is
> labels for roles. KaiGai, can you provide your thoughts on this
> discussion/approach/problems? I realize it's come a bit far-afield from
> your original proposal.

Something else which has come up but is related is the ability to
support a "pam_tally"-like function in PG. Basically, the ability to
lock users out if they've had too many failed login attempts. I wonder
if we could add this hook (or maybe have more than one if necessary) in
a way to support a contrib module for that.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yeb Havinga 2010-07-09 14:57:13 FYI: Ubuntu 10.04 lucid strange segfault
Previous Message Simon Riggs 2010-07-09 14:51:27 Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms().