Ubuntu

ecryptfs-migrate-home not migrate files with long names

Reported by Jiří Navrátil on 2011-05-15
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ecryptfs-utils (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: ecryptfs-utils

I migrated home dir on reiserfs to ecryptfs via /usr/bin/ecryptfs-migrate-home command

some files were not migrated, because of long file names

i recommend to add check for file names length supported by ecryptfs prior migration (like check for available free space and used files)

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: ecryptfs-utils 87-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sun May 15 08:34:06 2011
EcryptfsInUse: Yes
ProcEnviron:
 LANGUAGE=cs_CZ:en
 PATH=(custom, user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SourcePackage: ecryptfs-utils
UpgradeStatus: Upgraded to natty on 2011-04-30 (14 days ago)

Martin Spacek (mspacek) wrote :

I'm still trying to figure out how to disable file name encryption in ecryptfs. I know there's an option you can pass while mounting manually, but I can't find anything anywhere about how to set up en encrypted home that automatically never encrypts file names. It would be nice if the `ecryptfs-migrate-home` command had a flag that allowed you to specify exactly that, and hence not make yourself susceptible to bug #344878.

Martine,

I think that next check for all file_names < max_file_name_length is sufficient for script (to not start migration)

your goal is more advanced

BTW do you speak czech?

Best regards

---
Jiri Navratil

21.6.2011 v 2:18, Martin Spacek <email address hidden>:

> I'm still trying to figure out how to disable file name encryption in
> ecryptfs. I know there's an option you can pass while mounting manually,
> but I can't find anything anywhere about how to set up en encrypted home
> that automatically never encrypts file names. It would be nice if the
> `ecryptfs-migrate-home` command had a flag that allowed you to specify
> exactly that, and hence not make yourself susceptible to bug #344878.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/782925
>
> Title:
> ecryptfs-migrate-home not migrate files with long names
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/782925/+subscriptions

> Martine,
>
> I think that next check for all file_names < max_file_name_length is
> sufficient for script (to not start migration)
>
> your goal is more advanced
>
> BTW do you speak czech?
>
> Best regards
>
> ---
> Jiri Navratil
>
>
> 21.6.2011 v 2:18, Martin Spacek <email address hidden>:
>
>> I'm still trying to figure out how to disable file name encryption in
>> ecryptfs. I know there's an option you can pass while mounting manually,
>> but I can't find anything anywhere about how to set up en encrypted home
>> that automatically never encrypts file names. It would be nice if the
>> `ecryptfs-migrate-home` command had a flag that allowed you to specify
>> exactly that, and hence not make yourself susceptible to bug #344878.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/782925
>>
>> Title:
>> ecryptfs-migrate-home not migrate files with long names
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/782925/+subscriptions
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/782925
>
> Title:
> ecryptfs-migrate-home not migrate files with long names
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/782925/+subscriptions

Dustin Kirkland  (kirkland) wrote :

Hi, thanks for the report!

The root cause of this is Bug #344878, so I'm marking it as a duplicate ;-)

hi

my bug can be easily solved by adding next check in script before migration I'm asking for that "only"

please reconsider to leave it separated The original bug dosnt seems to be easily solved

thx

---
Jiri Navratil

22.6.2011 v 1:04, Dustin Kirkland <email address hidden>:

> *** This bug is a duplicate of bug 344878 ***
> https://bugs.launchpad.net/bugs/344878
>
> Hi, thanks for the report!
>
> The root cause of this is Bug #344878, so I'm marking it as a duplicate
> ;-)
>
> ** This bug has been marked a duplicate of bug 344878
> file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/782925
>
> Title:
> ecryptfs-migrate-home not migrate files with long names
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/782925/+subscriptions

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ecryptfs-utils (Ubuntu):
status: New → Confirmed
Gary Brainin (brainin) wrote :

I agree that this should be a separate bug, particularly since #344878 is not going to result in any changes.

In my experience, the ecryptfs-migrate-home script did not end elegantly, but instead stopped with a report of rsync errors. The encrypted directory was set up and worked, but that was not clear from the script output, nor was there any easy way to tell which files were not copied--or, in fact, that failure to copy long filenames was the cause of the error. All I saw was a cryptic numerical rsync error that "some files were not copied."

I would appreciate if the script were updated to better handle this error condition, and give the end-user some indication of whether it otherwise succeeded or failed. Alternately, it wouldn't hurt if there were some indication (other than searching for bug reports) in the instructions for the script that super-long filenames don't work in encrypted mode.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers