** Attachment added: "This patch fixes the problem. It applies against 2.6.29-rc3, but may or may not apply against the Ubuntu kernel. I will test a little more before sending it upstream." http://launchpadlibrarian.net/21787775/0001-eCryptfs-Regression-in-unencrypted-filename-symlin.patch
-- ecryptfs does not handle symlinks within bzr https://bugs.launchpad.net/bugs/322532 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in “bzr” source package in Ubuntu: New Status in “ecryptfs-utils” source package in Ubuntu: Confirmed Status in “linux” source package in Ubuntu: New Bug description: Binary package hint: ecryptfs-utils I have an encrypted ~/Private directory. If I have a bzr tree with symlinks in it, then the bzr tree is corrupted and unusable. Attached is a tarball of a bzr tree. Here is how to reproduce: $ tar -zxvf ./bzr_links.tar.gz bzr_links/ bzr_links/.bzr/ bzr_links/.bzr/repository/ ... bzr_links/bar bzr_links/foo $ cd bzr_links/ $ bzr status modified: bar@ $ bzr diff bzr: ERROR: The dirstate file (DirState(u'/home/jamie/Private/tmp/bzr_links/.bzr/checkout/dirstate')) appears to be corrupt: Bad parse, we expected to end on \n, not: 51 [email protected]: (('', 'bar', 'bar-20090128230356-oc73poh1gp2zfkho-1'), [('l', 'foo', 0L, 0, 'n'), ('AAAAA0mA6eVJgOnlAAAAGQAQow4AAKH/', 'l', 0L, 0, 'n')]) Do the above in a non-encrypted directory (on an ext3 partition) yields: $ tar -zxvf ./bzr_links.tar.gz bzr_links/ bzr_links/.bzr/ bzr_links/.bzr/repository/ ... bzr_links/bar bzr_links/foo $ cd bzr_links/ $ bzr status $ bzr diff $ The bzr tree was created like so: $ mkdir bzr_links $ cd bzr_links $ bzr init $ touch foo $ bzr add $ bzr ci $ ln -s foo bar $ bzr add $ bzr ci $ cd ../ $ tar -zcvf ./bzr_links.tar.gz ./bzr_links _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
