Skip to content
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

Fix for issue where SSH daemon does not answer SSH_MSG_CHANNEL_REQUEST for "window-change" #111

Closed
wants to merge 1 commit into from

Conversation

pheller
Copy link
Contributor

@pheller pheller commented Nov 20, 2012

resize_pty(), and Client.invoke_shell(). Perhaps useless, but more RFC
compliant. Updated methods to include these parameters in server messages.

Adjusted Channel.resize_pty() to neither request nor wait for a response, as
per RFC 4254 6.7 (A response SHOULD NOT be sent to this message.) This is
necessary as certain hosts have been observed to not acknowledge this type of
channel request (Cisco IOS XR), which causes paramiko to end the session.

resize_pty(), and Client.invoke_shell().  Perhaps useless, but more RFC
compliant.  Updated methods to include these parameters in server messages.

Adjusted Channel.resize_pty() to neither request nor wait for a response, as
per RFC 4254 6.7 (A response SHOULD NOT be sent to this message.)  This is
necessary as certain hosts have been observed to not acknowledge this type of
channel request (Cisco IOS XR), which causes paramiko to end the session.
@pheller pheller closed this Jan 17, 2013
@pheller pheller reopened this Jan 17, 2013
@pheller
Copy link
Contributor Author

pheller commented Jan 17, 2013

Closing and recreating to get the Travis CI status back.

@pheller pheller closed this Jan 17, 2013
@bitprophet
Copy link
Member

I assume this 100% duplicates #133, will check there.

@pheller
Copy link
Contributor Author

pheller commented Feb 3, 2013

It does. I closed / opened to force Travis CI to run the build. My Circle CI trial broke the Travis CI integration for this pull request.

--phil

On Feb 3, 2013, at 3:24 PM, Jeff Forcier notifications@github.com wrote:

I assume this 100% duplicates #133, will check there.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants