[Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su and sudo
My experience with libnss-ldap is that nscd allows sudo but not su. Also the GUI authentication doesn't work. I just got around to testing libnss-ldapd and I can verify that both sudo and su work there. Ubuntu's gui authentication process does not work though. When you try to perform a privileged action like adding a printer it opens the Authentication dialogue and asks for a password. When you enter an ldap password it returns bad password and the entire printer config system freezes. The following errors are from auth.log: May 7 11:53:11 engine cupsd: pam_unix(cups:auth): check pass; user unknown May 7 11:53:11 engine cupsd: pam_unix(cups:auth): authentication failure; logname= uid=0 euid=0 tty=cups ruser= rhost=localhost May 7 11:53:11 engine cupsd: pam_unix(cups:account): could not identify user (from getpwnam(lquigley)) -- NSS using LDAP+SSL breaks setuid applications like su and sudo https://bugs.launchpad.net/bugs/423252 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su and sudo
I'm sorry, my previous comment didn't hold up to scrutiny. A reboot seems to have gotten rid of those errors The GUI authentication dialogue is asking for the root password rather than the password of the logged in user. Does anyone know if this is the intended behavior? -- NSS using LDAP+SSL breaks setuid applications like su and sudo https://bugs.launchpad.net/bugs/423252 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 507616] Re: CustomLog directive in apache2.conf makes it impossible to change default logging without editing the global config.
The problem with editing apache2.conf is that future distro changes get lost. Once you edit a config file the end user is given two options during an upgrade. They can either replace the current file with the packaged maintainer's file or keep the edited file. So either the system loses the local change or else it because distinct to a default ubuntu configuration. The greater problem is depending on which version of apache2 was installed at the point that the change was made, the configuration can look different. If this log line was moved to a file within conf.d then I could set up a divert which over-wrote the config without disrupting the package maintainers future changes. -- CustomLog directive in apache2.conf makes it impossible to change default logging without editing the global config. https://bugs.launchpad.net/bugs/507616 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 507616] [NEW] CustomLog directive in apache2.conf makes it impossible to change default logging without editing the global config.
Public bug reported: Binary package hint: apache2 Ubuntu Karmic apache2 - 2.2.12-1ubuntu2.1 The following line in apache2.conf is a global, un-editable configuration: CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined In hardy logging was configured in the default site configuration. By adding this configuration line it becomes impossible to change or disable the default logging behavior without editing apache2.conf . I install a standard apache configuration file into /etc/apache2/conf.d/ which configures apache to log to syslog. In hardy this config file overrides the global behavior, but this does not seem to be possible in Karmic. Documentation I've read suggests that CustomLog declarations within a virtualhost will override global declarations, but multiple CustomLog declarations are complementary. ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- CustomLog directive in apache2.conf makes it impossible to change default logging without editing the global config. https://bugs.launchpad.net/bugs/507616 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
