All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Postgresql labeling revisited
Date: Mon, 18 Aug 2014 10:42:13 -0400	[thread overview]
Message-ID: <53F210C5.7090607@tresys.com> (raw)
In-Reply-To: <1407846958-13370-1-git-send-email-aranea@aixah.de>

On 8/12/2014 8:35 AM, Luis Ressel wrote:
> In the following mails, I'm resending two patches which I already submittted in
> February. They were put on hold so that the developers of the postgresql policy
> could comment on it, but there haven't been any answers since.
> 
> I'd really like to see these patches included, as it's impossible for normal
> users to use the postgres client programs (e.g. psql) without them. Our
> postgresql policy is supposed to protect postgresql servers running on the host,
> not rendering the client programs inaccessible.

I don't see any problems with this, but will still give KaiGai a final
chance to comment.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  parent reply	other threads:[~2014-08-18 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 12:35 [refpolicy] Postgresql labeling revisited Luis Ressel
2014-08-12 12:35 ` [refpolicy] [PATCH 1/2] Only label administrative postgres commands as postgresql_exec_t Luis Ressel
2014-08-12 12:35 ` [refpolicy] [PATCH 2/2] Also apply the new postgres labeling scheme on Debian Luis Ressel
2014-08-14  6:59   ` Russell Coker
2014-08-18 14:42 ` Christopher J. PeBenito [this message]
2014-08-20 18:39 ` [refpolicy] Postgresql labeling revisited Christopher J. PeBenito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53F210C5.7090607@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=refpolicy@oss.tresys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.