DE

↑ ↓ select, Enter open, Esc close

Show the current umask

harmlessPermissions and ownershipalle
user@server
umask && umask -S

Prints the umask first in octal (such as 0022) and then symbolically (u=rwx,g=rx,o=rx). The umask subtracts permissions from the base values 666 for files and 777 for directories, so 022 results in 644 and 755. Explains why files created via SSH, cron or deploy scripts get different permissions than expected.

Note: umask 002 changes the value for the running shell, to make it permanent set it in ~/.profile, for example. PHP-FPM and other services have their own umask.

Also searched as

  • why do new files have wrong permissions
  • check umask linux
  • default permissions for new files
  • umask 022 or 002

Related one-liners

All in Permissions and ownership

Copy permissions and owner from a reference file

#chmod --reference=/var/www/vhosts/example.com/httpdocs/index.php /var/www/vhosts/example.com/httpdocs/wp-config.php && chown --reference=/var/www/vhosts/example.com/httpdocs/index.php /var/www/vhosts/example.com/httpdocs/wp-config.php
cautionPermissions and ownership

Find world-writable files and directories

$find /var/www/vhosts -xdev -perm -0002 ! -type l -ls 2>/dev/null
harmlessPermissions and ownership

Remove write permission for others recursively

$chmod -R o-w /var/www/vhosts/example.com/httpdocs
cautionPermissions and ownership

Secure the permissions of wp-config.php

$chmod 600 /var/www/vhosts/example.com/httpdocs/wp-config.php
cautionPermissions and ownership

Set all directories to 755 recursively

$find /var/www/vhosts/example.com/httpdocs -type d -exec chmod 755 {} +
cautionPermissions and ownership

Set all files to 644 recursively

$find /var/www/vhosts/example.com/httpdocs -type f -exec chmod 644 {} +
cautionPermissions and ownership

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.