From: Dominick Grift <dac.override@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: CIL: invalid protocol (dccp portcon)
Date: Mon, 28 Mar 2016 15:22:55 +0200 [thread overview]
Message-ID: <56F9302F.2060002@gmail.com> (raw)
In-Reply-To: <CAHC9VhRmUz0tJs9ZNKrV8wgrOoSNokoLz2UhVM8yArRQpjztOg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 03/28/2016 03:21 PM, Paul Moore wrote:
> On Mon, Mar 28, 2016 at 8:53 AM, Dominick Grift
> <dac.override@gmail.com> wrote:
>> 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)
>
> I'm not sure if the CIL toolchain checks /etc/protocols or if it
> uses hardcoded values, but did you check to make sure "dccp" is
> listed in /etc/protocols?
>
did'nt check, but did now. it is in there.
- --
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+TArAAoJECV0jlU3+UdpCToL/RJ7/gTd41XwLiSj3Zn7WVim
XoNXj27ULqaF2wpODpPQEtRT3ugE8VfWHbu86n25Hx1INahkd4ec0ufmZd1IDrFH
amIirVx7vVlVWQIZswAqp6Q0+rWAmaU3CegzIfqoENZnxDUmSAKsU5AuNbcA4WVL
AcZh6CiwwffgMC5buxiV3cgKT2k5gaTXa+pSe3quFU0hzHNxJMiNQJR7Qps0TSB2
QFhzFJMiYOyhbo04mLpknOaKY2G3W3HNaR5Uum/C8RR8QZemHwGaZbg51QLKCkT5
eyHbu/qdXJLZS+Hw0UCY5HqJTdHKaZVF4Pf25P3ImjpATtnmeYNH+WtLSdyxtLrs
BdvLjdl5br48mBBLJtUuIUYwCBETYWZRbiNYshQ2AjrTrHTcc/MgaILbdurJBq4c
776kr2yFODrhdwEfd0JsJJ8/AaB1DRFaGmKu/R4DxVdRIzM0ttki0LViaok5AnQ2
D/nW/jkIqJ9s1BC1AIxezN4vbWv03xTLpQZfo1R5aQ==
=EDvL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-03-28 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 12:53 CIL: invalid protocol (dccp portcon) Dominick Grift
2016-03-28 13:21 ` Paul Moore
2016-03-28 13:22 ` Dominick Grift [this message]
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=56F9302F.2060002@gmail.com \
--to=dac.override@gmail.com \
--cc=paul@paul-moore.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.