[refpolicy] what is a suitable type for /dev/cdc-wdm
dominick.grift at gmail.com
Tue Sep 27 10:33:48 CDT 2011
On Tue, 2011-09-27 at 09:17 -0400, Christopher J. PeBenito wrote:
> On 09/26/11 06:27, Dominick Grift wrote:
> > /dev/cdc-wdm 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,
> >> 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.
why are serial ttys labeled tty_device_t?
> ls -alZ /dev/ | grep ttyS
> crw-rw----. root tty system_u:object_r:tty_device_t:s0 ttyS0
> crw-rw----. root dialout system_u:object_r:tty_device_t:s0 ttyS1
> crw-rw----. root dialout system_u:object_r:tty_device_t:s0 ttyS2
> crw-rw----. root dialout system_u:object_r:tty_device_t:s0 ttyS3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: This is a digitally signed message part
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20110927/e361b0e2/attachment.bin
More information about the refpolicy