You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to specify a host like so .*(one|two)\.foo\.com yet this isn't being matched, is only a small subset of regex supported? Or am I doing it wrong?
I'm finding validating config pretty tricky once you've loads of definitions, is there an easier way other than running ssh -v after building ssh_config? It'd be nice if there was some command you could pass a hostname and it'd spit out the config for.
I'm only using this regex as assh doesn't seem to support multiple host matches without a template - unlike normal ssh. e.g. I can't specify "*.one.foo.com" "*.two.foo.com":
The text was updated successfully, but these errors were encountered:
The code uses path globbing - a minimal regex. That's a better match for the very limited globbing implemented in the config file parser in the typical ssh library that's going to read the generated config.
Use
Hosts:
"*one.foo.com *two.foo.com":
yoursshoption: x
I think the issue here is that the README mentions regex a lot of times, which leads people to think they can do complex stuff like "(host(A|B|C)\d+" and so on. It might be useful to add a section to the page that just says it supports Go's path.Match and linked to https://golang.org/pkg/path/#Match
I'm trying to specify a host like so
.*(one|two)\.foo\.com
yet this isn't being matched, is only a small subset of regex supported? Or am I doing it wrong?I'm finding validating config pretty tricky once you've loads of definitions, is there an easier way other than running
ssh -v
after building ssh_config? It'd be nice if there was some command you could pass a hostname and it'd spit out the config for.I'm only using this regex as assh doesn't seem to support multiple host matches without a template - unlike normal ssh. e.g. I can't specify
"*.one.foo.com" "*.two.foo.com":
The text was updated successfully, but these errors were encountered: