solarian Posted January 18, 2006 Report Share Posted January 18, 2006 Hello! I just noticed that when I log into a xless environment, or just start a new session in a terminal (such as Konsole or Eterm, I get this line: /usr/X11R6/lib/X11/xserver/xprint-startup: line 114: /etc/init.d/functions: Permission denied It looks like this: The last things I remember doing is: * changed security settings in MCC to "high" (but that was like 3 days ago) * updated my Mandriva distribution (security updates) * installed a new mouse cursor theme I looked at /usr/X11R6/lib/X11/xserver/xprint-startup and etc/init.d/functions, but I didn't understand anything I saw :unsure: so, ummmm.... help?! Quote Link to comment Share on other sites More sharing options...
solarian Posted January 18, 2006 Author Report Share Posted January 18, 2006 So, I tried to switch to -standart- security level in MCC, and the weird output is gone! Switched to -high-, and the output appears again. 02:47:04 draksec[11045]: Configuring msec 02:47:04 draksec[11045]: Setting security level to "Standard" 02:47:04 draksec[11045]: running: msec -o run_commands=0 -o log=stderr 2 02:47:05 draksec[11045]: Setting security administrator option to "no" 02:47:05 draksec[11045]: Setting security periodic checks 02:47:05 draksec[11045]: Setting msec functions related to network 02:47:05 draksec[11045]: Setting msec functions related to system 02:47:05 draksec[11045]: Applying msec changes 02:47:05 draksec[11045]: running: /usr/sbin/msec 02:47:05 msec: ### Program is starting ### 02:47:05 msec: Reading local rules from /etc/security/msec/level.local 02:47:05 msec: Allowing chkconfig --add from rpm 02:47:05 msec: Setting password maximum aging for new user to 99999 02:47:05 msec: Setting password maximum aging for root and users with id greater than 500 to 99999 and delay to -1 days 02:47:05 msec: got current maximum password aging for user root with command 'LC_ALL=C /usr/bin/chage -l root' 02:47:05 msec: got current maximum password aging for user avatar with command 'LC_ALL=C /usr/bin/chage -l avatar' 02:47:05 msec: got current maximum password aging for user net_crawler with command 'LC_ALL=C /usr/bin/chage -l net_crawler' 02:47:05 msec: Allowing reboot to the console user 02:47:05 msec: Writing config files and then taking needed actions 02:47:05 msec: Fixing owners and permissions of files and directories 02:47:05 draksec[11045]: ### Program is exiting ### 02:47:15 draksec[11191]: ### Program is starting ### 02:47:19 draksec[11191]: Configuring msec 02:47:19 draksec[11191]: Setting security level to "High" 02:47:19 draksec[11191]: running: msec -o run_commands=0 -o log=stderr 3 02:47:20 draksec[11191]: Setting security administrator option to "no" 02:47:20 draksec[11191]: Setting security periodic checks 02:47:20 draksec[11191]: Setting msec functions related to network 02:47:20 draksec[11191]: Setting msec functions related to system 02:47:20 draksec[11191]: Applying msec changes 02:47:20 draksec[11191]: running: /usr/sbin/msec 02:47:20 msec: ### Program is starting ### 02:47:20 msec: Reading local rules from /etc/security/msec/level.local 02:47:20 msec: Allowing chkconfig --add from rpm 02:47:20 msec: Setting password maximum aging for new user to 99999 02:47:20 msec: Setting password maximum aging for root and users with id greater than 500 to 99999 and delay to -1 days 02:47:20 msec: got current maximum password aging for user root with command 'LC_ALL=C /usr/bin/chage -l root' 02:47:20 msec: got current maximum password aging for user avatar with command 'LC_ALL=C /usr/bin/chage -l avatar' 02:47:20 msec: got current maximum password aging for user net_crawler with command 'LC_ALL=C /usr/bin/chage -l net_crawler' 02:47:20 msec: Allowing reboot to the console user 02:47:20 msec: Writing config files and then taking needed actions 02:47:20 msec: Fixing owners and permissions of files and directories 02:47:20 draksec[11191]: ### Program is exiting ### Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted January 18, 2006 Report Share Posted January 18, 2006 I get exactly the same error/message in pclos which is based on mandriva but not in mandriva. Security is set to "High" in both. When I get home, I'll try reseting the security level to Standard in pclos and see if it goes away. It's obviously a bug but why it effects one install but not the other, I can't say. Quote Link to comment Share on other sites More sharing options...
solarian Posted January 22, 2006 Author Report Share Posted January 22, 2006 So anyone has any advices? Maybe I should chmod those two files by hand.. but I don't want to compromise my security. That output is annoying... Quote Link to comment Share on other sites More sharing options...
scarecrow Posted January 22, 2006 Report Share Posted January 22, 2006 (edited) Checkout your ~.xsession or ~.xinitrc or ~.bashrc files for something invoked which creates those error messages when you change your security settings. Edited January 22, 2006 by scarecrow Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.