This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Umask subtracts permission bits from the mode a new file would get. The calculator shows the result of a mask you type. It does not change a shell.
000 leaves new files writable by everyone. That is not the default you copy. A service account gets the mask in its unit or its profile, not in a login you happened to have open. One mask.
192.0.2.10/24 and example.com are documentation. They stay in the note.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Write the mask.
- Read the resulting file and directory modes.
- Reject 000.
- Name where the mask will live.
- Do not apply it during the reading.
- Stop.
Mistakes that outlive the command
Umask Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- umask 000.
- The mask set in the wrong account.
- A world-writable file treated as normal.
- The mask applied during the reading.
Decisions to write down
One decision for Umask Explained: The mask is not 000. The account is named. Nothing was applied. And the result was read.
Checks before you call it done
Confirm this before you call the change done: The mask is written. 000 was refused. The account is written. Nothing was applied. And the resulting mode is written. If one of those fails, stop.
# Do not use umask 000.
# One account.
# Do not apply during the reading.Before you leave the host
Umask Explained ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.