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 migrate- home` command had a flag that allowed you to specify /bugs.launchpad .net/bugs/ 782925 migrate- home not migrate files with long names /bugs.launchpad .net/ubuntu/ +source/ ecryptfs- utils/+ bug/782925/ +subscriptions
> 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-
> 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:/
>
> Title:
> ecryptfs-
>
> To manage notifications about this bug go to:
> https:/