From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: CIL: invalid protocol (dccp portcon)
Date: Mon, 28 Mar 2016 14:53:14 +0200 [thread overview]
Message-ID: <56F9293A.6090902@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I was adding support for syslog ports, and /etc/services indicated to
me that syslog(_tls) has support for dccp protocol. So tried to add
that support in.
However when trying to specify a portcon, secilc tells me dccp is an
invalid protocol.
e.g.
(portcon "dccp" 6514 port_obj_context)
- --
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCAAGBQJW+Sk2AAoJECV0jlU3+UdpstQMALrcdpqAQIFTKpQ7qmg9HZUE
ybu/cMobCNWWE+bfXs8+emaQtbm46f4FIwXnXkfVzkH0tnUV3+XrUytsT4K1iYFs
nVZsNBUxNuNb2RgRugeIYtdq03tsY74G5YtIOjjYESES2kcuZTcA24XeVqSuqqlF
nFvx4iwGAzJ4hQmhCk3PVZfvked/7dDDDt6XA+csYsbnKRnoJLiE5Wxm6LzCF/4n
itImypngR8/rNs9CKdJk0GSfkPKV+llAzn+w+ZgqeVlb3HiHe9rtUqhe8JsVfyax
NWjNAXOE5/cUABVC1rofvs1gmbe2/vu6PTvvFHiA0dtJ4yWMgiM1Mwn2SSMjbclA
qrkzfPmOakHlWzBd8ZZzHpboLJZ7V/9BI9Wi9guZnmBhHBzHi9VNmXFH6v3zkebU
ETFGVpEzR3cbyrA8QuDkee2YQeI53cvKz79hP1gPzANpG3HrPnTiX4ooobhfZz+k
1Cr1tXwKfVqXKTBRha7T7Kv78Al341m/RxlNmHs4vQ==
=iix7
-----END PGP SIGNATURE-----
next reply other threads:[~2016-03-28 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 12:53 Dominick Grift [this message]
2016-03-28 13:21 ` CIL: invalid protocol (dccp portcon) Paul Moore
2016-03-28 13:22 ` Dominick Grift
2016-03-28 13:27 ` Stephen Smalley
2016-03-28 13:29 ` Richard Haines
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=56F9293A.6090902@gmail.com \
--to=dac.override@gmail.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.