It's segfaulting because of this odd usage of crypt(3):
sent_pw = (char *) crypt(sent_pw, real_pw);
That returns NULL, because in the SHA case the real_pw contains the {
character which is invalid for the second parameter which is meant to be
the salt.
Later on strcmp is
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1272857
Title:
Double free in libapache2-mod-auth-pgsql causes Apache to crash
To manage notifications about
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: apache2 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
I'll change this bug to "low" because to be affected one has to change
the profile from complain (the default) to enforce.
** Changed in: sssd (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
I filed bug #1699576 for the missing chown capability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1689387
Title:
SSSD Prevented from Notifying Systemd on Startup by Apparmor
To
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu)
Status: New => In Progress
** Changed in: sssd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
When starting sssd, we can see warning in the logs when apparmor is in
complain mode:
Jun 21 18:36:52 15-89 kernel: [ 1641.660315] audit: type=1400
audit(1498070212.069:72): apparmor="ALLOWED" operation="capable"
profile="/usr/sbin/sssd" pid=26257 comm="sssd" capability=0
** Description changed:
[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
** Description changed:
[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
** Bug watch added: Debian Bug tracker #865463
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865463
** Also affects: lvm2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865463
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
I'm marking this bug as "new" again because of the package change (from
docker.io to lvm2), to allow it to be triaged again in this new context.
** Changed in: lvm2 (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Summary changed:
- Missing thin-provisioning-tools prevent VG from being activated
+ Missing thin-provisioning-tools prevent VG from being (de)activated
** Description changed:
- I had configured thin-pool storage driver for docker on one of the PowerVM
lapr. And had created containers.
-
** Description changed:
[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
** Description changed:
[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
** Description changed:
- The pam winbind module seems to be broken on current 17.04 beta2.
+ [Impact]
- 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:
** Description changed:
- After performing a system update one of my users was no longer able to
- authenticate against Active Directory. This is on a Ubuntu 14.04 on
- amd64.
+ [Impact]
- The error in /var/log/auth.log was:
+ The pam_winbind.so module is unusable in zesty. It won't load
** Changed in: samba (Ubuntu Zesty)
Status: New => In Progress
** Changed in: samba (Ubuntu Zesty)
Importance: Undecided => High
** Changed in: samba (Ubuntu Zesty)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a
17 matches
Mail list logo
