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 not give any indication of real login name I put $USER in the bug report description but in the script it is my real login id.
Upstream ansered BTW that since the code is accessed by root, it should be --user=root and not my login i but the problem is not there it is as if, the fscrypt keyboard input is not correctly received when called from a shell script. I copied the past phrase after checking in another windows and still it does not always open. Fortunately, sometimes it works...
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?
I will do but as I also want to change the fscrypt policy to 2 and this requires reinit of the full fscrypt setup as far as I understand. I need to open my safe, move it elsewhere, delete the fscrypt protected directory, probably remove the root .fscrypt directory and redo a fscrypt setup. and copy back to the directory So it will take time because I have to do it also for the backup...
3. Could you provide a pointer to the upstream bug you filed?
Sure it is in the fscrypt upstream git in the bug section https://github.com/google/fscrypt/issues/199
Thanks for providing the 2.6 version. -- eric
