| 1 |
(v3: amended with KDE Plasma Vaults) |
| 2 |
|
| 3 |
Title: sys-fs/cryfs-0.10.2 update |
| 4 |
Author: Andreas Sturmlechner <asturm@g.o> |
| 5 |
Content-Type: text/plain |
| 6 |
Posted: 2019-10-28 |
| 7 |
Revision: 1 |
| 8 |
News-Item-Format: 1.0 |
| 9 |
Display-If-Installed: <sys-fs/cryfs-0.10 |
| 10 |
|
| 11 |
Filesystems created with CryFS 0.9.x are incompatible with the new storage |
| 12 |
format. [1] Migration is necessary before mounting with CryFS 0.10 and |
| 13 |
possible for old containers going back as far as CryFS 0.9.4. [2] |
| 14 |
|
| 15 |
However, upstream recommend to create new containers with 0.10 to avoid |
| 16 |
potential data loss from a failed migration, and in order to benefit from all |
| 17 |
performance advantages of the new format. |
| 18 |
|
| 19 |
Before updating, copy all data from cryfs containers to a temporary and secure |
| 20 |
location. After the update, move it back into a newly created container. Don't |
| 21 |
forget to remove the temporary files afterwards. |
| 22 |
|
| 23 |
Users of KDE Plasma Vaults should follow the same procedure. To check the type |
| 24 |
of existing containers, open them using the Vaults widget. It is part of the |
| 25 |
path as displayed in dolphin. |
| 26 |
|
| 27 |
[1] https://bugs.gentoo.org/690324 |
| 28 |
[2] https://github.com/cryfs/cryfs/releases/tag/0.10.1 |
Archives