ssh -c 3des-cbc host
seems to work around this problem for me for now. +1 to fixing this
ASAP?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore:
Alternatively, I moved 3des-cbc to the front of the Ciphers list in
$HOME/.ssh/config
Will this bite me someday?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
I'm in the same situation, and shortening the cipher list didn't help.
I've tried via terminal with ‘ssh -c aes256-ctr host’ and by editing
/etc/ssh/ssh_config, and removing some ciphers off the cipher list. Same
result. This bug is now almost a year old. Being critical, I get the
feeling it's not
Workaroud found here solved my problem
Shortening the cipher list (‘ssh -c aes256-ctr’)
http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh-
client-connection-reset-by-peer/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hi when I try to 'git clone' some repository.
I encounter the same problem.
-
git clone g...@bitbucket.org:someone/somerepository.git
Cloning into somerepository...
Read from socket failed: Connection reset by peer
fatal: The remote end hung up unexpectedly
This is the header of my private key:
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,
After AES-128-CBC, theres a large hex number. First what is that
number for? Do you require it too?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I'm trying to use sourceforge.net ssh server, but my great problem is
GIT, I can't pull or push code. I don't know how to collect debug
information of git trying to use ssh to connect to git.gnome.org. Any
hint?
--
You received this bug notification because you are a member of Ubuntu
Server
esodan, clint, if it is the same problem, then no need to research it from the
beginning.
Check out my post at
http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh-client-connection-reset-by-peer/
, it tries to shed light on what's happening.
--
You received this bug
Is it possible that the new OpenSSL dropped support for your key
encryption?
Can you paste just the first 3 lines of your private key file, with the
BEGIN, Proc-Type and DEK-Info lines?
(Warning, I do not know if this will leak sensitive info, if you are
unsure, do not paste it).
Also can you
I have the same problem with sourceforge.net service. My machine have a
dual boot from Federa 15 and Ubutu. On Fedora I can use ssh with no
problems but on Ubuntu 11.10 I can't use ssh. This is my debug from ssh
-vvv:
ssh -vvv -t eso...@shell.sourceforge.net
OpenSSH_5.8p1 Debian-7ubuntu1, OpenSSL
Hi,
Im experiencing the same issue described here but whats more weird is that
switching ISPs seems to fix my problem when i ssh my servers, i mean, i have
two internet service providers, with service provider A, ssh doesnt work and i
get the Read from socket failed: Connection reset by peer
i must confirm that is not a IPS restriction or something, because i can
ssh using both ISPs using windows or putty on linux or ssh clients on
iPhone.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Hello
The security man answered :
This is the IDS embeded in a fire check point
So, no cisco. But what would be different if it were a CISCO, JUNIPER,
or ACME ? The fact that a third party is analysing and wrongly -- or
perhaps too much strictly, (or even rightly)-- identifying a packet from
a
But what would be different if it were a CISCO, JUNIPER, or ACME?
The idea is to identify common conditions and reproducing the behavior you
described, as any other bug,
No offense, but your analysis alone is not enough to declare the problem solved.
--
You received this bug notification
In my case it was due to an Intrusion Detection System
I have exactly the same problem. upgrade to 11.04 then ssh to the university I
work won't work any more. both client and server say connection reset by
peer, limiting the cipher length have it work. Details ares here :
Schplurtz: can you share what type of IDS it was? From what I hear, it
sounds like Cisco equipment.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login
My temporal solution:
wget
http://mirror.pnl.gov/ubuntu//pool/main/o/openssh/openssh-client_5.5p1-4ubuntu5_i386.deb
sudo dpkg -i openssh-client_5.5p1-4ubuntu5_i386.deb
Before:
$ ssh -p 2121 in...@200.57.xx.xx
Read from socket failed: Connection reset by peer
After:
$ ssh -p 2121
i have the same problem in my ubuntu (upgraded 10.10 to 11.04).
when i connect with that = ssh A.B.X.X no problem.
but when i try connect to = ssh A.(B+1).X.X , i gets error that Read from
socket failed: Connection reset by peer
then i install putty (apt-get install putty) when i use putty for
Serge: I am really not sure this is related to ecdsa bug. Last time I
checked (about a week ago) the bug still existed even in upstream. See
the connection reset by peer discussions in mailing list:
http://lists.mindrot.org/pipermail/openssh-unix-
dev/2011-February/thread.html
In comment #14 I
Also, I'll re-post the available workarounds as I collected from other
reports of this bug:
1. shortening the list of ciphers by -c aes128-ctr to command line
2. adding to ~/.ssh/config: HostKeyAlgorithms
I agree that that patch can't be relevant. Ralf has
HostbasedAuthentication turned off.
** Also affects: openssh (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613505
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
On the upstream thread, I wondered if the MTU might be relevant. That
would certainly be one explanation for a bug that's apparently sensitive
to packet length.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
** Changed in: openssh (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore: Read from socket failed: Connection
* Colin Watson cjwat...@canonical.com:
On the upstream thread, I wondered if the MTU might be relevant. That
would certainly be one explanation for a bug that's apparently sensitive
to packet length.
I'm having this problem in the local LAN and via DSL (from home)
--
Ralf Hildebrandt
I'm afraid that doesn't answer the question ...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore: Read from socket failed: Connection reset by
Marking as confirmed based on the linked debian bug.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
** Changed in: openssh (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Upstream bug posts the following as a solution:
http://hg.mindrot.org/openssh/rev/138961506b91
Note that it implies that removing your ecdsa keys would allow ssh to
succeed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in
Seems to be the same case as
- Debian sid: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613505
- Arch Linux https://bugs.archlinux.org/task/22897?project=1
I'll try to report it to upstream
** Bug watch added: Debian Bug tracker #613505
I suspect (but not sure) it's related to
https://bugzilla.mindrot.org/show_bug.cgi?id=1858
** Bug watch added: OpenSSH Portable Bugzilla #1858
https://bugzilla.mindrot.org/show_bug.cgi?id=1858
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I was most probably mistaken in the above assumption. sorry.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore: Read from socket failed: Connection
downgrading openssh-client from 1:5.8p1-1ubuntu1 to 1:5.5p1-4ubuntu5
makes the problem go away.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore:
Repeated login attempts to the same machine yield different results:
$ ssh -vv r...@albatross.python.org
OpenSSH_5.8p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1:
FWIW the OpenSSH configure script indicates that ECC only needs OpenSSL
0.9.8g.
I think this GDB session is probably a red herring due to the way sshd
re-execs itself.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
* Colin Watson cjwat...@canonical.com:
FWIW the OpenSSH configure script indicates that ECC only needs OpenSSL
0.9.8g.
I think this GDB session is probably a red herring due to the way sshd
re-execs itself.
Yup.
So what is the problem here. I cannot see any obvious error.
--
Ralf
Sooo, I found this. All the failing systems have
ii libssl1.0.0 1.0.0c-2
SSL shared libraries
installed (I compiled Postfix against openssl-1.0.0, that's why it's
installed), yet their sshd is not linked against libssl1.0.0:
mail:~# ldd /usr/sbin/sshd
But I found that it also fails against a host withOUT openssl-1.0.0:
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2:
So I ran sshd on the target machine in a debugger:
# gdb /usr/sbin/sshd
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore: Read from socket failed: Connection reset by
peer
--
Ubuntu-server-bugs mailing list
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore: Read from socket failed:
$ ssh -vvv root@mail
OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010
debug1: Reading configuration data /home/hildeb/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to mail
mail:~# /usr/sbin/sshd -p2 -ddd
debug2: load_server_config: filename /etc/ssh/sshd_config
debug2: load_server_config: done config len = 639
debug2: parse_server_config: config /etc/ssh/sshd_config len 639
debug3: /etc/ssh/sshd_config:5 setting Port 22
debug3: /etc/ssh/sshd_config:9 setting
$ ssh -vvv root@netsight
OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010
debug1: Reading configuration data /home/hildeb/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to netsight
** Changed in: openssh (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore: Read from socket failed:
43 matches
Mail list logo
