-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Version 0.8: maintanance #42
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cloudhead also market the specific place with the fix (the rest is chore)
Ok(0) | ||
} else { | ||
Err(io::ErrorKind::Interrupted.into()) | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cloudhead important!
Before, I was unconditionally passing to the inner session write operation. Now, I do that only if the handshake in the current session is complete
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that means you can't write before the handshake anymore? That sounds good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, you also was not being able to write before the handshake before...
fn artifact(&self) -> Option<Self::Artifact> { Some(()) } | ||
fn artifact(&self) -> Option<Self::Artifact> { | ||
match self { | ||
Socks5::Initial(addr, false) if !addr.requires_proxy() => Some(addr.clone()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line is the actual bugfix: we return artifact signifying successful handshake if the proxy is not used and not needed. Thus, we do not run a empty handshake and successfully activate handshake in up-level session.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.