RE: releasibility in mcstransd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 
Seems reasonable to me unless you want to create a nice new encoding
language ;)

How would the user process translate, eg, s0:c102.c128, just s0?

-Chad 

> 
> I am adding releasibility support to mcstransd and just 
> wanted to see if there were any comments or complaints to 
> what I'm planning here.
> 
> Rather than adding a generic prefix mechanism like the CMW 
> encodings I did something specific for releasibility, in setrans.conf:
> 
> releasibility c100.c128
> 
> then encodings look like:
> 
> s0:~c100 = rel_US
> s0:~c101 = rel_Texas
> 
> so a file with s0:c102.c128 would translate to s0:rel_US,rel_Texas.
> 
> any comments? Does anyone think this is absolutely the wrong approach?
> 
> 


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux