-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ChannelForwardedTCPIP.getPortForwarding(Session) DO NOT CHECK a Session instance. #52
Comments
Hi @parkjunhong, |
norrisjeremy
referenced
this issue
in norrisjeremy/jsch
Sep 2, 2021
norrisjeremy
referenced
this issue
in norrisjeremy/jsch
Sep 2, 2021
Hi @parkjunhong, I have included your suggest fix as part of PR #64 (911358b) that I have opened. Thanks, |
norrisjeremy
referenced
this issue
in norrisjeremy/jsch
Sep 2, 2021
norrisjeremy
referenced
this issue
in norrisjeremy/jsch
Sep 2, 2021
Hi @parkjunhong, Your suggested fix was included in the 0.1.66 release. Thanks, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
HI, I'm Park, Jun Hong in Korea.
I have been used a original Jsch and developed a program that maintains a ssh tunneling.
I found a below bug and fixed it for my application.
So, I report this bug and hope to fix this bug for here.
Found Bugs
Recently I've finished a program that provides a remote port forwarding. This program provides 3 functions.
I found a bug that Remote Port Forwardings are mixed, although it's remote server is different from each other.
A method that provides Local Port Forwarding checks a Session instance.
String[] bar=new String[foo.size()];
for(int i=0; i<foo.size(); i++){
bar[i]=(String)(foo.elementAt(i));
}
return bar;
}
But a method that provides Remote Port Forwardings DO NOT CHECK a Session instance.
To fix this bug, add codes to check whether config.session is equals to the parameter 'session'.
The text was updated successfully, but these errors were encountered: