On Mon, 11 Sep 2023, Philipp Marek wrote:> I've got a usecase right now where I've got to use a few > intermediate ProxyJump hosts, and it would help debugging > via -v tremendously if the debug lines would have a prefix > of the originating host, so that they can be easily associated. > > The FQDN might be too long, though -- perhaps just the PID > with an additional line associating it with the host would be > a better fit?it's a bit of a hack, but you can get PID in debug messages right now using LogVerbose=*, though you'll probably need to set it in ssh_config if you're using ProxyJump as options from the command-line are mostly not passed to the subordinate ssh processes. -d
>> I've got a usecase right now where I've got to use a few >> intermediate ProxyJump hosts, and it would help debugging >> via -v tremendously if the debug lines would have a prefix >> of the originating host, so that they can be easily associated. >> >> The FQDN might be too long, though -- perhaps just the PID >> with an additional line associating it with the host would be >> a better fit? > > it's a bit of a hack, but you can get PID in debug messages right now > using LogVerbose=*, though you'll probably need to set it in ssh_config > if you're using ProxyJump as options from the command-line are mostly > not passed to the subordinate ssh processes.Thanks for the idea -- but that means having write access to sshd_config and (potentially) disturbing all other users on the machines. Well, how about the general idea of including the PID? If it's at the end like [1234] it's okay as well, highlighting strings in an editor is easy enough.