Everyday Utilities for Sysadmins

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.

Small tools with sharp edges

A diff shows what changed between two texts. It does not say whether the change is safe. You still read it. A diff of a configuration is the change you review before reload. A diff that contains a password is a diff you do not paste into a ticket. Rotate the secret and compare a redacted copy.

Base64 is an encoding. It turns bytes into text so they can sit in a file or a header. It is not encryption. Anyone can decode it. Do not put a password in Base64 and call it protected. The encoder on this site does the transform in the browser. If you paste a real secret into it, you have placed that secret in the page you are using. Prefer a placeholder.

A hash is a fingerprint. It tells you whether two files are the same. It does not tell you whether the file is trustworthy unless you got the expected hash from a channel you trust. MD5 is weak for an adversary and still a checksum for an accidental copy error. Prefer a stronger hash the vendor published when the vendor published one.

Time converters, JSON formatters, and the other small tools on this desk stay in the browser so the log line does not have to leave the building. They are for the line you are allowed to hold. A log line with a token is still a secret, even if the tool is local.

Review a config change with a diff and a placeholder

Save the previous config and the new config as two files. Diff them. The result should be the lines you meant to change and nothing else. If the diff is a thousand lines because the generator reordered keys, do not reload. Find a canonical form or edit by hand until the diff is readable. The diff checker on this site can show that. Do not upload a file that contains a live secret. Replace the secret with prompt-for-this first.

If a vendor asks for a certificate in Base64, encode the certificate, not the private key mixed into a chat. The private key stays in the file with the mode from the permissions guide. A Base64 string of a key in a ticket is still the key.

When you download an image or a package and the project published a checksum, compute the hash and compare it to the value you copied from the project, not to a value in the same folder as the download. A mismatch means you do not install. It does not mean you retry until a tool says yes.

Convert a log timestamp to the timezone in the ticket so two people agree what 02:15 was. The scheduling guide already asked for that timezone. The converter is the arithmetic.

A change you can finish

Utilities do not change the host. The change is the config you reload after the diff is clean, and that reload belongs to the guide for that service. This page stops at a diff you can explain.

If a secret landed in a diff or a Base64 note, the change becomes a rotation. You do not continue the reload until the secret is rotated and the note is gone.

Replace secrets with prompt-for-this before any paste into a tool or a ticket.
Diff the previous file and the new file.
Reject a diff you cannot read.
Encode only the data the form asked for, and not a password you meant to hide.
Compare checksums to a value from the publisher.
Convert times into the timezone written on the ticket.
Hand the reviewed file to the service's own reload steps.

Mistakes that outlive the command

everyday utilities fails in the same few ways. Each one looks finished on the day you type it. The list is here so the ticket can forbid them before the window, not so you can recognise them in an incident review.

Calling Base64 encryption.
Pasting a live password into a browser tool or a ticket.
Reloading from a diff you did not read because it was long.
Trusting a checksum that came in the same archive as the file.
Using MD5 as proof against tampering when the vendor published a stronger hash.
A diff of two files that are not the before and after of this change.
Converting a timestamp and then forgetting which timezone you converted into.
Treating a formatter's rewrite as a harmless reorder and reloading it blind.

Decisions to write down before the window

Decision 1 for everyday utilities. Secrets are prompt-for-this in every paste. A real secret in a diff stops the work for a rotation. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 2 for everyday utilities. The diff is small enough to read, or you are not done editing. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 3 for everyday utilities. Base64 output is not described as protected. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 4 for everyday utilities. The expected hash came from the publisher's channel. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 5 for everyday utilities. A mismatch stops the install. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 6 for everyday utilities. Timestamps in the ticket name their timezone. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 7 for everyday utilities. The tool ran in the browser and did not need the file uploaded anywhere. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 8 for everyday utilities. The reload belongs to the service guide, after this review. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 9 for everyday utilities. The previous file is kept so the diff can be repeated. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 10 for everyday utilities. A second person can point at the changed lines. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Decision 11 for everyday utilities. No utility output with a secret was filed. Write that decision in the ticket before you change the host. The proof is the smallest command or screen that confirms it, recorded with the hostname and the time. If the host disagrees, the ticket changes. A second change does not go on top of a failed check. The rollback is the previous value you wrote down, not a reboot that hides which line mattered.

Utility checks before the reviewed file is reloaded

Check 1 in Utility checks before the reviewed file is reloaded. The before and after files are the ones from this change. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 2 in Utility checks before the reviewed file is reloaded. Secrets were replaced before the diff was shared. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 3 in Utility checks before the reviewed file is reloaded. The diff was read. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 4 in Utility checks before the reviewed file is reloaded. Base64 was not used to hide a password. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 5 in Utility checks before the reviewed file is reloaded. Any checksum matched a publisher value. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 6 in Utility checks before the reviewed file is reloaded. A mismatch was not ignored. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 7 in Utility checks before the reviewed file is reloaded. Timezone is named on converted times. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 8 in Utility checks before the reviewed file is reloaded. The previous file is still available. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 9 in Utility checks before the reviewed file is reloaded. Nothing was reloaded from an unread reorder. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 10 in Utility checks before the reviewed file is reloaded. A second person saw the changed lines. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 11 in Utility checks before the reviewed file is reloaded. The service guide's test command is the next step, not another formatter. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 12 in Utility checks before the reviewed file is reloaded. The ticket does not contain a live secret. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 13 in Utility checks before the reviewed file is reloaded. The browser tool was enough. The file was not sent anywhere else. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 14 in Utility checks before the reviewed file is reloaded. The hostname in the prompt matches the hostname in the ticket for everyday utilities. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 15 in Utility checks before the reviewed file is reloaded. The result line includes the time and the person, not only the command. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 16 in Utility checks before the reviewed file is reloaded. You can point at the rollback value without searching a chat history. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Check 17 in Utility checks before the reviewed file is reloaded. Done is a sentence a second person can repeat: the proof for everyday utilities happened, and the next host is not started early. Record the device name, the result, and the time on the same line. If the result does not match this check, stop and fix the ticket before you add another change. The rollback for this check is the previous value you wrote down, not a reboot. A reboot hides whether the check was the one that mattered. When the check passes, move to the next one. When it fails, the incident is this check.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Guides in this cluster

These supporting pages belong to this pillar. A published page is linked. The others are named until they are published.