From 7a17e3a0f1e9c0dfa7eae11816f55c820f689d4f Mon Sep 17 00:00:00 2001 From: Eric Biggers Date: Fri, 27 Dec 2024 16:08:52 -0800 Subject: [PATCH] README.md: fix a typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ed31ea1..58fd870 100644 --- a/README.md +++ b/README.md @@ -88,7 +88,7 @@ Before using `fscrypt`, you should consider other solutions: `systemd-homed` has better integration with systemd than `fscrypt` does. However, `systemd-homed` (as of systemd v255) uses the ["V1" Linux kernel encryption API](https://www.kernel.org/doc/html/v6.8/filesystems/fscrypt.html#limitations-of-v1-policies), - while `fscrypt` perfers the "V2" API. The older API causes + while `fscrypt` prefers the "V2" API. The older API causes [known issues](#some-processes-cant-access-unlocked-encrypted-files), and migrating `systemd-home` to the "V2" API is tracked [in this `systemd` issue](https://github.com/systemd/systemd/issues/18280). -- 2.39.5