| 2017-03-29 17:07:00 |
Mario Lipinski |
bug |
|
|
added bug |
| 2017-04-03 11:18:33 |
mist |
samba (Ubuntu): status |
New |
Incomplete |
|
| 2017-04-03 11:18:35 |
mist |
samba (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2017-04-03 11:20:10 |
mist |
bug |
|
|
added subscriber mist |
| 2017-05-05 19:00:21 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-05-05 21:17:46 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2017-05-08 14:32:57 |
Christian Ehrhardt |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2017-05-08 14:37:56 |
Andreas Hasenack |
samba (Ubuntu): status |
Confirmed |
In Progress |
|
| 2017-05-08 14:37:58 |
Andreas Hasenack |
samba (Ubuntu): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2017-05-08 14:38:00 |
Andreas Hasenack |
samba (Ubuntu): importance |
Undecided |
High |
|
| 2017-05-08 14:40:01 |
Robie Basak |
bug task added |
|
samba (Ubuntu Zesty) |
|
| 2017-05-08 14:57:57 |
Andreas Hasenack |
samba (Ubuntu Zesty): status |
New |
In Progress |
|
| 2017-05-08 14:57:59 |
Andreas Hasenack |
samba (Ubuntu Zesty): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2017-05-08 14:58:05 |
Andreas Hasenack |
samba (Ubuntu Zesty): importance |
Undecided |
High |
|
| 2017-05-08 21:28:43 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/323767 |
|
| 2017-05-08 21:29:11 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-05-08 21:29:14 |
Andreas Hasenack |
tags |
|
patch |
|
| 2017-05-29 10:26:27 |
Filippe LeMarchand |
bug |
|
|
added subscriber Filippe LeMarchand |
| 2017-06-08 19:10:21 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/325329 |
|
| 2017-06-19 12:53:48 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/325929 |
|
| 2017-06-20 13:41:11 |
Launchpad Janitor |
samba (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-06-21 13:04:57 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/326073 |
|
| 2017-06-21 13:33:30 |
Andreas Hasenack |
description |
The pam winbind module seems to be broken on current 17.04 beta2.
Mar 29 18:28:21 daw0 lightdm: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
Mar 29 18:28:21 daw0 lightdm: PAM adding faulty module: pam_winbind.so
I get this error message after a fresh install of Ubuntu GNOME and libpam-winbind when logging in with an account that should not exist anywhere. No winbind configuration done yet, but had seen this error message than also. |
[Impact]
The pam_winbind.so module is unusable in zesty. It won't load because of missing symbols:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
This is due to the (re)introduction of patch fix-1584485.patch which changes the way this module is built, trying to statically link some libraries. That linking was incorrectly done.
The patch was subsequently removed, but later added back again by mistake during a huge sync.
A new version of the patch exists, but upstream (Samba) isn't very fond of such a change and asked to submit it for discussion to the samba-technical mailing list.
That was done, but since this could take some time, we decided it's best to revert the patch one more time.
[Test Case]
In a zesty machine/container:
* sudo apt install libpam-winbind winbind samba
* tail -f /var/log/auth.log
* perform a login on this machine. Via ssh, for example
* the broken version will log this:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
* The fixed version will load winbind just fine, but won't log anything (unless you fully setup winbind). It's easier to add "debug" to the pam_winbind.so lines in /etc/pam.d/common-* files and repeat the login, then you get to see it being loaded in the logs
[Regression Potential]
This reversal has been done before and worked. Right now, the biggest regression potential is to add the broken patch back again.
[Other Info]
Sorry for keeping both bugs open (#1644428 and #1677329), but the history on this issue is a bit complicated with multiple SRUs and regressions. |
|
| 2017-06-21 13:45:25 |
Andreas Hasenack |
description |
[Impact]
The pam_winbind.so module is unusable in zesty. It won't load because of missing symbols:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
This is due to the (re)introduction of patch fix-1584485.patch which changes the way this module is built, trying to statically link some libraries. That linking was incorrectly done.
The patch was subsequently removed, but later added back again by mistake during a huge sync.
A new version of the patch exists, but upstream (Samba) isn't very fond of such a change and asked to submit it for discussion to the samba-technical mailing list.
That was done, but since this could take some time, we decided it's best to revert the patch one more time.
[Test Case]
In a zesty machine/container:
* sudo apt install libpam-winbind winbind samba
* tail -f /var/log/auth.log
* perform a login on this machine. Via ssh, for example
* the broken version will log this:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
* The fixed version will load winbind just fine, but won't log anything (unless you fully setup winbind). It's easier to add "debug" to the pam_winbind.so lines in /etc/pam.d/common-* files and repeat the login, then you get to see it being loaded in the logs
[Regression Potential]
This reversal has been done before and worked. Right now, the biggest regression potential is to add the broken patch back again.
[Other Info]
Sorry for keeping both bugs open (#1644428 and #1677329), but the history on this issue is a bit complicated with multiple SRUs and regressions. |
[Impact]
The pam_winbind.so module is unusable in zesty. It won't load because of missing symbols:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
This is due to the (re)introduction of patch fix-1584485.patch which changes the way this module is built, trying to statically link some libraries. That linking was incorrectly done.
The patch was subsequently removed, but later added back again by mistake during a sync.
A new version of the patch exists (https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/323767), but upstream (Samba and Debian) isn't very fond of such a change and asked me to submit it for discussion to the samba-technical mailing list (https://lists.samba.org/archive/samba-technical/2017-June/121139.html).
That was done, but since this could take some time, we decided it's best to revert the patch again.
[Test Case]
In a zesty machine/container:
* sudo apt install libpam-winbind winbind samba
* tail -f /var/log/auth.log
* perform a login on this machine. Via ssh, for example
* the broken version will log this:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
* The fixed version will load pam_winbind.so just fine, but won't log anything (unless you fully setup winbind). It's easier to add "debug" to the pam_winbind.so lines in /etc/pam.d/common-* files and repeat the login, then you get to see it being loaded in the logs.
[Regression Potential]
This reversal has been done before and worked. Right now, the biggest regression potential is to add the broken patch back again.
Reversing this patch will also reintroduce bug #1584485, but I think the configuration that leads to that bug is asking for trouble and I stated as such in a comment (https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/comments/43). "winbind" should be listed after "files" or "compat", not before.
That being said, it is my opinion that having a working pam_winbind module benefits more users than the amount of users that could be affected by the particular configuration that leads to #1584485.
[Other Info]
Sorry for keeping both bugs open (#1644428 and #1677329), but the history on this issue is a bit complicated with multiple SRUs and regressions. |
|
| 2017-06-21 17:49:20 |
Andreas Hasenack |
description |
[Impact]
The pam_winbind.so module is unusable in zesty. It won't load because of missing symbols:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
This is due to the (re)introduction of patch fix-1584485.patch which changes the way this module is built, trying to statically link some libraries. That linking was incorrectly done.
The patch was subsequently removed, but later added back again by mistake during a sync.
A new version of the patch exists (https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/323767), but upstream (Samba and Debian) isn't very fond of such a change and asked me to submit it for discussion to the samba-technical mailing list (https://lists.samba.org/archive/samba-technical/2017-June/121139.html).
That was done, but since this could take some time, we decided it's best to revert the patch again.
[Test Case]
In a zesty machine/container:
* sudo apt install libpam-winbind winbind samba
* tail -f /var/log/auth.log
* perform a login on this machine. Via ssh, for example
* the broken version will log this:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
* The fixed version will load pam_winbind.so just fine, but won't log anything (unless you fully setup winbind). It's easier to add "debug" to the pam_winbind.so lines in /etc/pam.d/common-* files and repeat the login, then you get to see it being loaded in the logs.
[Regression Potential]
This reversal has been done before and worked. Right now, the biggest regression potential is to add the broken patch back again.
Reversing this patch will also reintroduce bug #1584485, but I think the configuration that leads to that bug is asking for trouble and I stated as such in a comment (https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/comments/43). "winbind" should be listed after "files" or "compat", not before.
That being said, it is my opinion that having a working pam_winbind module benefits more users than the amount of users that could be affected by the particular configuration that leads to #1584485.
[Other Info]
Sorry for keeping both bugs open (#1644428 and #1677329), but the history on this issue is a bit complicated with multiple SRUs and regressions. |
[Impact]
The pam_winbind.so module is unusable in zesty. It won't load because of missing symbols:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
This is due to the (re)introduction of patch fix-1584485.patch which changes the way this module is built, trying to statically link some libraries. That linking was incorrectly done.
The patch was subsequently removed, but later added back again by mistake during a sync.
A new version of the patch exists (https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/323767), but upstream (Samba and Debian) isn't very fond of such a change and asked me to submit it for discussion to the samba-technical mailing list (https://lists.samba.org/archive/samba-technical/2017-June/121139.html).
That was done, but since this could take some time, we decided it's best to revert the patch again.
[Test Case]
In a zesty machine/container:
* sudo apt install libpam-winbind winbind samba
* tail -f /var/log/auth.log
* perform a login on this machine. Via ssh, for example
* the broken version will log this:
Jun 21 13:17:05 zesty-pamwinbind-1677329 systemd: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
* The fixed version will load pam_winbind.so just fine, but won't log anything (unless you fully setup winbind). It's easier to add "debug" to the pam_winbind.so lines in /etc/pam.d/common-* files and repeat the login, then you get to see it being loaded in the logs:
Jun 21 17:48:52 zesty-pamwinbind-1677329 sshd[18052]: pam_winbind(sshd:session): [pamh: 0x56460f355740] ENTER: pam_sm_open_session (flags: 0x0000)
Jun 21 17:48:52 zesty-pamwinbind-1677329 sshd[18052]: pam_winbind(sshd:session): [pamh: 0x56460f355740] LEAVE: pam_sm_open_session returning 0 (PAM_SUCCESS)
[Regression Potential]
This reversal has been done before and worked. Right now, the biggest regression potential is to add the broken patch back again.
Reversing this patch will also reintroduce bug #1584485, but I think the configuration that leads to that bug is asking for trouble and I stated as such in a comment (https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/comments/43). "winbind" should be listed after "files" or "compat", not before.
That being said, it is my opinion that having a working pam_winbind module benefits more users than the amount of users that could be affected by the particular configuration that leads to #1584485.
[Other Info]
Sorry for keeping both bugs open (#1644428 and #1677329), but the history on this issue is a bit complicated with multiple SRUs and regressions. |
|
| 2017-07-13 17:54:30 |
Andreas Hasenack |
attachment added |
|
zesty-revert-static-winbind-1677329.debdiff https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1677329/+attachment/4914215/+files/zesty-revert-static-winbind-1677329.debdiff |
|
| 2017-07-27 13:45:33 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-08-04 18:11:51 |
Brian Murray |
samba (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-08-04 18:11:55 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-08-04 18:11:58 |
Brian Murray |
tags |
patch |
patch verification-needed verification-needed-zesty |
|
| 2017-08-04 20:42:05 |
Andreas Hasenack |
tags |
patch verification-needed verification-needed-zesty |
patch verification-done-zesty verification-needed |
|
| 2017-08-05 22:05:05 |
Marco Antonio Alvarez |
tags |
patch verification-done-zesty verification-needed |
patch verification-done-zesty |
|
| 2017-08-09 18:29:32 |
Nish Aravamudan |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2017-08-14 15:36:30 |
Launchpad Janitor |
samba (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-08-14 15:36:38 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-10-23 20:09:36 |
Andrew Bartlett |
bug watch added |
|
https://bugzilla.samba.org/show_bug.cgi?id=14780 |
|
