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 notificati
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 anymore
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
ssh-rsa-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com
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 t
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 r
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 subsc
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
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=6135