Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README.md: fix a typo #420

Merged
merged 1 commit into from
Dec 28, 2024
+1 −1
Merged

README.md: fix a typo #420

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Original file line number Diff line number Diff line change
@@ -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).