homed: don't insist on authentication against host-copy user record
authorLennart Poettering <lennart@poettering.net>
Wed, 20 May 2020 16:38:07 +0000 (18:38 +0200)
committerLennart Poettering <lennart@poettering.net>
Thu, 21 May 2020 21:39:30 +0000 (23:39 +0200)
commitc8f145adbb17fb448a78cfaf65f67f22026e6792
tree64c56cb68b6d588576d827b860553e030e847d1d
parent1a53adb3aba43405c204aeb22a544323f1ea4949
homed: don't insist on authentication against host-copy user record

homed maintains two or three copies of the user's identity record per
home directory: one on the host, one inside the LUKS header, and one
embedded in the home directory.

Previously we'd insist that if a user logs in they have to authenticate
against all three, as a safety feature. This broke logging into
unfixated records however, since in that case the host version is
synthetic and thus does not carry any authentication data.

Let's hence losen the strictness here: accept authentication against
host records that carry no auth data. This should be safe as we know
after all that the second/third record will catch invalid accesses.

Fixes: #15178
src/home/homework-luks.c
src/home/homework.c
src/home/homework.h