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
It is my understanding that the OpenSSH match keyword should now be supported after the closing of issue #717 .
However, I am still experiencing issues with it.
Specifically, I am trying to work with xpra (https://xpra.org/) which uses an ssh channel for providing a persistent remote display server and client for forwarding applications and desktop screens. In turn xpra relies on paramiko for its ssh connection.
With paramiko 2.7.1 even something simple as xpra attach ssh:localhost:101 (which should ssh to localhost and attach there to display :101) fails with the following error:
Removing the match sections in the config file (which incidentally should never do anything with localhost) appears to clear the issue.
Using paramiko 2.6.0 seems to also avoid the issue, but it is unclear to me if that version of paramiko should have support for match at all, plus it has issues for other reasons such as problems with ssh keys being in their own format rather than PEM.
To break things, it is enough for the ssh config file to contain something as simple as
Match host blahblah
at the end.
The text was updated successfully, but these errors were encountered:
It is my understanding that the OpenSSH
match
keyword should now be supported after the closing of issue #717 .However, I am still experiencing issues with it.
Specifically, I am trying to work with
xpra
(https://xpra.org/) which uses an ssh channel for providing a persistent remote display server and client for forwarding applications and desktop screens. In turnxpra
relies onparamiko
for its ssh connection.With paramiko 2.7.1 even something simple as
xpra attach ssh:localhost:101
(which should ssh tolocalhost
and attach there to display:101
) fails with the following error:Removing the
match
sections in theconfig
file (which incidentally should never do anything with localhost) appears to clear the issue.Using paramiko 2.6.0 seems to also avoid the issue, but it is unclear to me if that version of paramiko should have support for
match
at all, plus it has issues for other reasons such as problems with ssh keys being in their own format rather than PEM.To break things, it is enough for the ssh config file to contain something as simple as
at the end.
The text was updated successfully, but these errors were encountered: