Normally deleting or re-owning them (depending on the file) does not create problems and often it solves some, like the infamous. 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). In general files and directory in your home should be owned by you. With other permissions, GPG will complain about unsafe permissions. ~/.gnupg (and contents) should be accessible only by you. should be writable only by the user, but can be world-readable. Other files like authorized_keys, known_hosts, etc. Used to encrypt the sensitive part of this file using 3DES. To specify a passphrase when generating the key which will be Private key file if it is accessible by others. Sensitive data and should be readable by the user but not acces‐ Group-writable provided that the group in question contains onlyĬontains the private key for authentication. Read/write for the user, and not writable by others. The potential for abuse, this file must have strict permissions: The file format andĬonfiguration options are described in ssh_config(5). See man ssh, section FILES: ~/.ssh/config #DEFAULT OWNERSHIP OF NEW FOLDER SOFTWARE#Other than that, a common case involves two security-related software that require restricted permissions on certain files, namely: 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |