2. I just uploaded version 0.2.6-1 of the fscrypt package. Once the new
version becomes available in the archive could you check if the problem
is still present?
Yes and BTW even without --user= I also get the problem.
#!/bin/bash
fscrypt unlock /home//mySafe
Result=$?
exit $Result
If
On 3/4/20 3:58 PM, Paride Legovini wrote:
> are you sure that in your backup script $USER expands to the username
you want and not to 'root', given that you run it as root? You could try
adding a 'set -x' right after the script's shebang to check how the
commands are being called.
In fact to n
Eric Valette wrote on 18/02/2020:
> 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 unlo
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 ti
4 matches
Mail list logo
