[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SN7PR14MB73782CD825FF151648AB323596BFA@SN7PR14MB7378.namprd14.prod.outlook.com>
Date: Mon, 29 Dec 2025 13:59:21 +0000
From: Benjamin McMahon <benjamin.mcmahon@...pros.com>
To: "oss-security@...ts.openwall.com" <oss-security@...ts.openwall.com>
Subject: Re: Systemd vsock sshd
To prevent the vsock-based sshd from auto-spawning, see https://www.freedesktop.org/software/systemd/man/devel/systemd-ssh-generator.html
In short: `systemd.ssh_auto=no` is the kernel-command-line setting which persists after reboots.
~Benjamin
________________________________________
From: Jacob Bachmeyer <jcb62281@...il.com>
Sent: Sunday, December 28, 2025 10:11 PM
To: oss-security@...ts.openwall.com <oss-security@...ts.openwall.com>; Greg Dahlman <dahlman@...il.com>
Subject: Re: [oss-security] Systemd vsock sshd
[You don't often get email from jcb62281@...il.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
On 12/27/25 21:46, Greg Dahlman wrote:
> [...]
>
> **Systemd v256 change** - When the *openssh-server* package is
> installed on a VM with vsock support, systemd now automatically
> starts an *sshd* instance that listens on the **af_vsock** socket in
> the **global network namespace** without any manual configuration.
Obvious question: what manual configuration is required to kill that
listener?
-- Jacob
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
