https://bugzilla.mindrot.org/show_bug.cgi?id=3437
--- Comment #1 from Christoph Anton Mitterer <calestyo@scientia.org> ---
Having thought a bit more about this, at least for scp one would
probably need a new output format, so that one can read the settings
for remote source *and* destination connections.
Perhaps one could simply prefix each line with "src:" / "dst:" or
something like that (ideally using a separator char, that won't ever
show up in plain option names.
Similarly,... it might be interesting for consumers of -G output, to
learn about any further hops (ProxyJump and so)... so perhaps the
settings of these could also be printed with another prefix, e.g. a
number n indicating that these are the settings for the nth hop.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
--- Comment #1 from Christoph Anton Mitterer <calestyo@scientia.org> ---
Having thought a bit more about this, at least for scp one would
probably need a new output format, so that one can read the settings
for remote source *and* destination connections.
Perhaps one could simply prefix each line with "src:" / "dst:" or
something like that (ideally using a separator char, that won't ever
show up in plain option names.
Similarly,... it might be interesting for consumers of -G output, to
learn about any further hops (ProxyJump and so)... so perhaps the
settings of these could also be printed with another prefix, e.g. a
number n indicating that these are the settings for the nth hop.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs