Releases: google/fscrypt
Releases · google/fscrypt
Bug and Security Fixes
Improved Compatibility and Easier Builds
This small release makes fscrypt much easier to build and use.
PasswordHash
has completely moved tox/crypto/argon2
, eliminating thelibargon2
build and runtime dependancy. Now the dependancies to build fscrypt arego
,make
,gcc
, and some system headers. That's it! (#84)PasswordHash
will only use at most 128MiB. This allows users to encrypt files on removable media and rest assured that it will still work when plugged into another system with less memory. (#74)- fscrypt's build and CI systems have been greatly improved. All dependancies are now vendored with
dep
allowing for reproducible builds. Building, testing, and changing fscrypt is now much more straightforward. (#83, #85, #86, #88, #89, #90) - Other minor fixes (#70, #75, #87)
Improve Purging and Add Algorithms
This release improves the process of purging keyrings by:
- Fixing #57 where keys would not be cleared on logout if the session keyring was misconfigured.
- Adding #67 to always sync the filesystem metadata when purging keys.
Minor features include:
- Adding cryptographic algorithms from the 4.13 kernel (#64)
- Improving our Travis CI processes (#68, #69)
Features coming in 0.3:
- Major Documentation rewrite (#10)
- Commands to automatically handle ext4 feature flags
- UI refactoring
PAM and Keyrings Stabilization
See the Pull Requests and Closed Issues for more detailed information.
- The PAM module now works without crashing the login process
- Keys work properly when switching between root and non-root users
- Finalized how the keys will be provisioned into the kernel keyring
Initial PAM Module Release
This release introduces the PAM Module and associated documentation.
It also includes numerous bug fixes.
Initial Public Release
This is the version of fscrypt which was first made public on Github.
The redacted commit history from internal development is maintained.