On Mon, 19 Dec 2011 10:48:23 -0500, ill...@gmail.com wrote: > On 30 November 2011 14:03, Polytropon <free...@edvax.de> wrote: > > On Wed, 30 Nov 2011 13:40:19 -0500, ill...@gmail.com wrote: > >> A dirty workaround might be to link /.config > >> to something innocuous. One could obvio- > >> usly also have /.config mounted as a tmpfs(5). > >> So it couldn't persist from boot to boot. > >> > >> The cleanest solution is to forgo qt/kde, but > >> then you're slightly more limited in what you > >> can use for office-type stuff. > > > > The question remains: > > > > How is a user-started process (e. g. when you run > > the "startx" command) supposed to create directory > > entries and files on root level /, a thing that > > only root and root-like users (and programs!) > > should be allowed to? > > > > % mkdir /.config > > mkdir: /.config: Permission denied > > > > As a normal user, you _intendedly_ can't do this. > > Why would you assume that a program you start > > can do it? > > I don't have any QT/KDE stuff but isn't kdm suid > (& owned by root)?
That could be the reason: kdm, belonging to the KDE world and quite probably using Qt, running with the permissions to access /. You could temporarily try to disable kdm and replace it by xdm, or no display login manager at all. In that case, /.config shouldn't appear anymore. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
