Since this bug should be solved by building the kernel with the
following flags:
CONFIG_XFRM_ESPINTCP=y
CONFIG_INET_ESPINTCP=y
is it more appropriate to refer to a kernel-related package?
Package: libreswan
Version: 4.10-2+deb12u1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Trying to use TCP encapsulation (enable-tcp=yes) between two Debian 12 hosts,
in order to work around the connection freezing after a while when using
defaults.
On the client (initiat
Package: 389-ds-base
Version: 1.4.4.11-2
Severity: important
Tags: upstream
Dear Maintainer,
* What led up to the situation?
389-ds is regularly triggering compaction (notably during
checkpointing), which, with the version currently provided,
systematically leads to a crash.
* What exactl
> > Okay, so it got added to sssd due to
> >
> > https://github.com/SSSD/sssd/issues/5893
> >
> > so I wonder if ipa should stop doing the same, and remove the line
> > from
> > krb5.conf on upgrade.
>
> Seems this is filed upstream already at
>
> https://pagure.io/freeipa/issue/9267
>
> but
Package: freeipa-client
Version: 4.9.11-1
Severity: normal
Dear Maintainer,
on a host enrolled as an IPA client, Kerberos is not usable in Java.
The error message is:
KrbException: krb5.conf loading failed
(please find simple steps to reproduce below)
After debugging step by step, I found o
Package: freeipa-client
Version: 4.9.8-1+b3
Severity: normal
Dear Maintainer,
After installing freeipa-client, sssd is configured to activate certain
services in /etc/sssd/sssd.conf:
...
[sssd]
services = nss, pam, ssh, sudo
...
but the various sssd-*.socket socket-activated systemd services ar
6 matches
Mail list logo
