** Changed in: sudo (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon
** Changed in: sudo (Debian)
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/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon
** Changed in: sudo (Debian)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon sudo
This bug was fixed in the package sssd - 2.3.1-3
---
sssd (2.3.1-3) unstable; urgency=medium
* control: Move libsss-sudo to sssd-common Suggests. (LP: #1249777)
-- Timo Aaltonen Tue, 06 Oct 2020 15:56:19 +0300
** Changed in: sssd (Ubuntu)
Status: Confirmed => Fix
i solved following the last answer in this post:
https://superuser.com/questions/1086152/sudo-sending-annoying-alerts-issue-with-defaults-entries
adding ssh and sudo to the services option in the sssd section of
sssd.conf worked for me:
### sssd.conf
[sssd]
services = nss, sudo, pam, ssh
i'm
Tilman Schmidt, thank you for identifying the two separate issues. Your
assessment seems reasonable.
Let's use this bug to track the original issue.
For the separate matter of local changes to /etc/nsswitch.conf being
clobbered on package upgrade, I've filed bug 1781991 and a corresponding
bug
Confirm, that solution from #19 works on Ubuntu 16.04 only until next
update, after each update I need to change file manually again! Please
provide solution for remove this option permanently!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=879633.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
IMHO we have two separate issues here, both of which need to be
addressed:
First, and most important, installing an update for the sssd package
MUST NOT revert an intentional local configuration change. If you insist
in adding `sss` to the `sudoers` line in nsswitch.conf on initial
installation,
Imho, the correct fix here would be to just not fail on not getting
sudoers rights from the LDAP. (correctly detecting this specific issue
of course)
This leaves sudo through sssd enabled for that "minority" of users (the
minority probably being companies)
Also, when enabling it again, people
Worse, even if I remove the `sss` entry on the `sudoers` line as
suggested, every update of the `sssd` package adds it back again.
My preferred solution by far is solution 3) from comment #2 on
2013-11-12. At the very least, updating a package should not kill a
manual configuration change.
Re
** Changed in: sudo (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon sudo
** Bug watch added: Debian Bug tracker #793660
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793660
** Also affects: sudo (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793660
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
16.04, vanilla install with sssd pointing at LDAP, the issue is still
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages
@athompso, seems to work fine here on 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon sudo
invocation
To
Confirming that this problem still affects 16.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon sudo
invocation
My workaround is to replace
sudoers:files sss
with
sudoers:files
in /etc/nsswitch.conf because I do not use the SSS configuration for sudo, just
for AD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My testing so far hasn't turned up any issues with 1.11.7, I'd be quite
pleased to see it land in -updates if you're happy with that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
enables sudo in sssd.conf
sssd has MRE, so maybe it's time to push 1.11.7 to -updates..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to
So, the ipa-client-install script is fixed in 4.x so that it either
doesn't add sudoers to nsswitch.conf, or does enable sudo in sssd.conf?
I did indeed have problems finding rules using sssd-1.11.5-1ubuntu3
against FreeIPA server 4.1.2, I'm testing now using your
sssd-1.11.7-1~trusty1 packages
you need freeipa-client 4.x for proper sudo integration, vivid has that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon
** Also affects: sudo (Ubuntu)
Importance: Undecided
Status: New
** Changed in: sudo (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
Well, darn, I seem to have screwed up the status for the sudo package,
and now Launchpad won't let me change it back.
** No longer affects: sudo (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the noise.
Working through this, it's probably a config issue. On joining a host
via freeipa-client-install, nsswitch.conf is updated to add sss to
sudoers, however sssd.conf is *not* created with services = sudo, so
every sudo call gets a hard error trying to look up the defaults
As a workaround that doesn't require changing /etc/nsswitch.conf, you
can also explicitely disable sudo support for your sssd domain :
[sssd]
services = nss, pam, sudo
[mydomain/LDAP]
sudo_provider = none
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
lowering importance, you can remove the package if sudo integration
isn't used
** Changed in: sssd (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
I have the same problem with trusty 14.04
apt-cache policy sudo
sudo:
Installed: 1.8.9p5-1ubuntu1
Candidate: 1.8.9p5-1ubuntu1
Version table:
*** 1.8.9p5-1ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
** Attachment
Sudo in 14.04 is based on 1.8.9p5, which already has that patch from
RHBZ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages
And what do you mean sudo didn't change since raring? It's true that
saucy has same 1.8.6p3 as raring, but 14.04 has a newer version..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
Hi Timo,
please notice the timestamp of the comment in which I said that sudo
didn't change. I didn't run Trusty back then. It was just to point out
that the error did not occur in Raring, but sudo hadn't changed, so it
could not have introduced the error.
But I can also confirm that the error
nope, spoke to soon. I just tested a build with the second
debug_return_int(-1) changed to debug_return_int(0) and the error
still occurs.
No idea then, sorry :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
oh right, this was opened last year..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated nsswitch.conf leads to error messages upon sudo
invocation
To manage
** Bug watch added: Red Hat Bugzilla #879633
https://bugzilla.redhat.com/show_bug.cgi?id=879633
** Also affects: sudo (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=879633
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I can confirm this on 14.04 and I also get the message regardless if
it's a local or network user who runs sudo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
libsss-sudo generated
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sssd (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249777
Title:
I know that the sudo package did not change _at all_ since Raring, where
the problem didn't show up. sssd on the other hand changed quite a lot.
It affects both local and LDAP users. I don't have any sudo config in
LDAP, which is probably the problem.
What I believe happens is that either or
The issue filed in RHBZ was affecting local users (as in, present in
/etc/passwd) who invoked sudo rules stored in LDAP. Is that your case?
Anyhow, this smells more like a sudo issue rather than sssd.. (I'm not
dismissing the problem, just saying..)
--
You received this bug notification because
37 matches
Mail list logo
