|
Bugzilla – Full Text Bug Listing |
| Summary: | keine Authentifizierung per dovecot nach update; PAM adding faulty module | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Robert Divko <Robert> |
| Component: | Maintenance | Assignee: | Andreas Schwab <schwab> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | frede, maintenance, meissner, Michael.Dobrovnik |
| Version: | Leap 15.4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Robert Divko
2023-09-28 10:49:21 UTC
multiple pam modules affected ssh password login works (obviously) dovecot authentification for imap and pop did work before (6:14) I don’t see crashes of dovecot. Perhaps a module not linked against new glib-c? Error log of dovecot: Sep 28 14:42:09 mailserver dovecot[26284]: auth-worker(26436): conn unix:auth-worker (pid=26287,uid=459): auth-worker<74>: pam(user,ipadress,<4LXqomoGGMtNBHqX>): pam_authenticate() failed: Module is unknown after rollback: zypper in --oldpackage glibc-2.31-150300.52.2 everything works again —> seams to be connected to glibc change Same in OpenSUSE Leap 15.5 testing rollback. Kind Regards, Joerg rollback works! glibc-2.31-150300.58.1 produces strange PAM Errors after some authentications. glibc-2.31-150300.52.2 works without problems. seems this is an update from the SLE update repo. http://download.opensuse.org/update/leap/$releasever/sle/ latest update on the oss repo is 2.31-150300.46.1 (In reply to Robert Divko from comment #5) > after rollback: > zypper in --oldpackage glibc-2.31-150300.52.2 > everything works again > —> seams to be connected to glibc change rollback was from latest 15.4 glibc package: 2.31-150300.58.1 glibc-2.31-150300.52.2 is also the 2nd latest version on Leap 15.5. seems it is shared from the SLE15 Repo. How does it get forwarded to the right people to get it analyzed and fixed? dup *** This bug has been marked as a duplicate of bug 1215891 *** |