https://bugzilla.novell.com/show_bug.cgi?id=408006
User bjoern@cs.tu-berlin.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=408006#c7
--- Comment #7 from Björn Voigt 2008-09-29 14:02:04 MDT ---
Do we really need the shell scripting in /etc/init.d/xfs?
[...]
# create new fonts.dir files if necessary
/sbin/conf.d/SuSEconfig.fonts > /dev/null
find /tmp/.font-unix -type f -exec safe-rm {} \; 2> /dev/null
find /tmp/.font-unix -type d -exec safe-rmdir {} \; 2> /dev/null
rm -rf /tmp/.font-unix
mkdir --mode=0700 /tmp/.font-unix > /dev/null || { echo "can not create
directory '/tmp/.font-unix'"; exit -1;}
chown nobody.nobody /tmp/.font-unix
[...]
I started /usr/bin/xfs with strace. xfs seems to create the directory
/tmp/.font-unix itself. Also it sets correct permissions (drwxrwxrwt for
root:root), unlinks old sockets (/tmp/.font-unix/fs7100) and recreates a new
socket. The attected strace log shows this:
lstat64("/tmp/.font-unix", {st_mode=S_IFDIR|0755, st_size=4096, ...})
= 0
open("/tmp/.font-unix", O_RDONLY) = 6
fstat64(6, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fchown32(6, 0, 0) = 0
fchmod(6, 01777) = 0
[...] = 022
lstat64("/tmp/.font-unix", {st_mode=S_IFDIR|S_ISVTX|0777,
st_size=4096, ...}) = 0
unlink("/tmp/.font-unix/fs7100") = -1 ENOENT (No such file or
directory)
bind(6, {sa_family=AF_FILE, path="/tmp/.font-unix/fs7100"}, 24) = 0
Is there any security problem with xfs?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.