From: Dominick Grift <dominick.grift@defensec.nl>
To: Russell Coker <russell@coker.com.au>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: unreserved_port_t
Date: Thu, 04 Mar 2021 15:18:39 +0100 [thread overview]
Message-ID: <ypjl5z27m280.fsf@defensec.nl> (raw)
In-Reply-To: <1956679.fmg26ZhMKt@liv> (Russell Coker's message of "Wed, 03 Mar 2021 21:26:37 +1100")
Russell Coker <russell@coker.com.au> writes:
> How are we supposed to write policy for programs that bind to random unused
> ports >1024? There doesn't seem to be any macro that allows binging to
> unreserved_port_t except corenet_tcp_bind_all_unreserved_ports() which is too
> permissive.
Seems like corenet_tcp_bind_unreserved_ports() is currently missing. Please
add. There is a corenet_tcp_bind_reserved_ports().
--
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6 E0FF DA7E 521F 10F6 4098
https://sks-keyservers.net/pks/lookup?op=get&search=0xDA7E521F10F64098
Dominick Grift
prev parent reply other threads:[~2021-03-04 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 10:26 unreserved_port_t Russell Coker
2021-03-04 14:18 ` Dominick Grift [this message]
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=ypjl5z27m280.fsf@defensec.nl \
--to=dominick.grift@defensec.nl \
--cc=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).