boring fails ad parsing ssh config file /etc/ssh/ssh_config

[esantoro]

As per subject.

I'm running boring 0.11.8 on Fedora 42 and it silently fails when /etc/ssh/ssh_config contains the following line:

Include /etc/ssh/ssh_config.d/*.conf

Output:

esantoro@x13:/tmp$ ./boring open dev
[00:57:58.045] DEBUG Sending: {"kind":1,"tunnel":{"name":"dev","local":"8006","remote":"192.168.52.73:8006","host":"10.250.0.12","user":"root","identity":"","port":22,"mode":0,"status":0,"last_conn":"0001-01-01T00:00:00Z"}}
[00:57:58.047] DEBUG Received: {"success":false,"error":"could not parse SSH config: (55, 9): Error parsing Include directive: (3, 7): ssh_config: Match directive parsing is unsupported","tunnels":null}

[00:57:58.047] ERROR Could not open tunnel 'dev': could not parse SSH config: (55, 9): Error parsing Include directive: (3, 7): ssh_config: Match directive parsing is unsupported

My understanding is that this makes boring effectively broken on system running modern ssh client.

Also:

• it would have really helped if the behaviour of boring logging at debug level when the DEBUG environment variable is set was documented. I had to go read the source code to find that.
• the location of the logfile (/tmp/boringd.log) should be documented and configurable. on a multi-user system that static location might clash with other instances
• the location of the unix socket (/tmp/boringd.sock) should be documented and configurable. on multi-user system this might be a security issue.

For the log and socket a [[general]] section in the config file would do.

Extra:

• muscle memory always makes me type boring ls, could boring list be also be shortened to that?

Thank you in advance, I'm an (otherwise) very happy boring user!

[alebeck]

Hi Emanuele, thanks a lot for using boring and for your inputs, they're greatly appreciated!

The log message indicates that Match parsing is unsupported, this should have been fixed in v0.11.6. Can you confirm that you're running v0.11.8, and also how you upgrade boring? If it's not via homebrew/Linuxbrew, you might have to manually kill the daemon (e.g., killall boring) so that the new one gets launched with the next CLI interaction. This will be automated in an upcoming release.

I will better document the $DEBUG variable and log/socket file locations, this makes sense. Did you know you can overwrite the latter via $BORING_LOG_FILE and $BORING_SOCK, e.g. in your ~/.bashrc, followed by killing the daemon? I should also document that :)

Lastly, I can add the boring ls shortcut, I think that makes sense, but did you know boring l already works?

It might take a little while until I get to these changes.

Cheers