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
The generator writes a local peer line, one host line for the database and user you name, and a hostssl line that rejects every address. Replace the sample prefix 10.0.0.0/24 with a prefix you administer. Leave the reject line as a reject. Do not change it to trust, and do not use trust for every address. The hash tool builds a SCRAM-SHA-256 verifier for a password you type and says it does not send the value anywhere. It does not recover a password. Do not type a real password into a page you then file. prompt-for-this stays out of the note.
Do not reload PostgreSQL during the reading. password_encryption for a new role is scram-sha-256, not md5. One host you can name.
192.0.2.10, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the database named in the ticket. Read the draft, then the database, then decide.
Rollback is the backup, the file, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Replace the sample prefix.
- Read the reject line.
- Do not type a real password into the hash tool for the ticket.
- Do not reload.
- Stop.
Mistakes that outlive the statement
PostgreSQL pg_hba.conf Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- trust used for every address.
- The reject line changed into an allow.
- A real password filed in the note.
- A reload during the reading.
- md5 kept for a new role.
Decisions to write down
One decision for PostgreSQL pg_hba.conf Explained: The prefix is one you administer. The method is scram-sha-256. No password is in the note. And nothing was reloaded.
Checks before you call it done
Confirm this before you call the change done: The prefix was replaced. The reject line is still a reject. No password is in the note. Nothing was reloaded. And the host is yours. If one of those fails, stop.
# scram-sha-256 for one host you administer.
# Replace 10.0.0.0/24.
# The every-address line stays a reject.
# Do not use trust for every address.
# The hash tool does not recover a password.
# Do not reload during the reading.Before you leave the database
PostgreSQL pg_hba.conf Explained ends when the database in the prompt is the database in the ticket. If it is not, you are on the wrong database. Stop.
The draft stays a draft until a person has read the names in it. A generator does not log into the database. You delete a line that names a host, a database, or an account you did not write down.
192.0.2.10, 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 database 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. A sample password in a draft is replaced. It is not a password you keep.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the database name and the change aloud. If they cannot find them in the ticket, the note is not done.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a database you do not administer. You do not disable authentication, a firewall, or TLS 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.