Application Data Storage
Besides your keys, GpgFrontend saves a few things of its own: key server entries, key generation profiles, window positions, your list of key databases, key groups, key categories, and so on. Modules keep their secrets here too, such as the phrase of the Instant Messaging module. The sensitive parts are encrypted with the program’s own key.
The saved data also includes a copy of your unsaved text editor tabs, when Cache text editor contents. is on. It is on by default. See Unsaved Editor Tabs.
All of this happens automatically. There is nothing to set up and nothing to maintain. This page is here for people who want to know what is going on.
For the key that does the protecting, and the choices you have about it, see Application Secure Key.
Look at the Saved Data
Section titled “Look at the Saved Data”-
Open Settings and go to General.
-
In the Data box, click Reveal in File Explorer. Your file manager opens your profile folder. The saved data is in the
data_objsfolder there.
Clear the Saved Data
Section titled “Clear the Saved Data”-
Open Settings and go to General.
-
In the Data box, click the button that starts with Clear All Data Objects. The button also shows the total size of the saved data.
-
A Confirm window asks: “Are you sure you want to clear all data objects?” Click Yes to go ahead, or No to stop.
Sandboxed builds (Flatpak and Mac App Store) hide the Data box.
How It Works
Section titled “How It Works”Each saved item is encrypted on its own, with its own key made from the program’s key and the item’s name. Nothing is encrypted with one shared key, so breaking into one item tells an attacker nothing about the others.
The encryption also detects tampering. If someone changes a file, GpgFrontend notices and refuses to use it.
Files are written in a way that cannot leave a half-finished result behind. If the program or the computer stops in the middle of a write, the old version survives intact.
Where the Files Are
Section titled “Where the Files Are”The files live inside your profile, in a folder called data_objs. Each file
is named after a scrambled version of what it holds, so the file names give
nothing away.
Directory@profile/ your profile folder
Directorydata_objs/
- … one file for each saved item
Key Changes
Section titled “Key Changes”Below the Maximum Secure Level, the program uses one key all the time. You can move between those levels freely.
At Maximum, GpgFrontend makes a new key every week and saves new data with it. Old files stay readable, because each file records which key it was written with. A file moves to the new key the next time GpgFrontend saves it. You never see this happen.
If you lower the level from Maximum, data saved with those weekly keys can no longer be opened. GpgFrontend warns you first. See Application Secure Key.
Files Whose Key Is Gone
Section titled “Files Whose Key Is Gone”Once each time it runs, GpgFrontend checks the saved files in the background.
It cleans up files it can no longer use. First it moves them to a folder
called data_objs.quarantine, next to data_objs. Later it deletes them from
there.
How long it waits depends on the Secure Level:
| What is wrong with the file | Standard or Enhanced | Strong or Maximum |
|---|---|---|
| Its key is gone | Moved aside after 7 days | Moved aside after 3 days |
| It cannot be opened with its key | Left where it is | Moved aside at once |
| It is broken (bad name, too small) | Moved aside at once | Moved aside at once |
| Already moved aside | Deleted after 30 days | Deleted after 7 days |
Until a file is deleted, you can still find it in data_objs.quarantine.