From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] add module for the entropy key daemon
Date: Tue, 27 May 2014 09:29:43 -0400 [thread overview]
Message-ID: <53849347.8020503@tresys.com> (raw)
In-Reply-To: <20140525155334.GA16988@peter.simplex.ro>
On 05/25/2014 11:53 AM, Petre Rodan wrote:
>
> Hi Chris,
>
> On Fri, May 09, 2014 at 08:33:38AM -0400, Christopher J. PeBenito wrote:
>> On 05/07/2014 05:20 PM, Petre Rodan wrote:
>>> index 0000000..d2efb55
>>> --- /dev/null
>>> +++ b/ekeyd.te
>>> +require {
>>> + type unreserved_port_t;
>>> +}
>>
>> This looks like it should be a new port type based on the rules below.
>
> well, there is no standard port for this application and there is no default set anywhere AFAICT.
> the default is to send the random stream to the local machine only, but if the user needs to send entropy to more than a box that port needs to be set via EGDTCPSocket.
>
> the man page looks like this: http://manpages.ubuntu.com/manpages/lucid/man5/ekeyd.conf.5.html
Ok, then an interface needs to be created rather than requiring the type.
>>> +term_use_unallocated_ttys(ekey_tool_t)
>>
>> Why is it using unallocated ttys?
>
> the entropy-generating device is a usb dongle and /dev/ttyACM[0-9] (tty_device_t) ends up being used as an interface between the dongle and the software.
Please add a comment about this.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2014-05-27 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 21:20 [refpolicy] [PATCH 1/1] add module for the entropy key daemon Petre Rodan
2014-05-07 21:20 ` [refpolicy] [PATCH 1/1] add ekeyd related rules Petre Rodan
2014-05-09 12:33 ` [refpolicy] [PATCH 1/1] add module for the entropy key daemon Christopher J. PeBenito
2014-05-25 15:36 ` Petre Rodan
2014-05-25 15:53 ` Petre Rodan
2014-05-27 13:29 ` Christopher J. PeBenito [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=53849347.8020503@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.