diff options
| author | Yu Watanabe <watanabe.yu+github@gmail.com> | 2024-03-26 20:07:49 +0100 |
|---|---|---|
| committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2024-03-26 20:07:51 +0100 |
| commit | 193134de54e1bc9a35368d68e5631c097f301ea8 (patch) | |
| tree | 0a5ff10f20317be50c61e3fb820bab4f0995b266 /src | |
| parent | Merge pull request #31951 from bluca/resolve_reload (diff) | |
| download | systemd-193134de54e1bc9a35368d68e5631c097f301ea8.tar.xz systemd-193134de54e1bc9a35368d68e5631c097f301ea8.zip | |
home: fix typo
Follow-up for 5ec87d577f92effe27a62e965e02a6f9a40f81cc.
Diffstat (limited to 'src')
| -rw-r--r-- | src/home/homework.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/home/homework.c b/src/home/homework.c index 4fccafcb60..7865772db2 100644 --- a/src/home/homework.c +++ b/src/home/homework.c @@ -72,7 +72,7 @@ int user_record_authenticate( * The 'cache' parameter might also contain the LUKS volume key, loaded from the kernel keyring. * In this case, authentication becomes optional - if a secret section is provided it will be * verified, but if missing then authentication is skipped entirely. Thus, callers should - * consider carefuly whether it is safe to load the volume key into 'cache' before doing so. + * consider carefully whether it is safe to load the volume key into 'cache' before doing so. * Note that most of the time this is safe, because the home area must be active for the key * to exist in the keyring, and the user would have had to authenticate when activating their * home area; however, for some methods (i.e. ChangePassword, Authenticate) it makes more sense |