You are not logged in.
Hello!
I've done an update after a lengthy absence (5 weeks). I'm observing two effects that may or may not be related. I'll post as two different issues, so that they can be closed individually.
The other issue is bash: systemd_osc_context_cmd_id: unbound variable
The login (text mode, using `agetty`) now additionally displays the message
Try contacting this VM's SSH server via 'ssh vsock%1' from host.which is *not* part of `/etc/issue`. Which piece of software writes this message, and how can I turn it off?
I'm almost certain this is new.
Further info: This system is runnin on a VirtualBox VM.
$ hostnamectl # some lines removed
Icon name: computer-vm
Chassis: vm ?
AF_VSOCK CID: 1
Virtualization: oracle
Operating System: Arch Linux
Kernel: Linux 6.17.7-arch1-1
Architecture: x86-64
Hardware Vendor: innotek GmbH
Hardware Model: VirtualBox
Hardware Version: 1.2
Firmware Version: VirtualBox
Firmware Date: Fri 2006-12-01
Firmware Age: 18y 11month 1w `systemctl status` reports `Running`, everything seems fine.
Last edited by stefan (2025-11-08 15:22:41)
Offline
Offline
Hrmpf. I did not ask for this. I don't think I want this.
Is adding `systemd.ssh_auto=disable` to the kernel command line the best way to disable this?
Offline
It is *a* way to disable it and suggested by systemd.
You could also try to mask the generator
By symlinking /etc/systemd/system-generators/systemd-ssh-generator to /bin/true - but idk whether that works.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
I'm not sure this is solved.
Well, it is not solved. There are so many questions, most importantly: Do I have to deal with another SSH server being magically made available? I don't want this! Am I required to counteract every systemd dev's brainfart with extending the kernel command line? I don't hope so!
On the other hand: Maybe it is solved, as the Arch Linux maintainers cannot be blamed for upstream devs messing up. Hmmm.
I promote this upstream:
https://github.com/systemd/systemd/issues/39640
What do you tink seth? Should I consider this closed as far as the Arch Linux forum goes?
Last edited by stefan (2025-11-08 10:36:07)
Offline
Do I have to deal with another SSH server being magically made available?
Sort of, yes.
openssh had a socket activated daemon for a while, but that was reverted because it's easily exploitable, https://wiki.archlinux.org/title/OpenSS … activation
You probably want to check whether the socket listens on a WAN-facing connection at which point this becomes a serious issue.
Should I consider this closed as far as the Arch Linux forum goes?
You know what's causing this, you know that you don't want it and you know (?) how to avoid it, so there's little left to be done here.
Prospect:
I'd not hold my breath for Mr. 42% less Unix philosophy to change any opinion on this and arch developers will be very reluctant to change away from upstream defaults (by default) - certainly not if you can locally control it.
Offline
Marked as solved in the sense of “nothing we can do *here* about that”...
Offline