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
How to Encrypt SQLite Data at Rest is one lab note for SQLite. Encryption at rest is a key you can recover and a setting you can name. This hour writes the plan. It does not turn encryption off.
SQLite is a file, not a server. The client is sqlite3. There is no listener to publish. The file mode is not world-readable, and the directory is not writable by everyone. Do not VACUUM a file you have not copied. The file, when there is one, is one database file. There is no bind address. Do not invent a network listener for this file.
Do not disable encryption to make a restore easier. Do not put the key in the note or in git. Do not enable it on the only copy during the reading. The key location is a store, not the ticket, and encryption was not switched during the reading.
The generator drafts text in the browser. It does not log in. A header on a script says to review it before running, and a destructive line is supposed to stay a comment. You still read the draft. 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.
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.
- Write the database name and confirm you administer it.
- Save a backup, a file, or a snapshot before any draft is applied.
- Read the draft and delete every line this ticket did not name.
- Replace a sample password, a bind to every address, and any secret.
- Apply one change only when the lab window is open.
- Read the result back and compare it with the ticket.
- Stop. The next change is a different page.
Mistakes that outlive the statement
How to Encrypt SQLite Data at Rest goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Pasting a draft you did not read.
- The wrong database.
- A secret or a sample password left in the note.
- A listen address of every interface left in the file.
- Two changes in one window.
- No copy saved before the change.
- Disabling authentication, a firewall, or TLS to make a check pass.
- Calling the generator output a finished production change.
- Do not disable encryption to make a restore easier. Do not put the key in the note or in git. Do not enable it on the only copy during the reading.
Decisions to write down
One decision for How to Encrypt SQLite Data at Rest: The database is SQLite. The change is only this encryption-at-rest note. A sample password was replaced or was never present. A listen on every address was removed or was never present. Nothing was applied during the reading. And the proof you expect is: The key location is a store, not the ticket, and encryption was not switched during the reading.
Checks before you call it done
Confirm this before you call the change done: The database name matches the ticket. The draft was read. No secret is in the note. Authentication was not disabled. The listen address is not every interface. And nothing was applied, or the lab window is still closed. If one of those fails, stop.
# SQLite. encryption-at-rest note.
# Review before you run.
# Replace a sample password.
# Delete a bind to every address.
# Do not disable authentication.
# 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.Before you leave the database
How to Encrypt SQLite Data at Rest 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.
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.
- Pillar: SQLite Administration Guide
- How-To: How to Create Indexes in SQLite
- How-To: How to Import a CSV into SQLite
- How-To: How to Export SQLite Data to CSV
Companion: Security: Server Hardening Guide.