Package: python3-keystone
Version: 2:14.2.0-0+deb10u1
Severity: normal
Tags: patch upstream
Hello,
With Keystone configured as a federated-identity Service Provider (with
the IdP accessed over OpenID in our case but it might affect other
protocols as well), certain operations performed as a
Package: check-mk-agent
Having just tried to install check-mk-agent on a new Stretch system, I
found it to be missing. Indeed,
https://packages.debian.org/search?keywords=check-mk-agent
shows that while there are check-mk-agent packages available for wheezy,
jessie (backports only), buster and
For the record, this upstream version already comes bundled with systemd
units - they are in agent.tar.gz/cfg_examples/systemd. All that has to
be done by the Debian package itself is copy them to /lib/systemd/system.
--
MS
Package: sssd-krb5
Version: 1.11.7-3
On a system using configured to use SSSD with LDAP as id_provider and
Krb5 as auth_provider, users cannot log in (via SSH) when the Linux
keyring is to be used as credential cache. The exact errors appearing in
syslog are:
***
pam_unix(sshd:auth):
Hello,
I see something similar on a number of identical amd64 machines with
nscd and nss-ldap, which have been running etch for a couple of days - on
the affected machines, nscd dies with a SIGABORT within seconds from
starting. What is interesting here is that behaviour seems to spread: at
On Thu, 28 Apr 2005, GOTO Masanori wrote:
Before we suspect glibc, it's better to clear what actually causes
your problem. 2.3.2.ds1-20 and -21 do not have any nscd/NSS
modifications. The almost all code have been used over 1.5 years. So
I think it's your local environment/machine trouble
Package: nscd
Version: 2.3.2.ds1-21
Severity: grave
Justification: renders package unusable
My affected box is an AMD Sempron machine with a 2.6 kernel built
for K8 architecture. Having upgraded nscd to 2.3.2.ds1-20 (via
apt-get dist-upgrade) earlier this week I found myself unable
to log in
7 matches
Mail list logo
