https://bugs.kde.org/show_bug.cgi?id=452442
--- Comment #4 from florianhilgenb...@googlemail.com --- Thank you for elaborating. I am locking via Auto start instantly after Autologin. That for first user interaction is to enter password, thatfor I don't care what happens after login, I care about after unlocking. Let me elaborate since I got a feeling to not have explained myself very well. Desired Process: 1. Auto login, kwallet locked 2. Autostart triggers loginctl lock-session 3. User unlocks from lockscreen 4. Kwallet gets password from the unlock process. I can't see how that is another security issue than unlock the wallet upon manual login. If this is still declined, I won't force it anymore. Thank you :) On Mon, 11 Apr 2022, 20:36 Nate Graham, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=452442 > > --- Comment #3 from Nate Graham <n...@kde.org> --- > Theoretically yes, but to implement that we would have to punch a security > hole > in the screen locker that would make it less secure. Also it wouldn't > solve the > problem because the lock screen and the login screens are separate things. > The > wallet still wouldn't unlock at *login*. > > Really, if you have auto-login on, I'm not sure how much sense it makes to > use > a lock screen at all. Clearly security is not a major concern in such a use > case. :) > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
