debcrafters-packages team mailing list archive

[Seyeong Kim <2111226@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  [Impact]
  Hello
  
  A customer uses hyperv Ubuntu vm and uses hv_sock to connect to it.
  
  With Jammy, it works well with minimum setup. but with Noble, they
  can't.
  
  I've analyzed a bit further and found below.
  
  debian upstream added sshd@.service template back
  https://salsa.debian.org/ssh-team/openssh/-/commit/eb25ab611967996a0d57b4ee565faa7de58b41f6
  
  systemd 256 added ssh-generator
  https://github.com/systemd/systemd/commit/0e3220684c6184a2f70396d991200ae207a25377
  
  before systemd 256, ssh@.service was default.
  
  with Knetic, ssh@.service is removed
  https://launchpadlibrarian.net/619116456/openssh_1%3A9.0p1-1_1%3A9.0p1-1ubuntu1.diff.gz
  
  So,
  
  Questing : systemd 257, sshd@.service exists
  Plucky : systemd 257, sshd@.service exists
  Oracular : systemd 256, sshd@.service exists
  Noble : systemd 255, ssh@.service or sshd@.service doesn't exist.
  ...
  Jammy : systemd 249, ssh@.service exists.
- ... 
+ ...
  
  I guess, K, L, M, N are affected by this issue.
  
  [Test Cases]
  1. deploy hyperv Ubuntu vm
  2. echo 'hv_sock' >> /etc/module
  3. vi /lib/systemd/system/ssh.socket
-     ..
-     [Socket]
-     ...
-     ListenStream=vsock:22
-     ...
-     Accept=yes
-     ...
+     ..
+     [Socket]
+     ...
+     ListenStream=vsock:22   << add this part
+     ...
+     Accept=yes              << change from no to yes
+     ...
  4. systemctl disable ssh.service; systemctl daemon-reload; systemctl stop ssh.service;
  5. systemctl enable ssh.socket; systemctl start ssh.socket;
  
  # in the hyperv host
  1. hvc ssh user@ubuntu24.04
  # hang this point.
  
  [Where problems could occur]
  TBD
  
  [Others]

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2111226

Title:
  ssh@.service is still needed for hv_sock in Noble release

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Jammy:
  Fix Released
Status in openssh source package in Noble:
  In Progress
Status in openssh source package in Oracular:
  Fix Released
Status in openssh source package in Plucky:
  Fix Released
Status in openssh source package in Questing:
  Fix Released

Bug description:
  [Impact]
  Hello

  A customer uses hyperv Ubuntu vm and uses hv_sock to connect to it.

  With Jammy, it works well with minimum setup. but with Noble, they
  can't.

  I've analyzed a bit further and found below.

  debian upstream added sshd@.service template back
  https://salsa.debian.org/ssh-team/openssh/-/commit/eb25ab611967996a0d57b4ee565faa7de58b41f6

  systemd 256 added ssh-generator
  https://github.com/systemd/systemd/commit/0e3220684c6184a2f70396d991200ae207a25377

  before systemd 256, ssh@.service was default.

  with Knetic, ssh@.service is removed
  https://launchpadlibrarian.net/619116456/openssh_1%3A9.0p1-1_1%3A9.0p1-1ubuntu1.diff.gz

  So,

  Questing : systemd 257, sshd@.service exists
  Plucky : systemd 257, sshd@.service exists
  Oracular : systemd 256, sshd@.service exists
  Noble : systemd 255, ssh@.service or sshd@.service doesn't exist.
  ...
  Jammy : systemd 249, ssh@.service exists.
  ...

  I guess, K, L, M, N are affected by this issue.

  [Test Cases]
  1. deploy hyperv Ubuntu vm
  2. echo 'hv_sock' >> /etc/module
  3. vi /lib/systemd/system/ssh.socket
      ..
      [Socket]
      ...
      ListenStream=vsock:22   << add this part
      ...
      Accept=yes              << change from no to yes
      ...
  4. systemctl disable ssh.service; systemctl daemon-reload; systemctl stop ssh.service;
  5. systemctl enable ssh.socket; systemctl start ssh.socket;

  # in the hyperv host
  1. hvc ssh user@ubuntu24.04
  # hang this point.

  [Where problems could occur]
  TBD

  [Others]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2111226/+subscriptions