I often see users that try to fix an issue and somewhere read or just try to recursively chown
their home directory and sometimes even also reset permissions recursively to something like rwxr-xr-x
or similar.
Imagine such an owner/permission massacre - are there critical files/directories that need special permissions or to be root-owned for the system to work?
NO file in
~
has to be owned by root.If a software requires that a file in your home directory be owned by another user, it is a bug and should be reported as such.
Other than that, a common case involves two security-related software that require restricted permissions on certain files, namely:
SSH
See
man ssh
, sectionFILES
:Other files like
authorized_keys
,known_hosts
, etc. should be writable only by the user, but can be world-readable.GnuPG
~/.gnupg
(and contents) should be accessible only by you. With other permissions, GPG will complain about unsafe permissions.In general files and directory in your home should be owned by you.
I have some strange root-owned files that are probably the result of executing
sudo
command; in fact there are programs that write things under$HOME
(which well behaved programs requiring super-user privileges shouldn't do --- the effect is root taking ownership of files that should belongs to the user).Normally deleting or re-owning them (depending on the file) does not create problems and often it solves some, like the infamous
.Xauthority
file --- and sometimes, after runningsudo dconf-editor
, you have things in configurations you can't modify anymore.About special modes:
x
means right to cross);.ssh
must bedrwx------
(0700) and the private keys in it-rw-------
(0600)Public
directory for sharing, it should be probablydrwxr-xr-x
(read permission to anyone) ordrwxrwxrwt
(with write permission and sticky bit, for enabling writing).... I can't think to anything more needing special treatment.