pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Include permissive/enforcing state in sepgsql log messages.
3+ messages / 2 participants
[nested] [flat]

* pgsql: Include permissive/enforcing state in sepgsql log messages.
@ 2022-01-12 19:23  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2022-01-12 19:23 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Include permissive/enforcing state in sepgsql log messages.

SELinux itself does this (at least in modern releases), and it
seems like a good idea to reduce confusion.

Dave Page

Discussion: https://postgr.es/m/CA+OCxowsQoLEYc=jN7OtNvOdX0Jg5L7nMYt++=k0X78HGq-sXg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/134d9746364425e437a6d8eb1e2de0f3c59bfd2b

Modified Files
--------------
contrib/sepgsql/expected/alter.out | 256 ++++++------
contrib/sepgsql/expected/ddl.out   | 810 ++++++++++++++++++-------------------
contrib/sepgsql/expected/label.out |  26 +-
contrib/sepgsql/expected/misc.out  | 178 ++++----
contrib/sepgsql/selinux.c          |  15 +-
contrib/sepgsql/sepgsql.h          |   1 +
contrib/sepgsql/uavc.c             |   1 +
7 files changed, 649 insertions(+), 638 deletions(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pgsql: Include permissive/enforcing state in sepgsql log messages.
@ 2022-01-13 13:03  Simon Riggs <simon.riggs@enterprisedb.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Simon Riggs @ 2022-01-13 13:03 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-committers@lists.postgresql.org

On Wed, 12 Jan 2022 at 19:23, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Include permissive/enforcing state in sepgsql log messages.
>
> SELinux itself does this (at least in modern releases), and it
> seems like a good idea to reduce confusion.
>
> Dave Page
>
> Discussion: https://postgr.es/m/CA+OCxowsQoLEYc=jN7OtNvOdX0Jg5L7nMYt++=k0X78HGq-sXg@mail.gmail.com
>
> Branch
> ------
> master
>
> Details
> -------
> https://git.postgresql.org/pg/commitdiff/134d9746364425e437a6d8eb1e2de0f3c59bfd2b


Is that a bug fix to be backpatched, or a new/changed feature to be documented?

-- 
Simon Riggs                http://www.EnterpriseDB.com/





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pgsql: Include permissive/enforcing state in sepgsql log messages.
@ 2022-01-13 15:13  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Simon Riggs <simon.riggs@enterprisedb.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Tom Lane @ 2022-01-13 15:13 UTC (permalink / raw)
  To: Simon Riggs <simon.riggs@enterprisedb.com>; +Cc: pgsql-committers@lists.postgresql.org

Simon Riggs <simon.riggs@enterprisedb.com> writes:
> Is that a bug fix to be backpatched, or a new/changed feature to be documented?

It'd be the latter, if sepgsql had any documentation about the
content of its log messages.  But AFAICS it doesn't (and I'm not
volunteering to add that).

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2022-01-13 15:13 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-12 19:23 pgsql: Include permissive/enforcing state in sepgsql log messages. Tom Lane <tgl@sss.pgh.pa.us>
2022-01-13 13:03 ` Simon Riggs <simon.riggs@enterprisedb.com>
2022-01-13 15:13   ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox