eCryptfs 102

Milestone information

Dustin Kirkland 
Release registered:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon ecryptfs-utils_102.orig.tar.gz (md5, sig) release tarball 129
last downloaded 2 weeks ago
Total downloads: 129

Release notes 

[ Dustin Kirkland ]
  * debian/control:
    - bump standards, no change

  [ Tyler Hicks ]
  *, scripts/,
    - Break out the autoreconf and intltoolize commands from into
      an executable
    - Use the --copy option when invoking intltoolize
    - Include the new script in the release tarball
  * debian/rules, debian/control:
    - Use dh-autoreconf so that upstream sources can easily be used to build
      packages for all the stable Ubuntu releases in the ecryptfs-utils daily
      build PPA
    - Override the dh_autoreconf target by running the script
    - Drop Build-Depends on autotools-dev since dh-autoreconf is a superset of
    - Drop Build-Depends on autoconf, automake, and libtool since
      dh-autoreconf depends on all of these packages
  * m4/ac_python_devel.m4:
    - Fix FTBFS in Raring Ringtail due to multiarch Python. Be sure to include
      platform specific Python include directions in SWIG_PYTHON_CPPFLAGS.
  * src/utils/mount.ecryptfs_private.c:
    - Fix conditionals when checking whether to remove authentication tokens
      from the kernel keyring upon umount. This conditional was incorrectly
      modified in ecryptfs-utils-101, yet the authentication tokens still seem
      to be removed from the kernel keyring so it isn't clear if there was
      actually a user-facing regression.
    - Pass the FEKEK sig, rather than the FNEK sig, to
    - Restore behavior of not printing error messages to syslog when
      unmounting and keys cannot be found in the kernel keyring.
    - Restore behavior of printing a useful error message about
      ecryptfs-mount-private when mounting and keys cannot be found in the
      kernel keyring
    - Fix memory leak and clean up free()'s in an error path
    - Use pointer assignment tests, rather than strlen(), to determine which
      key signatures were fetched
  * src/daemon/main.c, src/include/ecryptfs.h,
    doc/manpage/ecryptfsd.8, doc/design_doc/ecryptfs_design_doc_v0_2.tex:
    - Remove netlink messaging interface support
    - Netlink messaging support was superceded by the miscdev interface
      (/dev/ecryptfs) in upstream kernel version 2.6.26 in July, 2008
    - Netlink messaging support was completely removed from the upstream
      kernel starting with version 2.6.32 in December, 2009
  * src/jprobes/*, scripts/
    - Remove all jprobes code, as I don't use jprobes to debug eCryptfs kernel
      issues and I don't like the idea of maintaining these jprobes outside of
      the kernel tree
  * src/escrow/*:
    - Remove all escrow code, as it isn't used or maintained
  * tests/kernel/, tests/kernel/llseek/test.c,
    tests/userspace/, tests/userspace/wrap-unwrap/test.c:
    - Migrate some old testcases over to the modern test framework
  * tests/lib/
    - Update etl_create_test_dir() to allow a parent directory to be specified
      when creating the directory
  * src/testcases:
    - Delete old testcases that were either too basic, covered by more
      extensive tests in the modern test framework, or just didn't work

  [ Nobuto MURATA ]
  * src/desktop/ecryptfs-record-passphrase:


This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.