All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "James B. Byrne" <byrnejb@harte-lyne.ca>
Cc: selinux@tycho.nsa.gov
Subject: Re: Where to go for advice on local policy secuirity implications
Date: Tue, 29 May 2012 10:23:37 -0400	[thread overview]
Message-ID: <4FC4DBE9.6050305@redhat.com> (raw)
In-Reply-To: <3cc2271ab50f5f35b273260eda59d356.squirrel@webmail.harte-lyne.ca>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/28/2012 11:54 AM, James B. Byrne wrote:
> We employ a third-party Apache module (passenger aka mod-rails) to handle
> our Ruby-on-Rails web applications.  Because of the lack of SELinux
> awareness built into the module we currently run these on an isolated
> virtual host in SE permissive mode.
> 
> We are in the process of examining whether it is possible to create a local
> policy for Passenger which will allow it to run in enforcing mode but not
> open the system to other exploits. We would like to know if there is any
> on-line venue where the security aspects of specific policy elements might
> be discussed.
> 
> Is there such a resource?  If so, can anyone here provide the reference?
> 
> 
Why not just email to refpolicy list the rules you want to allow along with
the AVC's.  If there is security info you do not want to reveal, I would be
willing to look at them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/E2+kACgkQrlYvE4MpobNBpACfVdm6sAYBtuTg2L5q7p8Hzv/3
5SoAmQFChBdVOQtNR1Nwp04GHtu6Q+7c
=U0yB
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2012-05-29 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28 15:54 Where to go for advice on local policy secuirity implications James B. Byrne
2012-05-28 20:16 ` Dominick Grift
2012-05-29 14:23 ` Daniel J Walsh [this message]
2012-05-29 14:49   ` James B. Byrne

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=4FC4DBE9.6050305@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=byrnejb@harte-lyne.ca \
    --cc=selinux@tycho.nsa.gov \
    /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.