It's a documented side effect that initialization of secure memory in gcrypt
drops privileges if getuid() != geteuid(). This results in breaking setuid
callers, like sudo or su.
Details
Details
- Reviewers
mart - Group Reviewers
Plasma - Commits
- R107:1a01e1eb870e: Avoid dropping privileges by initializing gcrypt secmem
Can use sudo again when pam_kwallet is involved.
Diff Detail
Diff Detail
- Repository
- R107 KWallet PAM Integration
- Branch
- patch3
- Lint
No Linters Available - Unit
No Unit Test Coverage
Comment Actions
Not closed automatically...
https://commits.kde.org/kwallet-pam/1a01e1eb870e1ab1d96a8641f1f3500af646c974