GNU bug report logs -
#77203
[PATCH 0/4] gnu: Add fscrypt.
Previous Next
Reported by: 45mg <45mg.writes <at> gmail.com>
Date: Sun, 23 Mar 2025 10:23:02 UTC
Severity: normal
Tags: patch
Done: Leo Famulari <leo <at> famulari.name>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 8 Apr 2025 20:28:58 -0400
with message-id <Z_W_SvbmG8B1xbM7 <at> jasmine.lan>
and subject line Re: [PATCH v2 0/4] Linux native filesystem encryption (fscrypt).
has caused the debbugs.gnu.org bug report #77203,
regarding [PATCH 0/4] gnu: Add fscrypt.
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
77203: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=77203
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Hi Guix,
The following patch series adds support for Linux native filesystem encryption
to Guix, via the `fscrypt` kernel interface and associated userspace tools
`fscrypt` and `fscryptctl`.
Patch 1/4 enables the relevant kernel configuration option,
CONFIG_FS_ENCRYPTION. This is the same patch as #77202 [1].
Patch 2/4 and 3/4 add the high-level `fscrypt` command-line utility (which is
implemented in Go); these are the same patches as #77174 [2].
Patch 4/4 adds `fscryptctl`, a lower-level tool written in C; this is the same
patch as #77175 [3].
I thought it would be good to group all these patches in a single series, so
I'll close #77202, #77174 and #77175 in favor of this one.
Further reference:
https://docs.kernel.org/filesystems/fscrypt.html
https://github.com/google/fscrypt?tab=readme-ov-file#runtime-dependencies
https://github.com/google/fscryptctl
[1] https://yhetil.org/guix/4a6e1c443ee07929cd582395bdcc5865610569f2.1742723412.git.45mg.writes <at> gmail.com/
[2] https://yhetil.org/guix/cover.1742646222.git.45mg.writes <at> gmail.com/
[3] https://yhetil.org/guix/933a717801203ce2e23173a8cebb957c153cdbd8.1742648529.git.45mg.writes <at> gmail.com/
45mg (4):
gnu: linux-libre: Enable CONFIG_FS_ENCRYPTION.
gnu: Add go-github-com-wadey-gocovmerge.
gnu: Add fscrypt.
gnu: Add fscryptctl.
gnu/packages/crypto.scm | 33 +++++++++++++++
gnu/packages/golang-crypto.scm | 74 +++++++++++++++++++++++++++++++++-
gnu/packages/golang-xyz.scm | 26 ++++++++++++
gnu/packages/linux.scm | 2 +
4 files changed, 134 insertions(+), 1 deletion(-)
base-commit: fbfd2b93831978aadbb96f32cafdab997b04c6c6
--
2.49.0
[Message part 3 (message/rfc822, inline)]
On Mon, Apr 07, 2025 at 06:44:40AM +0000, 45mg wrote:
> From that page and from the test I described above, it looks like
> CONFIG_FS_ENCRYPTION is the only option that's strictly necessary for
> the default encryption mode.
>
> The other options mentioned in the docs seem to be either (1) for using
> other encryption modes, or (2) for hardware acceleration, which is
> platform-specific. I don't have any need for (1) so I probably won't
> look into it in the near future. Once this patch series is merged and I
> start relying on fscrypt, I should get an idea of the performance
> situation; at that point I might look into (2) if I feel that the
> un-accelerated performance isn't good enough.
>
> (In the meantime, of course, anyone else is welcome to look into it.)
Sounds good! I pushed the patches as
bf6736bd878a14e0520a550bf8fbf8edb69876df
Thanks for working on this!
This bug report was last modified 42 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.