All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bleher <bleher@informatik.uni-muenchen.de>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: postfix, spamd, cupsd all attempting name_bind to 25, 893 etc. as "reserved_port_t"
Date: Sun, 26 Sep 2004 21:07:37 +0200	[thread overview]
Message-ID: <20040926190736.GA2529@jmh.mhn.de> (raw)
In-Reply-To: <20040926171824.GD28076@lkcl.net>

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

* Luke Kenneth Casson Leighton <lkcl@lkcl.net> [2004-09-26 20:31]:
> hi, i'm using the latest cvs from sf as policy.
> 
> kernel 2.6.8.1-selinux1 also from cvs (last week).
> 
> i get cups attempting to bind to port 631 as a "reserved_port_t",
> also postfix to 25 likewise
> and spamd_t to port 783 - again to reserved_port_t.
> 
> i've made absolutely no changes to the strict policy.

You need to use checkpolicy from cvs if you want to use the cvs policy.
reserved_port_t as used in the latest policy is only supported by the
cvs checkpolicy.

Thomas

-- 
http://www.cip.ifi.lmu.de/~bleher/selinux/ - my SELinux pages
GPG-Fingerprint: BC4F BB16 30D6 F253 E3EA  D09E C562 2BAE B2F4 ABE7

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-26 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 17:18 postfix, spamd, cupsd all attempting name_bind to 25, 893 etc. as "reserved_port_t" Luke Kenneth Casson Leighton
2004-09-26 19:07 ` Thomas Bleher [this message]
2004-09-26 21:03   ` Luke Kenneth Casson Leighton
2004-09-29 11:46     ` Russell Coker

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=20040926190736.GA2529@jmh.mhn.de \
    --to=bleher@informatik.uni-muenchen.de \
    --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.