Bug 433459 - Plasma Vault doesn't work with cryfs 0.11.0 (git version)
Summary: Plasma Vault doesn't work with cryfs 0.11.0 (git version)
Status: RESOLVED UPSTREAM
Alias: None
Product: Plasma Vault
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR critical
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-23 04:31 UTC by p d
Modified: 2021-02-24 02:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description p d 2021-02-23 04:31:00 UTC
SUMMARY

I use Fedora 33 KDE and have cryfs installed via this copr: https://copr.fedorainfracloud.org/coprs/fcsm/cryfs/ because it isn't available in the standard Fedora repos. This copr repo provides cryfs 0.11.0-dev which is from git. Plasma Vault doesn't work with this git version. When attempting to decrypt the vault, it doesn't invoke the cryfs command at all. Another frontend called SiriKali works, however. https://github.com/mhogomchungu/sirikali

STEPS TO REPRODUCE
1. Install latest unstable cryfs from git
2. Try to decrypt cryfs vault
3. It does nothing

OBSERVED RESULT

Cryfs isn't launched

EXPECTED RESULT

For the cryfs command to start decrypting the vault upon entering the passphrase

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)

Operating System: Fedora 33
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.17-200.fc33.x86_64
OS Type: 64-bit
Graphics Platform: X11

ADDITIONAL INFORMATION

Latest KDE from this copr, but is a problem on stock Fedora kde also https://copr.fedorainfracloud.org/coprs/zawertun/kde/
Comment 1 Ivan Čukić 2021-02-23 11:16:54 UTC
While we don't support unreleased software, this report is extremely useful so that we can get prepared for the next cryfs release. Thanks!

Seems the development version of cryfs has an issue working in an empty environment (cleaned up environment variables which is something vault does for safety reasons - we don't want someone injecting something into the environment to change the behaviour of cryfs behind our backs)

I've opened an upstream issue report:

https://github.com/cryfs/cryfs/issues/374

I'm not going to mark this as resolved/upstream until this is either fixed upstream, or here if the upstream doesn't ant to fix this.
Comment 2 Nate Graham 2021-02-23 16:10:19 UTC
Fixed in cryfs with https://github.com/cryfs/cryfs/commit/c6a69ae36bdfed8b274f1a608de11f0c0445407a
Comment 3 p d 2021-02-24 02:24:13 UTC
I compiled the latest cryfs commit and can confirm it's fixed now.

Thanks very much!