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

Jump to bottom

SSH/SFTP connect - packet length 1097295214 too large #11668

Closed
cyberduck opened this issue May 12, 2021 · 4 comments
Closed

SSH/SFTP connect - packet length 1097295214 too large #11668

cyberduck opened this issue May 12, 2021 · 4 comments
Assignees
@dkocher
Labels
bug sftp SFTP Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

88ad47c created the issue

A simple SFTP bookmark like all others which have always worked,
fails when connecting to a CentOS 7 system.

-Is there a way to get a debug log from Cyberduck, to attach here also?*
Screen Shot 2021-05-11 at 6.00.15 PM.png

See attached screen shots, and what the verbose connection from my Mac command line looks like, as follows:

macturbo:panzura beattidp$ ssh -v -i ~/.ssh/id_ecdsa topaz 'id'
OpenSSH_8.4p1, OpenSSL 1.1.1j  16 Feb 2021
debug1: Reading configuration data /Users/beattidp/.ssh/config
debug1: Reading configuration data /opt/local/etc/ssh/ssh_config
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to topaz [192.168.0.150] port 22.
debug1: Connection established.
debug1: identity file /Users/beattidp/.ssh/id_ecdsa type 2
debug1: identity file /Users/beattidp/.ssh/id_ecdsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to topaz:22 as 'beattidp'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:s3jqBnrg7UBE8wpLNDE/SxUWvSl7rFLdin7fxuQECzk
debug1: Host 'topaz' is known and matches the ECDSA host key.
debug1: Found key in /Users/beattidp/.ssh/known_hosts:537
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /Users/beattidp/.ssh/id_ecdsa ECDSA SHA256:ggRao6B8Xe8ywp5VgSKiwOFN3WNORKN2uSp30H7EIQU explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/beattidp/.ssh/id_ecdsa ECDSA SHA256:ggRao6B8Xe8ywp5VgSKiwOFN3WNORKN2uSp30H7EIQU explicit
debug1: Server accepts key: /Users/beattidp/.ssh/id_ecdsa ECDSA SHA256:ggRao6B8Xe8ywp5VgSKiwOFN3WNORKN2uSp30H7EIQU explicit
debug1: Authentication succeeded (publickey).
Authenticated to topaz ([192.168.0.150]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Sending command: id
Agent pid 14970
spawn ssh-add /home/beattidp/.ssh/panzura_id_rsa
Enter passphrase for /home/beattidp/.ssh/panzura_id_rsa: 
Identity added: /home/beattidp/.ssh/panzura_id_rsa (/home/beattidp/.ssh/panzura_id_rsa)
2048 SHA256:Te2jmXkmnCn7klyN6d7/ffwjztHbbsNOJNLJ18TphFs /home/beattidp/.ssh/panzura_id_rsa (RSA)
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
uid=1000(beattidp) gid=1001(beattidp) groups=1001(beattidp),10(wheel),1000(staff) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 2316, received 3136 bytes, in 0.3 seconds
Bytes per second: sent 7047.9, received 9543.3
debug1: Exit status 0

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Possibly related to #8554.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Follow the instructions to provide log output.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Possible duplicate for #7965. Typically you will need to move the commands that print the message from .bashrc script to .bash_profile.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See also our documentation.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug sftp SFTP Protocol Implementation worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck