Hi! This seems to be similar to #59 / #119 (or even #104), except that it resurfaced in a fully up-to-date "Fedora 44 Workstation" laptop (NetworkManager-ssh-1.4.4-1.fc44), and it happens even with setenforce 0 and /etc/selinux/config set to SELINUX=disabled.
Upon adding a SSH "VPN" (through nm-connection-editor or gnome-control-center) with the default config (simply setting the server's IPv6 in the "Gateway" field, not even touching the Advanced settings, though normally I'd enable "No tunnel" and "SOCKS bind" to "localhost:8000"), upon trying to activate the VPN I get this in journalctl -f:
NetworkManager[1753]: <info> [1778611902.5128] vpn[0x560bb3f99280,6dcee609-dc22-408c-b4c7-d8dcc9e6760b,"YUNOCONNECT"]: starting ssh
NetworkManager[1753]: <info> [1778611902.5133] audit: op="connection-activate" uuid="6dcee609-dc22-408c-b4c7-d8dcc9e6760b" name="YUNOCONNECT" pid=5733 uid=1000 result="success"
NetworkManager[1753]: <warn> [1778611902.6376] vpn[0x560bb3f99280,6dcee609-dc22-408c-b4c7-d8dcc9e6760b,"YUNOCONNECT"]: final secrets request failed to provide sufficient secrets
No matter what I set (or not) in the advanced settings, I get the same error/outcome.
The weirdest thing is, it happens for newly created SSH VPNs (even when selinux is disabled and the computer has rebooted before you try to create them)... but my previously created SSH VPN from last year (that I was using to test #130) does work without problems! And when I use nm-connection-editor to export their configs, and compare them in Meld, they are identical.
Hi! This seems to be similar to #59 / #119 (or even #104), except that it resurfaced in a fully up-to-date "Fedora 44 Workstation" laptop (
NetworkManager-ssh-1.4.4-1.fc44), and it happens even withsetenforce 0and/etc/selinux/configset toSELINUX=disabled.Upon adding a SSH "VPN" (through
nm-connection-editororgnome-control-center) with the default config (simply setting the server's IPv6 in the "Gateway" field, not even touching the Advanced settings, though normally I'd enable "No tunnel" and "SOCKS bind" to "localhost:8000"), upon trying to activate the VPN I get this injournalctl -f:No matter what I set (or not) in the advanced settings, I get the same error/outcome.
The weirdest thing is, it happens for newly created SSH VPNs (even when selinux is disabled and the computer has rebooted before you try to create them)... but my previously created SSH VPN from last year (that I was using to test #130) does work without problems! And when I use nm-connection-editor to export their configs, and compare them in Meld, they are identical.