From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] what is a suitable type for /dev/cdc-wdm[01]
Date: Tue, 27 Sep 2011 09:17:56 -0400 [thread overview]
Message-ID: <4E81CD04.7080107@tresys.com> (raw)
In-Reply-To: <1317032855.9488.30.camel@x220.mydomain.internal>
On 09/26/11 06:27, Dominick Grift wrote:
> /dev/cdc-wdm[01] character device nodes are currently labeled type
> device_t:
>
>> # matchpathcon /dev/cdc-wdm0
>> /dev/cdc-wdm0 system_u:object_r:device_t:s0
>
> what would be suitable type for these devices?
>
>> CDC Device Management (2 "devices")
>> CDC Mobile Direct Line (1 "device")
>>
>> The first is supported by the cdc-wdm driver available in 2.6.29
>> (haven't checked exactly when it was added, but it is rather new).
>> It
>> will add two new devices you can send AT commands
>> to /dev/cdc-wdm[01],
>> but not do any high speed data transfers over. Quite useful, since
>> the
>> three ACM devices are easily "lost" to GPS, SMS daemon and PPP.
I'm not sure, possibly modem_device_t or a new type.
>> The CDC Mobile Direct Line is actually a masqueraded CDC Ethernet
If this is a different device node then this probably should be a new type.
>> device. Ericsson has provided a driver which is mostly a copy of
>> cdc_ether.c. Nice feature to have, but I've not been able to measure
>> any speed advantages compared to PPP on ttyACM0. Still, fun to play
>> with :-)
>
> Also, why are ACM tty character device nodes labeled type tty_device_t
> and not for example acmtty_device_t?
It would seem that modem_device_t would be a better choice, assuming all ttyACM* devices are cellular modems.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-09-27 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 10:27 [refpolicy] what is a suitable type for /dev/cdc-wdm[01] Dominick Grift
2011-09-27 13:17 ` Christopher J. PeBenito [this message]
2011-09-27 15:33 ` Dominick Grift
2011-09-27 15:42 ` Christopher J. PeBenito
2011-09-27 15:49 ` Dominick Grift
2011-10-04 12:28 ` Christopher J. PeBenito
2011-10-04 12:44 ` Dominick Grift
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=4E81CD04.7080107@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.