[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1061516: marked as done (Please add a sshd@.service template for socket activation)

Your message dated Wed, 06 Mar 2024 10:05:19 +0000
with message-id <E1rho9H-007tkS-Hc@fasolo.debian.org>
and subject line Bug#1061516: fixed in openssh 1:9.6p1-5
has caused the Debian Bug report #1061516,
regarding Please add a sshd@.service template for socket activation
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 owner@bugs.debian.org
immediately.)


-- 
1061516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061516
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: openssh-server
Version: 1:9.6p1-3
Severity: normal
Control: affects -1 systemd

The next release of systemd will contain support to connect to the 
system with SSH over an AF_VSOCK socket:
https://github.com/systemd/systemd/pull/30777/files

The server side of this uses what Ubuntu currently ships as 
ssh@.service, i.e. a template for socket activation of per-connection 
sshd daemons.

systemd currently expects the template to be named sshd@.service 
(because that is what Fedora uses), but if you prefer to keep the 
ssh@.service name then I suppose that we could patch systemd as well.

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: openssh
Source-Version: 1:9.6p1-5
Done: Colin Watson <cjwatson@debian.org>

We believe that the bug you reported is fixed in the latest version of
openssh, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061516@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <cjwatson@debian.org> (supplier of updated openssh package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 06 Mar 2024 09:45:56 +0000
Source: openssh
Architecture: source
Version: 1:9.6p1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSH Maintainers <debian-ssh@lists.debian.org>
Changed-By: Colin Watson <cjwatson@debian.org>
Closes: 1061516
Changes:
 openssh (1:9.6p1-5) unstable; urgency=medium
 .
   * Restore systemd template unit for per-connection sshd instances,
     although without any corresponding .socket unit for now; this is mainly
     for use with the forthcoming systemd-ssh-generator (closes: #1061516).
     It's now called sshd@.service, since unlike the main service there's no
     need to be concerned about compatibility with the slightly confusing
     "ssh" service name that Debian has traditionally used.
Checksums-Sha1:
 fb67c982eebd06de48e4d695a03ef29c3a87da23 3341 openssh_9.6p1-5.dsc
 97fb1ef7d877a4d79b7b9bcddbbafc0d3f286106 188804 openssh_9.6p1-5.debian.tar.xz
Checksums-Sha256:
 92be51621fa9ed2618a2ee953aa977321642762c6cd49da2e15bb9c7342fa1ed 3341 openssh_9.6p1-5.dsc
 8777b5a1563587755fba0ab12875761e7eb284d9d310933ef74404dce9ef1f37 188804 openssh_9.6p1-5.debian.tar.xz
Files:
 3aff678be62f13f20115f1237eee18e0 3341 net standard openssh_9.6p1-5.dsc
 302f29bf3b4875ac6a13ace7ba969079 188804 net standard openssh_9.6p1-5.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmXoO5QACgkQOTWH2X2G
UAuIkhAAmT2wj17nh7oipnUro+MpgkQV7uW2eBMIzcfPZfLZhIBlmz5wQHnqaYBS
F1ZbChRhPZEoThv4vEUT7/PYbZdLuKVXdVYmyYSeGr3lD9ZsV6SnX8g82EFNbMjI
4BCXohJShbu/4WNHaHnDCPd+JsT5s0/2YsHhkqX/uBF2dHFtYbUwGv0U0H8kc2zR
EUSxbg33L9RrNLjwFAVH+7Eg8r09XyS8yAcV9ph3h02jP7IjksBvcnHCzpt3pDyX
V4omCotEdTt6+qp2jP77DeeS81GnRKHmuWdVza/G6zCCTltb1YawQoKNnU4VjmiP
bLpqdTcrhfBSZawjfrcqe9tGHWyfb1pU+HoOVCJsBL/MfrpLYmFLt0Y3iyNxyOIu
29vPHvmvdpF0A+NdFBuXMp6Usx6n++hkJK4iuWd12lYY69qUZ35YLfGn9XNKxyEn
Ray34jYxU4uahKRnKu/ZRXCduWxg+po4pF2BJ0aiWcMHNt61o0f7izod9+GnjbSf
xMKPEIK3qT3E7j7M0N3BI90Y+hJmbXMprycn47C0qUVj6ta2Bzbk+ziHM9wtIdk4
39iPSpCVQeFWVIZCcW/JwME/cjzHsHKPRVbgTxMNYMEfjz0nmSoygxOxGUWWN9SJ
W663mcgkYN6WpG/1PBpvesTM97qSTq6A57GOPXRFLT3fkUfEsCU=
=AFUQ
-----END PGP SIGNATURE-----

Attachment: pgpr1sgb9QCKb.pgp
Description: PGP signature


--- End Message ---
Reply to: