Prevent usage of SSH persistent connections

[fooker]

Deployment sometimes get stuck on "Pushed system closure" if SSH control master already exists for the connection to make.

This is more like a bug in the nix SSH implementation which is usually mitigated by setting these options in NIX_SSHOPTS.

[frobware]

I too ran into 'Deployment sometimes get stuck on "Pushed system closure"' an awful lot and as a short-term measure simply removed persistent connections from my ssh config.

[dantefromhell]

I'm getting the issues too, but since many of my system use Security Key based pubkey auth the ControlMaster feature is super helpful for not pressing my Yubikey constantly.
Have the ControlMaster forcefully disabled would break my setup.

But I do run into the reported issue too. I have not tested/ tuned this, but from past experiences SSH default config is rather bad at detecting connections that got closed on the server side by a reboot.
Possibly tuning the KeepAlive SSH settings would solve the reported problem without needing to disable the ControlMaster?

[lovesegfault]

Why do you bother setting ControlPath? If ControlMaster is no, ssh won't even look at ControlPath.

[NeverBehave]

Is this related? I thought colmena haven't implement session reuse.

Ah nvm, it is nix ssh implementation details.

#6