Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Username

Subject

Message body

Font colour:

Font size:

[quote="lauter5"]Hello

[quote]Incorrect MAC received on packet[/quote]
I got this error on login with RSA key to a server. Version is 6.3.3. 
PuTTY 0.81 does the same and does not work.
PuTTY 0.76 works.
FilleZilla newest works.
Bitvise newest works.

ERROR on Server:
[code]
Apr 18 09:25:44 xxxx sshd[3079764]: Corrupted MAC on input. [preauth]
Apr 18 09:25:44 xxxx sshd[3079764]: ssh_dispatch_run_fatal: Connection from xxx.xxx.xxx.xxx port 56901: message authentication code incorrect [preauth]
Apr 18 09:28:03 xxxxx sshd[3080299]: Corrupted MAC on input. [preauth]
Apr 18 09:28:03 xxxxx sshd[3080299]: ssh_dispatch_run_fatal: Connection from xxx.xxx.xxx.xxx port 56937: message authentication code incorrect [preauth]
[/code]
ERROR on WINSCP:
[code]@sessionlog@
. 2024-04-18 11:10:53.299 Enumerating network events for socket 2392
. 2024-04-18 11:10:53.299 Enumerated 1 network events making 1 cumulative events for socket 2392
. 2024-04-18 11:10:53.299 Handling network read event on socket 2392 with error 0
. 2024-04-18 11:10:53.299 Waiting for the server to continue with the initialization
. 2024-04-18 11:10:53.299 Looking for incoming data
. 2024-04-18 11:10:53.299 Looking for network events
. 2024-04-18 11:10:53.347 Server also has ecdsa-sha2-nistp256 host key, but we don't know it
. 2024-04-18 11:10:53.347 Host key fingerprint is:
. 2024-04-18 11:10:53.347 ssh-ed25519 255 SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxx
. 2024-04-18 11:10:53.349 Verifying host key xxxxxxxxxxxxxxxxxxxxxxxxxxx with fingerprints xxxxxxxxxxxxxxxxxxxxxxxxxxxx, ssh-ed25519 255 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
. 2024-04-18 11:10:53.360 Host key matches cached key
. 2024-04-18 11:10:53.361 Initialised AES-256 SDCTR (AES-NI accelerated) [aes256-ctr] outbound encryption
. 2024-04-18 11:10:53.361 Initialised HMAC-SHA-256 outbound MAC algorithm
. 2024-04-18 11:10:53.361 Initialised AES-256 SDCTR (AES-NI accelerated) [aes256-ctr] inbound encryption
. 2024-04-18 11:10:53.361 Initialised HMAC-SHA-256 inbound MAC algorithm
. 2024-04-18 11:10:53.361 Incorrect MAC received on packet
. 2024-04-18 11:10:53.361 Attempt to close connection due to fatal exception:
* 2024-04-18 11:10:53.361 Incorrect MAC received on packet
. 2024-04-18 11:10:53.361 Closing connection.
. 2024-04-18 11:10:53.361 Selecting events 0 for socket 2392
* 2024-04-18 11:10:53.383 (EFatal) Incorrect MAC received on packet
* 2024-04-18 11:10:53.383 Anmeldung fehlgeschlagen.
[/code]
TNX[/quote]

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

Filename

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

File Comment

Options

Private file (available to author and site moderators only)

Topic review

martin

Re: Incorrect MAC received on packet

2024-04-22

Please post complete logs from WinSCP, PuTTY and FileZilla.

Though, if the latest PuTTY does not work, please consider reporting to the problem to PuTTY team instead: https://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html

lauter5

Incorrect MAC received on packet

2024-04-18 10:21

Hello

Incorrect MAC received on packet

I got this error on login with RSA key to a server. Version is 6.3.3.
PuTTY 0.81 does the same and does not work.
PuTTY 0.76 works.
FilleZilla newest works.
Bitvise newest works.

ERROR on Server:

Apr 18 09:25:44 xxxx sshd[3079764]: Corrupted MAC on input. [preauth]

Apr 18 09:25:44 xxxx sshd[3079764]: ssh_dispatch_run_fatal: Connection from xxx.xxx.xxx.xxx port 56901: message authentication code incorrect [preauth]

Apr 18 09:28:03 xxxxx sshd[3080299]: Corrupted MAC on input. [preauth]

Apr 18 09:28:03 xxxxx sshd[3080299]: ssh_dispatch_run_fatal: Connection from xxx.xxx.xxx.xxx port 56937: message authentication code incorrect [preauth]

ERROR on WINSCP:

. 2024-04-18 11:10:53.299 Enumerating network events for socket 2392
. 2024-04-18 11:10:53.299 Enumerated 1 network events making 1 cumulative events for socket 2392
. 2024-04-18 11:10:53.299 Handling network read event on socket 2392 with error 0
. 2024-04-18 11:10:53.299 Waiting for the server to continue with the initialization
. 2024-04-18 11:10:53.299 Looking for incoming data
. 2024-04-18 11:10:53.299 Looking for network events
. 2024-04-18 11:10:53.347 Server also has ecdsa-sha2-nistp256 host key, but we don't know it
. 2024-04-18 11:10:53.347 Host key fingerprint is:
. 2024-04-18 11:10:53.347 ssh-ed25519 255 SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxx
. 2024-04-18 11:10:53.349 Verifying host key xxxxxxxxxxxxxxxxxxxxxxxxxxx with fingerprints xxxxxxxxxxxxxxxxxxxxxxxxxxxx, ssh-ed25519 255 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
. 2024-04-18 11:10:53.360 Host key matches cached key
. 2024-04-18 11:10:53.361 Initialised AES-256 SDCTR (AES-NI accelerated) [aes256-ctr] outbound encryption
. 2024-04-18 11:10:53.361 Initialised HMAC-SHA-256 outbound MAC algorithm
. 2024-04-18 11:10:53.361 Initialised AES-256 SDCTR (AES-NI accelerated) [aes256-ctr] inbound encryption
. 2024-04-18 11:10:53.361 Initialised HMAC-SHA-256 inbound MAC algorithm
. 2024-04-18 11:10:53.361 Incorrect MAC received on packet
. 2024-04-18 11:10:53.361 Attempt to close connection due to fatal exception:
* 2024-04-18 11:10:53.361 Incorrect MAC received on packet
. 2024-04-18 11:10:53.361 Closing connection.
. 2024-04-18 11:10:53.361 Selecting events 0 for socket 2392
* 2024-04-18 11:10:53.383 (EFatal) Incorrect MAC received on packet
* 2024-04-18 11:10:53.383 Anmeldung fehlgeschlagen.

TNX

Post a reply

Topic review

Re: Incorrect MAC received on packet

Incorrect MAC received on packet

Documentation

Support

Associations

Follow Us