Package: libnss3 Version: 2:3.58-1 Followup-For: Bug #972713 I'm seeing the same problem when connecting to a stock buster ejabberd server with a Let's Encrypt certificate and no special TLS configuration. Something definitely changed between 2:3.56-1 and 2:3.58-1 and I'm dubious it's poor TLS configuration (although it's possible it's related to versions of TLS libraries). ejabberd appears to use the buster OpenSSL libssl for its side of the connection.
-- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnss3 depends on: ii libc6 2.31-4 ii libnspr4 2:4.29-1 ii libsqlite3-0 3.33.0-1 libnss3 recommends no packages. libnss3 suggests no packages. -- no debconf information
