fscrypt.git/README.md, branch v0.3.5 Go tool for managing Linux filesystem encryption README.md: remove old warning about ext4 encryption on removable media 2024-02-17T21:38:07+00:00 Eric Biggers ebiggers@google.com 2024-02-17T21:31:27+00:00 2bf4521e3d3fd1c5b5a383defd1535d929ad808b This warning is only applicable for systems with kernel versions older than v4.1, which is now too old to be worth the mention here. 
This warning is only applicable for systems with kernel versions older
than v4.1, which is now too old to be worth the mention here.
README.md: update documentation about alternatives 2024-02-17T21:29:01+00:00 Eric Biggers ebiggers@google.com 2024-02-17T21:17:01+00:00 c74be8ce5ba5fd123f38e22868cab43fe40753a3 






README.md, errors.go: CephFS now supports fscrypt
2023-11-03T05:05:07+00:00

Eric Biggers
ebiggers@google.com

2023-11-03T05:05:04+00:00

6c5fc571ba7b851e7b36b054fd428bf6ad779dcc












Bump up required Go version to 1.18
2023-09-09T22:54:30+00:00

Eric Biggers
ebiggers@google.com

2023-09-09T22:52:08+00:00

43869584b3c9f9acade09d2d35b20e69623d98f8












README.md: don't recommend 'go get'
2023-09-09T21:46:23+00:00

Eric Biggers
ebiggers@google.com

2023-09-09T21:43:01+00:00

ed87812bb4d1fb37c66671f3eb598ac6194bc35c

With the latest version of go, the recommended 'go get' commands fail:

    go: go.mod file not found in current directory or any parent directory.
            'go get' is no longer supported outside a module.
            To build and install a command, use 'go install' with a version,
            like 'go install example.com/cmd@latest'
            For more information, see https://golang.org/doc/go-get-install-deprecation
            or run 'go help get' or 'go help install'.

Replace them with commands that work.





With the latest version of go, the recommended 'go get' commands fail:

    go: go.mod file not found in current directory or any parent directory.
            'go get' is no longer supported outside a module.
            To build and install a command, use 'go install' with a version,
            like 'go install example.com/cmd@latest'
            For more information, see https://golang.org/doc/go-get-install-deprecation
            or run 'go help get' or 'go help install'.

Replace them with commands that work.







Add a NEWS file
2023-01-31T06:59:20+00:00

Eric Biggers
ebiggers@google.com

2023-01-31T06:59:20+00:00

a72760aa794e7714496074a0264314d26fa3b4c8

Copy the GitHub release notes into a NEWS.md file so that the release
notes are included in the actual git repo.  This way, they aren't hidden
away in GitHub, where they require an internet connection to access and
will be lost if GitHub ever goes away.  This also makes the release
notes be properly versioned; GitHub allows past release notes to be
edited, and there doesn't seem to be any record of what changed.

Finally, this allows packages to install the release notes into
/usr/share/doc/$pkgname/, as is the usual convention.





Copy the GitHub release notes into a NEWS.md file so that the release
notes are included in the actual git repo.  This way, they aren't hidden
away in GitHub, where they require an internet connection to access and
will be lost if GitHub ever goes away.  This also makes the release
notes be properly versioned; GitHub allows past release notes to be
edited, and there doesn't seem to be any record of what changed.

Finally, this allows packages to install the release notes into
/usr/share/doc/$pkgname/, as is the usual convention.







Make pam_fscrypt.so support the unlock_only option
2022-10-20T03:47:57+00:00

Eric Biggers
ebiggers@google.com

2022-10-18T17:12:02+00:00

295c503a77f53b87305bba310e37cbdd9b516936

Now that it's been requested by users, bring back the "unlock_only"
option, which was originally proposed as part of
https://github.com/google/fscrypt/pull/281 but was dropped in the final
version of that pull request.

Resolves https://github.com/google/fscrypt/issues/357





Now that it's been requested by users, bring back the "unlock_only"
option, which was originally proposed as part of
https://github.com/google/fscrypt/pull/281 but was dropped in the final
version of that pull request.

Resolves https://github.com/google/fscrypt/issues/357







Add support for AES_256_HCTR2 filenames encryption
2022-10-20T03:45:51+00:00

Eric Biggers
ebiggers@google.com

2022-10-18T17:02:50+00:00

632d66d6fddfa9fd0a279a1811ced1efc567be29

Support for AES_256_HCTR2 filenames encryption was added in kernel
version 6.0.  The kernel doesn't yet support AES_256_HCTR2 for contents
encryption.





Support for AES_256_HCTR2 filenames encryption was added in kernel
version 6.0.  The kernel doesn't yet support AES_256_HCTR2 for contents
encryption.







Add lustre to allowed filesystems and update documentation
2022-04-09T03:28:17+00:00

Eric Biggers
ebiggers@google.com

2022-04-09T03:08:42+00:00

8ac0e607c236e42df8943b9575da1579fe670b76












Bump up required Go version to 1.16
2022-04-08T23:08:12+00:00

Eric Biggers
ebiggers@google.com

2022-04-08T22:55:58+00:00

657a1f0f44b61725f1b8041bceef6f262ffcb770

Bump up the required Go version to 1.16 so that we can assume that Go
modules are enabled by default.  Go 1.16 is the latest end-of-life
release, so this makes it so that we support the latest end-of-life
release (1.16), the current maintainance release (1.17), the current
release (1.18), and future releases.  This the same approach we took
when we last bumped up the required Go version.

Also update the ci.yml file to test with these versions.





Bump up the required Go version to 1.16 so that we can assume that Go
modules are enabled by default.  Go 1.16 is the latest end-of-life
release, so this makes it so that we support the latest end-of-life
release (1.16), the current maintainance release (1.17), the current
release (1.18), and future releases.  This the same approach we took
when we last bumped up the required Go version.

Also update the ci.yml file to test with these versions.