Re: [PATCH] Add <<none>> support to sepgsql_restorecon

From: Ted X Toth <txtoth(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Add <<none>> support to sepgsql_restorecon
Date: 2023-01-17 14:59:02
Message-ID: 167396754287.1137.10261043173596032365.pgcf@coridan.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The intent of this patch is not to stop all relabeling only to stop sepgsql_restorecon from doing a bulk relabel. I believe sepgsql_object_relabel is called by the 'SECURITY LABEL' statement which I'm using to set the label of db objects to a specific context which I would not want altered later by a restorecon. This is particularly important in a MLS (multi-level security) environment where for example if a row were labeled at the 'secret' level I would not restorecon to relabel it possibly causing a downgrade.

The new status of this patch is: Ready for Committer

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-01-17 15:18:46 Re: Extracting cross-version-upgrade knowledge from buildfarm client
Previous Message Tomas Vondra 2023-01-17 14:52:07 Re: Sampling-based timing for EXPLAIN ANALYZE