Skip to contentSkip to conversation

font paths

DISCUSSION Russell Coker 2 participants 3 messages Oct 28, 2002 – Oct 29, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

http://lists.debian.org/debian-kde/2002/debian-kde-200210/msg00605.html

Please read the above discussion about font paths used by KDE. I imagine that GNOME is likely to do the same (if they don't already).

Would it make sense to have a user_home_xfont_t for the fonts so the X server can read them but not the rest of the user's files?

Signature · 10 lines
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
#1 lore raw
Quoted 7 lines · Russell Coker

http://lists.debian.org/debian-kde/2002/debian-kde-200210/msg00605.html

Please read the above discussion about font paths used by KDE. I imagine that GNOME is likely to do the same (if they don't already).

Would it make sense to have a user_home_xfont_t for the fonts so the X server can read them but not the rest of the user's files?

Does the same issue arise for other user-configurable data that X needs to read? If so, you might want a more general type for this purpose.

--
Stephen D. Smalley, NAI Labs
[email protected]

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

#2 lore raw
Quoted 11 lines · Stephen Smalley
Quoted 7 lines · Russell Coker

http://lists.debian.org/debian-kde/2002/debian-kde-200210/msg00605.html

Please read the above discussion about font paths used by KDE. I imagine that GNOME is likely to do the same (if they don't already).

Would it make sense to have a user_home_xfont_t for the fonts so the X server can read them but not the rest of the user's files?

Does the same issue arise for other user-configurable data that X needs to read? If so, you might want a more general type for this purpose.

I don't know.

Maybe it should be user_home_x_ro_t?

Signature · 10 lines
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


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