Description of problem: Our cryfs 0.9.10 is a year old, while development have progressed, improving performance, security, integrity, easier use etc, and also adding windows client ( = more useful on Mageia too) The 0.10.x versions have a different filesystem but thankfully can migrate from 0.9.10 - which is the one we have :) Reading the changelog https://github.com/cryfs/cryfs/releases i can not see a problem, and if packaged in mga7-64 testing i can do real life testing of filesystem migration and syncing the encrypted folder by means of our NextCloud client.
It sounds like 0.10.x wouldn't be an appropriate stable update per our policies, but 0.9.11 would have all of the same fixes.
Assignee: bugsquad => geiger.david68210
I find 0.9.11 only have one fix over 0.9.10, regarding a race condition: https://github.com/cryfs/cryfs/compare/0.9.10...0.9.11 0.10.x have a plenty of fixes and improvements regarding speed and security. https://github.com/cryfs/cryfs/compare/0.9.10...0.10.2 I guess the file system change (though automatic) is the culprit for not putting in updates? (downgrading after filesystem change wont work with old data!) But we definately want 0.10.x in mga8. And backport to mga7 would be nice :)
Keywords: (none) => BackportVersion: 7 => Cauldron
Latest 0.10.2 release now in Cauldron! I can't update for mga7 as we need libcryptopp >= 8.0. So let's close this bug.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Nice, thanks :)