Bug#951570: fscrypt 2.5 unlock does work well with --user=$USER

[Eric Valette]

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/xxxx/mySafe
Result=$?
exit $Result

If the first unlock fails, then I have to cancel the script and restart. 
Even after I entered the right passwd.

-- eric