Quoting Robie Basak ([email protected]):
> Serge,
>
> ubuntu@panda-test:~$ gcc -o test test.c
> ubuntu@panda-test:~$ ./test
> char is unsigned
>
> Comparing a char to -1 is undefined, so perhaps it's being optimised
> away in this case?
No, run it on an x86 and you'll get 'char is signed'. I was hoping your
arm toolchain was somehow different from mine.
Perhaps my test case was too brief. Could you try:
mkdir /home/ubuntu/.ecryptfs
mkdir /home/ubuntu/a /home/ubuntu/b
cat > /home/ubuntu/.ecryptfs/ab.conf << EOF
/home/ubuntu/a /home/ubuntu/b ecryptfs none 0 0
EOF
ecryptfs-wrap-passphrase /home/ubuntu/ab.sig
(type 'x\n' twice)
then to try the mounting:
ecryptfs-add-passphrase
(type 'x\n')
mount.ecryptfs_private ab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884407
Title:
mount.ecryptfs_private is broken on arm
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/884407/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
