eCryptfs 77
Milestone information
- Project:
- eCryptfs
- Series:
- trunk
- Version:
- 77
- Released:
- Registrant:
- Dustin Kirkland
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
[ Dustin Kirkland ]
* src/libecryptfs
revert the zombie code removal from pam_ecryptfs as it seems this
bit is still needed; fix the source of the problem introduced in
commit r407; check for non-zero return codes; this problem would
manifest itself as a) unable to unlock screensaver, b) unable to
switch users, c) unable to mount home folder on initial login;
LP: #402222, #402029
* src/utils/
ids on removal
* src/utils/
due to open sessions; handle this in ecryptfs-
the flock() blocking; use /dev/shm for counter; add an iterator to the
counter file to prevent users from DoS'ing one another from accessing
their encrypted directories, LP: #402745
* debian/
* configure.ac: link against pam, silence shlib warning
* src/include/
src/
src/
mount.
fetch_
mount.
the ecryptfs.h headers; this will allow us to short-circuit some of the
costly key-loading code on pam_auth if the private dir is already
mounted, speeding up some subsequent authentications significantly,
LP: #402748
* doc/ecryptfs-
more user friendly
* src/utils/
.ecryptfs and .Private data in /home/.ecryptfs rather than /var/lib,
as users are forgetting to backup /var/lib, and are often putting
/home on a separate partition; furthermore, this gives users a place
to access their encrypted data for backup, rather than hiding the
data below $HOME, LP: #371719
[ Tyler Hicks ]
* src/libecryptfs
add blowfish/56-bytes to the list of ciphers we officially support,
LP: #402790
Changelog
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.