From: Daniel J Walsh <dwalsh@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>, Joe Orton <jorton@redhat.com>,
Mark J Cox <mjc@redhat.com>,
"Fedora SELinux support list for users & developers."
<fedora-selinux-list@redhat.com>,
Nalin Dahyabhai <nalin@redhat.com>
Subject: Adding two new booleans to httpd to tighten it's security.
Date: Fri, 09 Dec 2005 15:58:14 -0500 [thread overview]
Message-ID: <4399EFE6.5040206@redhat.com> (raw)
Currently policy allows httpd to connect to relay ports and to
mysql/postgres ports.
Adding these booleans
* httpd_can_network_relay
* httpd_can_network_connect_db
And turning this feature off by default. This is going into tonights
reference policy and into FC4 test release.
If we had these turned off we would have prevented the last apache worm
virus.
This could cause problems for people who run httpd relays or have their
apache databases talking to mysql and postgres databases over the network.
You can turn the features back on by executing:
setsebool -P httpd_can_network_relay=1
or
setsebool -P httpd_can_network_connect_db=1
Will consider adding this feature to RHEL in a future update.
Comments?
Dan
--
--
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.
next reply other threads:[~2005-12-09 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 20:58 Daniel J Walsh [this message]
[not found] ` <20051212110247.GA25100@redhat.com>
2005-12-13 4:14 ` Adding two new booleans to httpd to tighten it's security Daniel J Walsh
[not found] ` <439E23F3.7090709@speakeasy.net>
2005-12-13 4:15 ` Daniel J Walsh
2005-12-13 14:46 ` Tom London
[not found] ` <439F4A13.3020701@speakeasy.net>
2005-12-14 3:31 ` Tom London
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=4399EFE6.5040206@redhat.com \
--to=dwalsh@redhat.com \
--cc=fedora-selinux-list@redhat.com \
--cc=jorton@redhat.com \
--cc=mjc@redhat.com \
--cc=nalin@redhat.com \
--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.