Re: [systemd-devel] systemd services via SSH (-H key)

On Sat, 24.10.15 15:57, Reindl Harald (h.rei...@thelounge.net) wrote: > Am 24.10.2015 um 15:04 schrieb Lennart Poettering: > >Well, I am pretty sure using "#" as separator for that is a really > >untypical syntax. I am not sure it's really such a big improvement > >supporting such a syntax over

Re: [systemd-devel] systemd services via SSH (-H key)

24.10.2015 16:57, Reindl Harald пишет: Am 24.10.2015 um 15:04 schrieb Lennart Poettering: Well, I am pretty sure using "#" as separator for that is a really untypical syntax. I am not sure it's really such a big improvement supporting such a syntax over simply asking people to put the right

Re: [systemd-devel] systemd services via SSH (-H key)

Am 24.10.2015 um 15:04 schrieb Lennart Poettering: Well, I am pretty sure using "#" as separator for that is a really untypical syntax. I am not sure it's really such a big improvement supporting such a syntax over simply asking people to put the right statement in ~/.ssh/config... Note thta

Re: [systemd-devel] systemd services via SSH (-H key)

On Sat, 24.10.15 09:20, Stuart Longland (stua...@longlandclan.id.au) wrote: > Makes sense. So that explains why not another character such as /. I > suppose # might work as a delimiter for specifying a port number: > > e.g. > foo#portno > > I seem to recall seeing that in BIND: > >

Re: [systemd-devel] systemd services via SSH (-H key)

well, you can argue with all sorts of workarounds, lacking something like specify a port for a tcp connection is a fractal of bad design Am 24.10.2015 um 16:58 schrieb Andy Pieters: Exactly so for Reindl's use scenario, considering 5 hosts all on the same ip address but with different ports,

Re: [systemd-devel] systemd services via SSH (-H key)

On Fri, 23.10.15 09:07, Stuart Longland (stua...@longlandclan.id.au) wrote: > On 23/10/15 08:59, Reindl Harald wrote: > >> Because the syntax of -H parameter is "[user@]host[:container]" > >> and it does not allow specifying an explicit port number. > > > > [user@]host[:container][:port] > >

Re: [systemd-devel] systemd services via SSH (-H key)

B1;4201;0cOn Fri, 23.10.15 14:24, Mantas Mikulėnas (graw...@gmail.com) wrote: > Yeah, I was referring to UUCP, since it's the same kind of hop-by-hop > source-routing. > > (Admittedly, ":" was used the same way in Berknet...) > > Though, wouldn't containers just run sshd themselves? Or is this

Re: [systemd-devel] systemd services via SSH (-H key)

On Fri, 23.10.15 14:03, Mantas Mikulėnas (graw...@gmail.com) wrote: > On Fri, Oct 23, 2015 at 1:55 PM, Lennart Poettering > wrote: > > > On Fri, 23.10.15 00:59, Reindl Harald (h.rei...@thelounge.net) wrote: > > > > > > > > > > > Am 23.10.2015 um 00:39 schrieb Ivan

Re: [systemd-devel] systemd services via SSH (-H key)

On Fri, 23.10.15 00:59, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 23.10.2015 um 00:39 schrieb Ivan Shapovalov: > >On 2015-10-22 at 23:12 +0200, Reindl Harald wrote: > >>[...] > >>and why not simply "timedatectl -H user@host[:port]" since host:port > >>is > >>a well known protocol

Re: [systemd-devel] systemd services via SSH (-H key)

On Fri, Oct 23, 2015 at 2:11 PM, Lennart Poettering wrote: > On Fri, 23.10.15 14:03, Mantas Mikulėnas (graw...@gmail.com) wrote: > > > On Fri, Oct 23, 2015 at 1:55 PM, Lennart Poettering < > lenn...@poettering.net> > > wrote: > > > > > On Fri, 23.10.15 00:59, Reindl

Re: [systemd-devel] systemd services via SSH (-H key)

On 23/10/15 21:04, Lennart Poettering wrote: >> Can a container name be all-numeric? > We make the same restrictions on container names as on host names. And > that means all-numeric is OK. Ahh, so there goes the idea of just using heuristics (i.e. am I looking at a string of digits only) to

Re: [systemd-devel] systemd services via SSH (-H key)

23.10.2015 0:50, Jan Alexander Steffens пишет: > On Thu, Oct 22, 2015 at 11:07 PM, Mikhail Kasimov > wrote: >> Hello! >> >> 1. systemd services have a special key (-H) to connect to remote host >> via ssh. E.g. 'timedatectl -H user@host'. By default port 22 is used. >>

Re: [systemd-devel] systemd services via SSH (-H key)

Am 22.10.2015 um 23:07 schrieb Mikhail Kasimov: 1. systemd services have a special key (-H) to connect to remote host via ssh. E.g. 'timedatectl -H user@host'. By default port 22 is used. But in very often cases admins change the default ssh-port in sshd-daemon settings (e.g. 41122). It's

Re: [systemd-devel] systemd services via SSH (-H key)

On 2015-10-22 at 23:12 +0200, Reindl Harald wrote: > [...] > and why not simply "timedatectl -H user@host[:port]" since host:port > is > a well known protocol agnostic way to specify a non-default port? Because the syntax of -H parameter is "[user@]host[:container]" and it does not allow

[systemd-devel] systemd services via SSH (-H key)

Hello! 1. systemd services have a special key (-H) to connect to remote host via ssh. E.g. 'timedatectl -H user@host'. By default port 22 is used. But in very often cases admins change the default ssh-port in sshd-daemon settings (e.g. 41122). It's useful to avoid connections from ssh-bruteforce

Re: [systemd-devel] systemd services via SSH (-H key)

On 23/10/15 08:59, Reindl Harald wrote: >> Because the syntax of -H parameter is "[user@]host[:container]" >> and it does not allow specifying an explicit port number. > > [user@]host[:container][:port] > [user@]host[:port][:container] Can a container name be all-numeric? Who made the decision