Package: fscrypt
Version: 0.2.5-2
Severity: normal
Tags: upstream
I have a pc backup script running rsync that runs as root. As a normal user I
created
a protected directory call it mysafe.
When I do as a normal user ($USER)
fscrypt unlock /home/$USER/mysafe
I open the safe almost the fisrt time (pasword is long and I may make a typo
once).
When in the backup script, run as root I do:
fscrypt unlock /home/$USER/mysafe --user=$USER
I can enter the password twenty time without sucess.
It was working well before I switched to fscrypt 2.5 and 5.4 kernel. I often
need to log
in and open safe as $USER as the script does:
fscrypt status ${SAFE_LOCATION} | grep -q "Unlocked: Yes"
before trying to unlock...
I reported this upstream.
NB: a 2.6 version as been published January 30.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.20 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fscrypt depends on:
ii libc6 2.30-0experimental2
ii libpam0g 1.3.1-5
fscrypt recommends no packages.
Versions of packages fscrypt suggests:
pn libpam-fscrypt <none>
-- no debconf information
