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

A Incorrect MAC received on packet occur during PuTTY session. #10

Closed
Aimeast opened this issue Dec 20, 2018 · 6 comments
Closed

A Incorrect MAC received on packet occur during PuTTY session. #10

Aimeast opened this issue Dec 20, 2018 · 6 comments
Labels

Comments

@Aimeast
Copy link
Owner

Aimeast commented Dec 20, 2018

It is found a problem when test the #9. PuTTY may throw Incorrect MAC received on packet during shell session.

@Aimeast
Copy link
Owner Author

Aimeast commented Dec 31, 2018

Reproduce

  1. Connect via PuTTY by default
  2. Just run command dir in shell and repeat about 5~15 times
  3. PuTTY may throw the Incorrect MAC ERROR

I dont know why PuTTY may received Incorrect MAC, but ssh.exe looks like OK. Maybe chose a difference encryption algorithm.

@Aimeast
Copy link
Owner Author

Aimeast commented Jan 13, 2019

Because PuTTY needs to send package winadj@putty.projects.tartarus.org, HERE https://tartarus.org/~simon/putty-snapshots/htmldoc/AppendixF.html. Some of synchronization mechanism goes wrong. (send a packet with repeating outbound packet sequence)

@acid2000
Copy link

But a ChannelFailureMessage is sent as the spec says.

I’ve seen this issue with the standard Ubuntu ssh client.

I think it might be related to multiple channels sending data at the same time and the crypto going out of sync

@Aimeast
Copy link
Owner Author

Aimeast commented Jan 14, 2019

Hi @acid2000 , I pushed this commit 92bb558#diff-92634550b79326c13fac2679d286573fR374 .

Could you please test it is fixed or not?

@Aimeast
Copy link
Owner Author

Aimeast commented Jan 18, 2019

Anyone else found this question still exists?

@robeving
Copy link
Contributor

I patched session.cs on my build. Seems to fix the bug / I wasn't able to reproduce the original issue.

@Aimeast Aimeast closed this as completed Jan 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants