github Download
Destroying keys

Destroying keys #

After you have rotated the keys, you might want to destroy the old ones.

When it is safe to destroy keys #

Transport keys may be destroyed after you have confirmed that all instances are using the new keys.

Data storage keys may be destroyed after you have confirmed that no data is encrypted with old keys.

We strongly recommend to never destroy the keys immediately after rotation. First you make a backup of the old keys. Then you remove the supposedly unused keys from the components that may use them. After that, you verify that your operations are not affected by this removal. Only then you might plan for eventual destruction of the key backup.

How to destroy Acra keys #

In order to destroy historical keys, remove corresponding files from the *.old subdirectories. For example, to remove old storage encryption keys:

├── your_client_ID_storage              current private storage key
├── your_client_ID_storage.old
│   ├── 2020-02-02T12:43:56.460128      previous private storage keys
│   └── 2020-08-03T16:54:12.176121
├── your_client_ID_storage.pub          current public storage key
├── your_client_ID_storage.pub.old
│   ├── 2020-02-02T12:43:56.460653      previous public storage keys
│   └── 2020-08-03T16:54:12.176642
Note: The above instructions work only for current keystore version 1. New keystore version 2 does not support key destruction at the moment.