public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] ssh rekeying slow ?
Date: Wed, 25 Jun 2014 12:18:49 +0200	[thread overview]
Message-ID: <53AAA209.1000900@xunil.at> (raw)


When I ssh into a server in my basement, this takes way more time than
usual.

I don't have a clue what might have changed ... aside from usual
updating. I rebuilt and restarted openssh down there without a change.

This is a bit annoying when logging in and using git to pull/push stuff
from/to there.

Does anyone have an idea what I could do to fix that?

Stefan

demo ->

$ ssh -v root@mythtv

OpenSSH_6.6.1, OpenSSL 1.0.1h 5 Jun 2014
debug1: Reading configuration data /home/sgw/.ssh/config
debug1: /home/sgw/.ssh/config line 33: Applying options for mythtv
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to mythtv [2001:15c0:65ff:8742:219:99ff:fee8:2343]
port 22.
debug1: fd 3 clearing O_NONBLOCK
debug1: Connection established.
debug1: identity file /home/sgw/.ssh/id_rsa type 1
debug1: identity file /home/sgw/.ssh/id_rsa-cert type -1
debug1: identity file /home/sgw/.ssh/id_dsa type -1
debug1: identity file /home/sgw/.ssh/id_dsa-cert type -1
debug1: identity file /home/sgw/.ssh/id_ecdsa type -1
debug1: identity file /home/sgw/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/sgw/.ssh/id_ed25519 type -1
debug1: identity file /home/sgw/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1-hpn14v4
debug1: Remote protocol version 2.0, remote software version
OpenSSH_6.6p1-hpn14v4
debug1: match: OpenSSH_6.6p1-hpn14v4 pat OpenSSH_6.5*,OpenSSH_6.6*
compat 0x14000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: AUTH STATE IS 0
debug1: REQUESTED ENC.NAME is 'aes128-ctr'
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: REQUESTED ENC.NAME is 'aes128-ctr'
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA
07:f3:16:2b:e9:64:87:fa:df:14:70:dc:03:60:5a:3c
debug1: Host 'mythtv' is known and matches the ECDSA host key.
debug1: Found key in /home/sgw/.ssh/known_hosts:168
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/sgw/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: Single to Multithread CTR cipher swap - client request
debug1: Authentication succeeded (publickey).
Authenticated to mythtv ([2001:15c0:65ff:8742:219:99ff:fee8:2343]:22).
debug1: HPN to Non-HPN Connection
debug1: Final hpn_buffer_size = 2097152
debug1: HPN Disabled: 0, HPN Buffer Size: 2097152
debug1: channel 0: new [client-session]
debug1: Enabled Dynamic Window Scaling
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: need rekeying
debug1: SSH2_MSG_KEXINIT sent
debug1: rekeying in progress
debug1: rekeying in progress
debug1: rekeying in progress
debug1: rekeying in progress
debug1: enqueue packet: 80
debug1: rekeying in progress
debug1: SSH2_MSG_KEXINIT received
debug1: AUTH STATE IS 1
debug1: REQUESTED ENC.NAME is 'aes128-ctr'
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: REQUESTED ENC.NAME is 'aes128-ctr'
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA
07:f3:16:2b:e9:64:87:fa:df:14:70:dc:03:60:5a:3c
debug1: Host 'mythtv' is known and matches the ECDSA host key.
debug1: Found key in /home/sgw/.ssh/known_hosts:168
debug1: ssh_ecdsa_verify: signature correct
debug1: set_newkeys: rekeying
debug1: spawned a thread
debug1: spawned a thread
debug1: dequeue packet: 80
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: set_newkeys: rekeying
debug1: spawned a thread
debug1: spawned a thread
debug1: SSH2_MSG_NEWKEYS received
debug1: Sending environment.
debug1: Sending env LANG = de_DE.UTF-8



             reply	other threads:[~2014-06-25 10:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 10:18 Stefan G. Weichinger [this message]
2014-06-25 18:30 ` [gentoo-user] Re: ssh rekeying slow ? James
2014-06-25 18:41   ` Stefan G. Weichinger
2014-06-25 19:49     ` Alan McKinnon
2014-06-25 21:10       ` Stefan G. Weichinger
2014-06-25 21:31         ` Alan McKinnon
2014-06-25 21:38           ` Stefan G. Weichinger
2014-06-25 21:31         ` Stefan G. Weichinger
2014-06-25 21:43           ` Stefan G. Weichinger
2014-06-25 22:13         ` Mick
2014-06-25 21:45   ` covici
2014-06-25 22:20     ` Stefan G. Weichinger
2014-06-25 22:34       ` Stefan G. Weichinger
2014-06-25 22:52       ` covici
2014-06-26  4:07 ` [gentoo-user] " Dale
2014-06-26 10:45   ` Stefan G. Weichinger
2014-06-26 10:54     ` Alan McKinnon
2014-06-26 13:12       ` Stefan G. Weichinger
2014-06-26 21:35         ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53AAA209.1000900@xunil.at \
    --to=lists@xunil.at \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox