Fix the priority of the PAM module
- Dominant language
- Go
- Stars
- 308
- Forks
- 41
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 58
Description
> If that works, go back to the default (by restoring the file or purging authd and installing it again), then modify `/usr/share/pam-configs/authd` so that (ignore the paths, only the changed lines):
>
>
>
> ```diff
>
> diff --git a/debian/pam-configs/authd.in b/debian/pam-configs/authd.in
>
> index 15528e92..808bbbda 100644
>
> --- a/debian/pam-configs/authd.in
>
> +++ b/debian/pam-configs/authd.in
>
> @@ -5,7 +5,7 @@ Priority: 1050
>
> Auth-Type: Primary
>
> Auth:
>
> [success=end ignore=ignore default=die] pam_authd_exec.so @AUTHD_DAEMONS_PATH@/authd-pam
>
> -Account-Type: Additional
>
> +Account-Type: Primary
>
> Account:
>
> [default=ignore success=ok user_unknown=ignore] pam_authd_exec.so @AUTHD_DAEMONS_PATH@/authd-pam
>
> Password-Type: Primary
>
>
>
> ```
>
>
>
> And run `pam-auth-update --disable authd` and enable it again `pam-auth-update --enable authd` (or just run `pam-auth-update` to rely on its UI to toggle it).
_Originally posted by @3v1n0 in [#665](https://github.com/canonical/authd/issues/665#issuecomment-2514703947)_
Contributor guide
Research direction
Open debian/pam-configs/authd.in and compare the Account-Type setting with the change shown in the issue. Apply the priority adjustment, then use pam-auth-update to disable and re-enable authd and verify that the generated PAM configuration reflects the intended setting.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100