Package: python3-lib389 Version: 2.3.1+dfsg1-1 Severity: important Tags: patch
Dear maintaner, when following the 389ds documentation [1] to enable TLS for 389ds I noticed that the step dsconf <ldap instance> security rsa set \ --tls-allow-rsa-certificates on \ --nss-token "internal (software)" \ --nss-cert-name Server-Cert failed with "Error: name 'log' is not defined". This is the same bug as [2]. Applying the upstream patch [3] fixes the problem. [1] https://access.redhat.com/documentation/en-us/red_hat_directory_server/12/html/securing_red_hat_directory_server/assembly_enabling-tls-encrypted-connections-to-directory-server_securing-rhds#proc_enabling-tls-encrypted-connections-to-directory-server-using-the-command-line_assembly_enabling-tls-encrypted-connections-to-directory-server [2] https://pagure.io/freeipa/issue/9283 [3] https://github.com/389ds/389-ds-base/commit/12c14ed15dba332378613ac3ad0bb046811c4d75 -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/6 CPU threads; PREEMPT) 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) Versions of packages python3-lib389 depends on: pn libnss3-tools <none> ii openssl 3.0.11-1~deb12u2 ii python3 3.11.2-1+b1 ii python3-argcomplete 2.0.0-1 pn python3-argparse-manpage <none> ii python3-dateutil 2.8.2-2 ii python3-distro 1.8.0-1 pn python3-ldap <none> ii python3-packaging 23.0-1 ii python3-pkg-resources 66.1.1-1 pn python3-pyasn1 <none> pn python3-pyasn1-modules <none> ii python3-pytest 7.2.1-2 python3-lib389 recommends no packages. python3-lib389 suggests no packages.