View previous topic :: View next topic |
Author |
Message |
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Tue Feb 07, 2017 11:03 am Post subject: [SOVLED] /.cache/qt_compose_cache_little_endian |
|
|
/.cache/qt_compose_cache_little_endian_cefa3bd948463b1f4a4d8ed85892fcef
keeps getting placed on my box even though i keep deleting it, does anyone knows what it is?
Last edited by squirrelsoup on Fri Feb 17, 2017 7:25 pm; edited 1 time in total |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Tue Feb 07, 2017 2:44 pm Post subject: Re: /.cache/qt_compose_cache_little_endian |
|
|
squirrelsoup wrote: | [...] does anyone knows what it is? |
squirrelsoup ... yes, a cache file created by Qt.
best ... khay |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Sat Feb 11, 2017 9:08 pm Post subject: |
|
|
Looks like a sign that you're running heavy GUI apps as root. Why? |
|
Back to top |
|
|
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Wed Feb 15, 2017 3:50 am Post subject: |
|
|
am i running heavy GUI as root? how can i know? |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21602
|
Posted: Wed Feb 15, 2017 4:40 am Post subject: |
|
|
Either your permissions on / are too permissive or you are running a Qt program as root. Either way, something is wrong. You should never run Qt (or GTK+ or ...) GUI applications as root. |
|
Back to top |
|
|
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Wed Feb 15, 2017 3:05 pm Post subject: |
|
|
i have no idea on how to solve this,
Code: | -rws--x--x 1 root 39880 Feb 14 21:11 /bin/mount
-rws--x--x 1 root 36880 Feb 9 06:28 /bin/su
-rws--x--x 1 root 46888 Feb 9 06:28 /bin/passwd
-rws--x--x 1 root 27336 Feb 14 21:11 /bin/umount
-rws--x--x 1 root 44400 Feb 9 04:44 /bin/ping6
-rws--x--x 1 root 39856 Feb 9 04:44 /bin/ping
-rws--x--x 1 root 54952 Feb 9 06:28 /usr/bin/chage
-rws--x--x 1 root 68136 Feb 9 06:28 /usr/bin/gpasswd
-rwsr-s--x 1 man 122648 Feb 9 06:34 /usr/bin/mandb
-rws--x--x 1 root 36496 Feb 9 06:28 /usr/bin/newgrp
-rws--x--x 1 root 33512 Feb 9 06:28 /usr/bin/newgidmap
-rws--x--x 1 root 46376 Feb 9 06:28 /usr/bin/chfn
-rws--x--x 1 root 33512 Feb 9 06:28 /usr/bin/newuidmap
-rws--x--x 1 root 2218160 Feb 14 21:53 /usr/bin/Xorg
-rws--x--x 1 root 41256 Feb 9 06:28 /usr/bin/chsh
-rws--x--x 1 root 23248 Feb 9 06:28 /usr/bin/expiry
-rws--x--x 1 root 23104 Feb 14 21:42 /usr/bin/pkexec
-rwsr-s--x 1 man 104408 Feb 9 06:34 /usr/bin/man
-rws--x--x 1 root 14592 Feb 14 21:42 /usr/lib64/polkit-1/polkit-agent-helper-1
-rws--x--x 1 root 441400 Feb 14 21:10 /usr/lib64/misc/ssh-keysign
-rws--x--x 1 root 6104 Feb 14 21:54 /usr/libexec/xf86-video-intel-backlight-helper
-rws--x--- 1 messagebus 56560 Feb 14 21:31 /usr/libexec/dbus-daemon-launch-helper
-rwxr-s--x 1 utmp 14752 Feb 14 22:18 /usr/libexec/gnome-pty-helper
-rws--x--x 1 root 31128 Feb 9 06:26 /sbin/unix_chkpwd
-rws--x--- 1 video 29424 Feb 15 03:41 /opt/bin/nvidia-modprobe |
|
|
Back to top |
|
|
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Wed Feb 15, 2017 3:35 pm Post subject: |
|
|
i followed this handbook: https://wiki.gentoo.org/wiki/Non_root_Xorg
does that mean i was running X as root all the time?
additional questions:
is it really necessary to set quotas on the disk in order to maintain a secure system?
is it really necessary to set file permissions, or is it already set o.k by default after installing Gentoo following the handbook? |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Wed Feb 15, 2017 5:00 pm Post subject: |
|
|
I don't know who would tell you such idiotic ideas, but they're wrong. Gentoo is already secure and hitting random parts with a sledgehammer won't magically make it better. |
|
Back to top |
|
|
ct85711 Veteran
Joined: 27 Sep 2005 Posts: 1791
|
Posted: Wed Feb 15, 2017 5:14 pm Post subject: |
|
|
In general, you should only use root when necessary, otherwise the majority of the time you use a regular user account. In a terminal, there is a big difference if you have a # or a $, the later indicates you are a regular user. Another easy test, is where your user's home directory is at. For regular users, they are usually in /home/... where the root's home directory is /root/. By default, a user can NOT view/modify another user's home folder (you shouldn't even be able to cd into it).
Note: Your terminal prompt could always be changed, but that is up to you to figure out.
Quotas are used for when you want to restrict how much storage space a user is taking up (so they don't hog your hard drive), for a single user it's of little concern. File permissions in general is set so one user is unable to modify another's file. Most times, a regular user only has enough permissions to write in a few locations, the temp folder (which is often cleaned out regularly) and their home directory. There can be other locations too, but that is depending out your setup and configuration.
Note: Doing cd ~ can be a quick way to get to your home directory, otherwise using pwd can help identify what directory you are in. |
|
Back to top |
|
|
Leio Developer
Joined: 27 Feb 2003 Posts: 494 Location: Estonia
|
Posted: Wed Feb 15, 2017 5:42 pm Post subject: |
|
|
It is more secure to run Xorg without root privileges with USE=-suid on xorg-server as discussed on that wiki page, if possible with your hardware and drivers.
But Xorg running as root doesn't meant that anything else does that, as the clients that connect to that X server (including session manager and so on) shouldn't be running as root, and Xorg definitely isn't what's creating some cache entries to your /. _________________ GNOME team lead; GStreamer; MIPS/ARM64 |
|
Back to top |
|
|
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Wed Feb 15, 2017 6:05 pm Post subject: |
|
|
ok, if i understand correctly, then i will leave quota's and file permissions as default.
however if root xorg not caused the cache file, what could have caused it? maybe virtualbox? |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21602
|
Posted: Thu Feb 16, 2017 2:49 am Post subject: |
|
|
Considering the name of the file, I think it is fair to assume that whatever created the file was run by root and uses Qt. What GUI programs have you been running as root and why? The only GUI programs that should run as root at all (and there are people who will argue even this one) are the GUI wrappers for certain system administration tasks. Virtualbox, browsers, mail clients, etc. should all be run as your user, not as root. |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Feb 16, 2017 4:18 am Post subject: |
|
|
squirrelsoup ...
whatever is writing it has $XDG_CACHE_HOME set to '/.cache/' ... which is unusual as generally this is set to $HOME/.cache (unless redefined to point elsewhere). So even though root has permissions to write that file, the location doesn't seem to match would would normally happen with such things. That leads me to think that whatever is run doesn't have the env of root (but none the less can write to '/').
You should check the above variable in both root, and user(s), and its probably a good idea to see what the permissions of '/' are:
Code: | $ echo $XDG_CACHE_HOME
$ su -
# echo $XDG_CACHE_HOME
# ls -ld / |
I don't use xdg but I assume it's setup in '/etc/env.d/' somewhere, perhaps the login manager doesn't have that in its env?
best ... khay |
|
Back to top |
|
|
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Thu Feb 16, 2017 6:51 pm Post subject: |
|
|
i did a reinstall and the cache file did not return.
check on /
Code: | $ ls -ld /
drwxr-xr-x 21 root root 4096 Feb 14 20:44 / |
|
|
Back to top |
|
|
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Fri Feb 17, 2017 5:02 pm Post subject: |
|
|
khayyam wrote: | squirrelsoup ...
whatever is writing it has $XDG_CACHE_HOME set to '/.cache/' ... which is unusual as generally this is set to $HOME/.cache (unless redefined to point elsewhere). So even though root has permissions to write that file, the location doesn't seem to match would would normally happen with such things. That leads me to think that whatever is run doesn't have the env of root (but none the less can write to '/').
You should check the above variable in both root, and user(s), and its probably a good idea to see what the permissions of '/' are:
Code: | $ echo $XDG_CACHE_HOME
$ su -
# echo $XDG_CACHE_HOME
# ls -ld / |
I don't use xdg but I assume it's setup in '/etc/env.d/' somewhere, perhaps the login manager doesn't have that in its env?
best ... khay |
i am sorry for being a total noob, but i have no idea what xdg means; however i found that i am running:
Code: | /bin/sh /etc/xdg/xfce4/xinitrc --/etc/X11/xinitserverrc |
does this need any security configuration, i.e can it be exploited remotely in some way?
is startx -- -nolisten tcp + securing ssh enough for anyone to stop remotely connecting to my gentoo desktop? |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Fri Feb 17, 2017 6:54 pm Post subject: |
|
|
squirrelsoup wrote: | i am sorry for being a total noob, but i have no idea what xdg means;[...] |
squirrelsoup ... XDG is a (pseudo) "specification" that defines $XDG_CACHE_HOME (ie, ~/.cache).
squirrelsoup wrote: | however i found that i am running: '/bin/sh /etc/xdg/xfce4/xinitrc --/etc/X11/xinitserverrc' does this need any security configuration, i.e can it be exploited remotely in some way? is startx -- -nolisten tcp + securing ssh enough for anyone to stop remotely connecting to my gentoo desktop? |
'-nolisten tcp' is on by default, so you don't need to provide it. If you want to check you can do the following:
ps auxwww | grep [/]usr/bin/X: | khayyam 12893 0.5 0.8 73736 17472 tty4 S<sl+ Feb15 14:52 /usr/bin/X -nolisten tcp :0 -auth /home/khayyam/.serverauth.12871 |
As for how secure your desktop is currently, as NeddySeagoon said before in another topic, security is like layers of an onion (meaning there isn't a one shot solution, good security is layered). That said, I would expect the out of the box configuration to not provide a potential vunerability by default (and it doesn't), so, yes, you should be safe with the default xorg-server install, and securing ssh. However, you could run a basic firewall (net-firewall/sanewall or net-firewall/firehol might be a good choice), to add an additional layer (the analogy to the onion should be making more sense now), etc, etc.
best ... khay |
|
Back to top |
|
|
squirrelsoup Tux's lil' helper
Joined: 29 Dec 2016 Posts: 98
|
Posted: Fri Feb 17, 2017 7:25 pm Post subject: |
|
|
thank you all |
|
Back to top |
|
|
|