Fix is waiting in the unapproved queue.
** Tags removed: foundations-todo
** Tags added: dcr-incoming
** Changed in: openssh (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: openssh (Ubuntu Noble)
Importance: Undecided => Medium
--
You received this bug notification bec
** Changed in: openssh (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage
The fix is scheduled to go out in 1:9.6p1-3ubuntu13.13 (unless a
security update has to go out in the mean time). The
1:9.6p1-3ubuntu13.12 update is currently pending, so all in all it's
probably going to be at least another month.
--
You received this bug notification because you are a member of
Can you please provide an update? Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications about this bug go to:
https://b
Can we please have an update? A workaround maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications about this bug go to:
http
The changes in 13.6 and 13.7 were reverted, and this bug is open again.
Removing the block-proposed-noble tag.
** Changed in: openssh (Ubuntu Noble)
Status: Fix Committed => Confirmed
** Tags removed: block-proposed-noble noble verification-done-noble
verification-needed
--
You received
Adding block-proposed-noble to avoid accidental release while the
regression in
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2087551 is
investigated.
** Tags added: block-proposed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
1:9.6p1-3ubuntu13.7 was moved back to noble-proposed due to a possible
regression[1] that is being investigated. Setting the bug tasks back to
fix committed.
1:9.6p1-3ubuntu13.5 was restored in noble-updates.
1. https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2087551
** Changed in: openss
This bug was fixed in the package openssh - 1:9.6p1-3ubuntu13.7
---
openssh (1:9.6p1-3ubuntu13.7) noble; urgency=medium
* d/t/sshd-socket-generator: run test_match_on_port test
The test case was added to verify the fix for LP: 2076023,
but it is not actually executed at the
I had an internal discussion about this SRU and decided that repeating
the verification done for 13.6 on 13.7 is indeed not necessary, given
the nature of the change introduced in 13.7.
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug not
Thanks for your verification, Vasaya.
openssh is a critical package in ubuntu, and this update has already
gone through one iteration. The original update was 1:9.6p1-3ubuntu13.6,
which was tested in comment #14 according to the test plan from the bug
description.
But then 1:9.6p1-3ubuntu13.7 was
Tested the same way as before, still works fine.
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd
Hello Vasya, or anyone else affected,
Accepted openssh into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.6p1-3ubuntu13.7 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
I have verified the fix using openssh-server from noble-proposed.
I setup a container and enabled noble-proposed:
nr@six:~$ lxc launch ubuntu:noble noble
Launching noble
nr@six:~$ lxc exec noble bash
root@noble:~# cat > /etc/apt/sources.list.d/proposed.sources << EOF
> Types: deb
> URIs: http://u
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifica
Thanks for verifying, Vasya!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Thanks, Nick!
I've installed version 1:9.6p1-3ubuntu13.6 and confirm that it fixed the
issue.
Here's how I verified:
1. Install new version
2. Check what's listening on port 22 via ss command:
$ sudo ss -tlnp | grep :22
LISTEN 0 8192 0.0.0.0:22 0.0.0.0:*
users:((
By default, the priority for -propsed is lower than -updates etc. Please
try:
$ apt install openssh-server -t noble-proposed
to specify you want to install from noble-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
How can I enable -proposed repo in 24.04? There is no preset in
/etc/apt/sources.list.d/ubuntu.sources for some reason.
Update: never mind, found the required block in
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Hello Vasya, or anyone else affected,
Accepted openssh into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.6p1-3ubuntu13.6 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
This is waiting on review from the SRU team. Many of the SRU team
members are also busy with opening the archive for 25.04 and other
things this week, but I will ping them.
Once it is accepted into noble-proposed, it will be at least a week
until it moves to noble-updates.
--
You received this b
Any estimate when the fixed version will be available in Ubuntu 24.04
without -proposal repos?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To ma
This bug was fixed in the package openssh - 1:9.7p1-7ubuntu4
---
openssh (1:9.7p1-7ubuntu4) oracular; urgency=medium
* Explicitly listen on IPv4 by default, with socket-activated sshd
(LP: #2080216)
- d/systemd/ssh.socket: explicitly listen on ipv4 by default
- d/t/sshd-
** Changed in: openssh (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications abou
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications abou
** Description changed:
+ [Impact]
+
+ The default listening sockets for sshd are different depending on
+ whether socket activation is used or not, even when /etc/ssh/sshd_config
+ is the default. E.g.:
+
+ # Socket-activated
+
+ root@n2:~# systemctl status ssh.socket
+ ● ssh.socket - OpenBSD
** Changed in: openssh (Ubuntu)
Status: Confirmed => Triaged
** Also affects: openssh (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/openssh/+git/openssh/+merge/474189
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv
Okay, I am not sure why the ipv6 socket is not accepting ipv4, because
AFAICT (and when I test on my machine) the way IPV6_V6ONLY is being set
in the default case, it should allow ipv4.
However, I do think there is a case to be made about the socket unit
being more aligned with the contents of /et
I have the same issue on a clean install of 24.04.1.
From ubuntu-24.04-live-server-amd64.iso I chose "Ubuntu Server
(minimized)" and "Install OpenSSH server".
$ sudo apt update && sudo apt upgrade -y && shutdown -r now
...
$ lsb_release -d
No LSB modules are available
Description:Ubuntu 24.04
Some more details. Here's a part of my sslh config:
listen:
(
{ host: "0.0.0.0"; port: "443"; },
{ host: "::"; port: "443"; }
);
And here's how it's working:
# ss -tlnp | grep sslh
LISTEN 0 50 0.0.0.0:4430.0.0.0:*
users:(("sslh-fork",pid=2557,fd=3),("sslh-fork"
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications about this
I first noticed that I could not ssh to my host, was getting connection
refused error. Then I tried to connect over IPv6 address and it worked.
I checked with `ss -tlnp | grep 22` and found out that sshd was only
listening on [::]:22. Then I tried almost everything to bind it to
0.0.0.0 without any
Is sshd not accessible at all over ipv4? How did you notice that sshd
was not listening on ipv4?
In the default case, we should end up with ssh.socket listening on
[::]:22, but with IPV6_V6ONLY=0 so that sshd is still accessible over
ipv4.
> Setting net.ipv6.bindv6only=0 also helps, but that's no
34 matches
Mail list logo
