Your message dated Fri, 29 Apr 2022 19:16:46 +0200
with message-id <bb526750-c59f-84a3-fa28-67bdccd07...@debian.org>
and subject line Re: systemd-creds: Support for encrypted credentials not
available.
has caused the Debian Bug report #1010363,
regarding systemd-creds: Support for encrypted credentials not available.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1010363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 250.4-1~bpo11+1
Severity: wishlist
X-Debbugs-Cc: m...@neils.tech
Dear Maintainer,
systemd v250 added support for encrypted credentials via the
systemd-creds tool. I installed the latest version of systemd from
bullseye-backports. When I run 'systemd-creds' I get the following
error: "Support for encrypted credentials not available."
The cause appears to be that systemd is built without OpenSSL, per this
upstream issue: https://github.com/systemd/systemd/issues/22114
In the changelog for the Debian systemd package there is this note:
-- Michael Biebl <bi...@debian.org> Fri, 24 Dec 2021 13:02:05 +0100
systemd (250~rc3-1) experimental; urgency=medium
...
* Explicitly disable OpenSSL support.
We don't want to pick up an OpenSSL dependency in a tainted build
environment and pull a second crypto stack into systemd's dependencies.
...
Is there any possibility that OpenSSL support could be added so we have
access to this feature?
Thank you,
Neils Christoffersen
-- Package-specific info:
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-13-amd64 (SMP w/4 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 systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-10
ii libapparmor1 2.13.6-10
ii libaudit1 1:3.0-2
ii libblkid1 2.36.1-8+deb11u1
ii libc6 2.31-13+deb11u3
ii libcap2 1:2.44-1
ii libcrypt1 1:4.4.18-4
ii libcryptsetup12 2:2.3.7-1+deb11u1
ii libfdisk1 2.36.1-8+deb11u1
ii libgcrypt20 1.8.7-6
ii libgnutls30 3.7.1-5
ii libgpg-error0 1.38-2
ii libip4tc2 1.8.7-1
ii libkmod2 28-1
ii liblz4-1 1.9.3-2
ii liblzma5 5.2.5-2.1~deb11u1
ii libmount1 2.36.1-8+deb11u1
ii libpam0g 1.4.0-9+deb11u1
ii libseccomp2 2.5.1-1+deb11u1
ii libselinux1 3.1-3
ii libsystemd0 250.4-1~bpo11+1
ii libzstd1 1.4.8+dfsg-2.1
ii mount 2.36.1-8+deb11u1
ii util-linux 2.36.1-8+deb11u1
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.12.20-2
ii systemd-timesyncd [time-daemon] 250.4-1~bpo11+1
Versions of packages systemd suggests:
ii libfido2-1 1.6.0-2
pn libtss2-esys-3.0.2-0 <none>
pn libtss2-mu0 <none>
pn libtss2-rc0 <none>
pn policykit-1 <none>
pn systemd-container <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.12.20-2
pn dracut <none>
ii initramfs-tools 0.140
ii libnss-systemd 250.4-1~bpo11+1
ii libpam-systemd 250.4-1~bpo11+1
ii udev 247.3-7
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 29 Apr 2022 10:50:53 -0500 Neils Christoffersen <m...@neils.tech>
wrote:
Package: systemd
Version: 250.4-1~bpo11+1
Severity: wishlist
X-Debbugs-Cc: m...@neils.tech
Dear Maintainer,
systemd v250 added support for encrypted credentials via the
systemd-creds tool. I installed the latest version of systemd from
bullseye-backports. When I run 'systemd-creds' I get the following
error: "Support for encrypted credentials not available."
The cause appears to be that systemd is built without OpenSSL, per this
upstream issue: https://github.com/systemd/systemd/issues/22114
In the changelog for the Debian systemd package there is this note:
-- Michael Biebl <bi...@debian.org> Fri, 24 Dec 2021 13:02:05 +0100
systemd (250~rc3-1) experimental; urgency=medium
...
* Explicitly disable OpenSSL support.
We don't want to pick up an OpenSSL dependency in a tainted build
environment and pull a second crypto stack into systemd's dependencies.
...
Is there any possibility that OpenSSL support could be added so we have
access to this feature?
Once systemd has fully switched to OpenSSL, we will make the switch as well.
As said, I don't want to link agains two crypto stacks.
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
