Quoting Robie Basak (<email address hidden>):
> 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:
Quoting Robie Basak (<email address hidden>): panda-test: ~$ gcc -o test test.c panda-test: ~$ ./test
> Serge,
>
> ubuntu@
> ubuntu@
> 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 .ecryptfs/ ab.conf << EOF wrap-passphrase /home/ubuntu/ab.sig
mkdir /home/ubuntu/a /home/ubuntu/b
cat > /home/ubuntu/
/home/ubuntu/a /home/ubuntu/b ecryptfs none 0 0
EOF
ecryptfs-
(type 'x\n' twice)
then to try the mounting:
ecryptfs- add-passphrase private ab
(type 'x\n')
mount.ecryptfs_