I'm still getting the error with the new package. What kind of config
items would I need submit to re-open a diff bug?
foo:/root # apt-get install sssd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libipa
This bug was fixed in the package sssd - 1.8.6-0ubuntu0.2
---
sssd (1.8.6-0ubuntu0.2) precise-proposed; urgency=low
* rules: Really install the new pam-auth-update file for password
changes. (LP: #1086272)
* rules: Pass --datadir, so the path in autogenerated python files is
1.8.6-0ubuntu0.2 solved the "User not known to the underlying
authentication module" for /etc/passwd users for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error
Verification passed on 12.04:
Linux Mark-Aurel 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
sssd Version: 1.8.6-0ubuntu0.2
libpam-sss Version: 1.8.6-0ubuntu0.2
Fixes pam error problem caused by libpam-sss and sssd (User not known to
the underlying au
** Changed in: sssd (Ubuntu Precise)
Milestone: ubuntu-12.04.2 => ubuntu-12.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when exiting su session
To ma
verified it myself
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when exiting su session
Hello Mark, or anyone else affected,
Accepted sssd into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/sssd/1.8.6-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Adam
What setup/config are you after? Sorry only just seen this comment after I hit
the bug again on Precise and 1.8.2-0ubuntu1.
I'm using sssd in PAM to do LDAP auth against a 389 directory server.
Prior to upgrade I saw this in logs:
Jan 11 14:50:41 webdev01 su[28656]: pam_unix(su:session): s
** Description changed:
+ [Impact]
+ PAM returns an error when exiting from an su session. Fixed upstream by
moving SELinux processing to the account stack.
+
+ [Test case]
+ Install sssd, 'su - $localuser; exit; echo $?'
+
+ [Regression potential]
+ small, included upstream for months, backpor
Iggywig,
Would you be willing to share your setup/configs so that we can help
Nathan figure out if this is a configuration issue, different bug, or
the same bug?
So far only one reported it as not fixing their issue.
Thanks to everyone who have tested this so far, I'll work on getting it
through
** Changed in: sssd (Ubuntu Precise)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when exiting su session
To manage noti
Tested the package from Timo's PPA. Fixed the bug on my Precise system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when exiting su session
To manage notifica
Confirmed with precise. This bug is the reason for everyday cronjob
messages containing this:
/etc/cron.daily/lighttpd:
su: User not known to the underlying authentication module
su: User not known to the underlying authentication module
run-parts: /etc/cron.daily/lighttpd exited with return code
I have sssd configured to authenticate against AD.
Here I have my user properly authenticating and su works fine.
root@host:~# su - nhuisman
root@host:~# exit
logout
auth.log entries
Nov 5 17:56:25 host sshd[8417]: pam_unix(sshd:session): session opened for
user root by (uid=0)
Nov 5 17:56:2
Nathan,
Could we get your auth.log and any reproducer steps that would help us
track this down?
Thanks,
Adam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when
Tested the new package, but the bug still exists for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when exiting su session
To manage notifications about thi
Uploaded a new package for precise to
https://launchpad.net/~sssd/+archive/updates
please test, it'll get SRU'd next.
** Changed in: sssd (Ubuntu Precise)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: sssd (Ubuntu Precise)
Milestone: None => ubuntu-12.04.2
** Changed in: sssd (Ubuntu Precise)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
sent a subset of that commit upstream to be included in 1.8.x, will add
it for precise one way or another.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when exi
Confirmed that backporting 7016947229 fixed this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM error when exiting su session
To manage notifications about this bug g
Mark, thanks for the suggestion, will look into that. I was under the
impression that pam_sss in /etc/pam.d/common-session was needed for
access control as provided by SSSD, but I was wrong, apparently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Andreas, if it helps in the meanwhile, it can be pretty easily worked
around. The pam_sss module doesn't really serve any purpose on Ubuntu
at the moment. You can comment the pam_sss line out of /etc/pam.d
/common-session and the error should go away.
--
You received this bug notification becau
Agreed, this is indeed somewhat critical in my opinion. It breaks, for
example, the Pacemaker resource agent for PostgreSQL
(ocf:heartbeat:pgsql), which uses "su" to start and stop a PostgreSQL
instance. Some packages' postinst scripts also fail because "su" doesn't
exit correctly, for example Monk
would be nice to backport the commit that fixes this to precise too.
** Also affects: sssd (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Precise)
Status: New => Triaged
** Changed in: sssd (Ubuntu Precise)
Assignee: (unassigned) => Timo Aalt
This bug was fixed in the package sssd - 1.9.0~beta6-0ubuntu1
---
sssd (1.9.0~beta6-0ubuntu1) quantal; urgency=low
* Merge from unreleased debian git. (LP: #1012900)
sssd (1.9.0~beta6-1) UNRELEASED; urgency=low
* New upstream prerelease 1.9.0beta6. Highlights:
- Add native s
This seems to be fixed in upstream 1.9.0~beta6.
** Changed in: sssd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900
Title:
Using SSSD, PAM err
there was a proposed patch from upstream that was thought to fix this,
but after testing it the error is still the same.
A way to reproduce it is to copy the example config from
/usr/share/doc/sssd/examples/ and modify it to enable a 'fake' ldap
domain, start sssd and run 'su ; exit'. I did try to
27 matches
Mail list logo
