aboutsummaryrefslogtreecommitdiff
path: root/cli-tests/t_encrypt_login.out
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2021-12-19 21:19:25 -0600
committerEric Biggers <ebiggers@google.com>2021-12-19 21:44:59 -0600
commit4c7c6631cc5a27cc6b4431f5ad3805a2d624c5f5 (patch)
treeb22856e0d3392a2def633d961ad29c2890ce4fb2 /cli-tests/t_encrypt_login.out
parent360467d0df626d2d0eac003a0a210814910804ce (diff)
Set owner of login protectors to correct user
When the root user creates a login protector for a non-root user, make sure to chown() the protector file to make it owned by the user. Without this, the protector cannot be updated by the user, which causes it to get out of sync if the user changes their login passphrase. Fixes https://github.com/google/fscrypt/issues/319
Diffstat (limited to 'cli-tests/t_encrypt_login.out')
-rw-r--r--cli-tests/t_encrypt_login.out2
1 files changed, 2 insertions, 0 deletions
diff --git a/cli-tests/t_encrypt_login.out b/cli-tests/t_encrypt_login.out
index c531f73..220d901 100644
--- a/cli-tests/t_encrypt_login.out
+++ b/cli-tests/t_encrypt_login.out
@@ -111,6 +111,8 @@ PROTECTOR LINKED DESCRIPTION
desc19 Yes (MNT_ROOT) login protector for fscrypt-test-user
desc20 No custom protector "Recovery passphrase for dir"
+Protector is owned by fscrypt-test-user:fscrypt-test-user
+
# Encrypt with login protector with --no-recovery
ext4 filesystem "MNT" has 1 protector and 1 policy