From: antoine <antoine@nagafix.co.uk>
To: SELinux <selinux@tycho.nsa.gov>
Subject: 'name_connect' undefined!
Date: Tue, 21 Jun 2005 23:58:30 +0100 [thread overview]
Message-ID: <1119394710.9416.23.camel@localhost> (raw)
On a x86 box running Gentoo SELinux profile , I cannot 'emerge sync' (in
enforcing mode): I get the following error message:
audit(1119487194.838:0): avc: denied { name_connect } for dest=873
scontext=root:sysadm_r:portage_fetch_t
tcontext=system_u:object_r:rsyncd_port_t tclass=tcp_socket
audit2allow gives me:
allow portage_fetch_t rsyncd_port_t:tcp_socket name_connect;
Which would make sense, except that 'name_connect' is not defined
anywhere! (and therefore I cannot compile the policy with that value)
So I tried allowing connect, name_bind and so on, but the audit message
is still coming up. Where does this 'name_connect' come from if it is
not in my policy source tree? (and how do I fix it)
Why this is not part for the default policy, I do not understand.
portage_fetch_t is the domain used by portage for fetching things via
rsync (and rsync is the main fetch method - webrsync being the other):
domain_auto_trans(portage_t, rsyncd_exec_t, portage_fetch_t)
Thanks
Antoine
--
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-06-21 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 22:58 antoine [this message]
2005-06-21 23:25 ` 'name_connect' undefined! Stephen Bennett
2005-06-22 11:42 ` Stephen Smalley
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=1119394710.9416.23.camel@localhost \
--to=antoine@nagafix.co.uk \
--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.