ecryptfs team mailing list archive

[Launchpad Bug Tracker <332331@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package ecryptfs-utils - 72-0ubuntu1

---------------
ecryptfs-utils (72-0ubuntu1) jaunty; urgency=low

  [ Dustin Kirkland ]
  * src/utils/ecryptfs-[u]mount-private: print message about cd $PWD,
    LP: #332331
  * doc/manpage/*: manpage updates
  * debian/ecryptfs-utils.prerm: prevent removal of ecryptfs-utils
    package, if in use, LP: #331085
  * src/utils/ecryptfs-setup-private:
    - allow for LDAP-based logins, LP: #317307
    - add --noautomount, --noautoumount options, LP: #301759

  [ Tyler Hicks ]
  * src/libecryptfs/cipher_list.c: ignore unknown ciphers, LP: #335632
  * doc/manpage/ecryptfs.7: add key sig mount options info, LP: #329491
  * src/utils/mount.ecryptfs.c: scrub unknown option

  [ James Dupin ]
  * doc/manpage/fr/*: initial cut at french manpages

  [ Michal Hlavinka ]
  * src/libecryptfs/module_mgr.c: fix mount parameter handling on
    interactive mounting, LP: #331948

 -- Dustin Kirkland <kirkland@xxxxxxxxxx>   Wed, 18 Mar 2009 18:53:11
-0500

** Changed in: ecryptfs-utils (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
ecryptfs-mount-private mounts the private/home directory, but the pwd is still the unmounted directory
https://bugs.launchpad.net/bugs/332331
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” source package in Ubuntu: Fix Released

Bug description:
Binary package hint: ecryptfs-utils

In the situation where you are in your $HOME or ~/Private, and this directory is unmounted, you can run:
 $ ecryptfs-mount-private

Assuming this mount succeeds, you are good to go.  However, you are still in your unmounted home/private directory.

To solve this, you need to cd to this directory again.  This should definitely be fixed by a one-liner in ecryptfs-mount-private.

:-Dustin