Displaying 20 results from an estimated 2000 matches similar to: "Problem with connecting to host running ssh 2.3.0p1"
2001 Apr 23
2
Bad packet length error
Hello,
I just built openssh-2.5.2p2 on an HP running HP-UX 11.00. Seems now
when I try and connect to other HP's running ssh with version
openssh-2.3.0p1 (using protocol version 2), I'm getting disconnected
because of a "Bad packet length" error:
ssh -v isd1
...
debug1: ssh_dss_verify: signature correct
debug1: Wait SSH2_MSG_NEWKEYS.
debug1: GOT SSH2_MSG_NEWKEYS.
debug1: send
2000 Dec 18
1
Hanging ssh
OK, with openssh-SNAP-20001218 I still have the problem of a hanging ssh
when running (one specific) command on a server. On the server side,
there's a small suid C prog (/usr/dh/mgmt/HupServer) that runs system
"/usr/local/apache/bin/apachectl stop/start". Incidentally, apachectl is a
shell script, hence the need for a suid wrapper for non-root users... On
the client side,
2001 Feb 18
1
OpenSSH 2.3.0p1 protocol 2 problem with AIX
Hi,
Connecting from RHL7 with OpenSSH 2.3.0p1 or 2.5.0p1 to OpenSSH 2.3.0p1 on
AIX 4.3.1. Protocol 2 doesn't work if you specify 'Ciphers
rijndael128-cbc' or Ciphers 'aes128-cbc'.
sshd -d -d -d on the server shows _nothing_ about these connections.
I'm not sure if rijndael has been left out from sshd somehow, but
shouldn't the error message be a little more
2001 Mar 21
1
Disconnecting: Bad packet length 2056273721.
OpenSSH-2.5.2.p1 won't connect to OpenSSH-2.5.1p2 using
version 2 protocol, quitting with the error message:
[dunlap at tesla dunlap]$ ssh -2 kraken
7a 90 3f 39 37 67 0d 9e ac 43 74 c3 83 83 f5 a2
Disconnecting: Bad packet length 2056273721.
tesla is Linux tesla.apl.washington.edu 2.2.16-3 #1 Mon Jun 19
19:11:44 EDT 2000 i686 unknown Intel RHL6.2 with OpenSSH-2.5.2.p1
compiled from sources
2001 Jan 10
1
SSH2/1 Failure when using bash shell, other shells work
Got a strange problem here. We have OpenSSH 2.3.0p1 running on a variety of
machines and on one particular Redhat 6.2 machine(all patches applied) we
run into a situation where it will not allow us to start a shell when using
bash or bash2. csh and others work fine.
One note...if I enable PermitRootLogin, the user root IS allowed to login
with bash. This is very strange. I'm guessing it
2001 May 08
1
sftp problem
I am trying to resolve an issue with SSH2 version 2.5.2p2 on Solaris 2.6.
SSH2, SSH1 and SCP all work fine in and out. The problem is with SFTP. I
can SFTP out, but not in. I can't SFTP into itself. After I issue the
command, I get a password prompt. After I give the password, the connection
closes with an Exit Status 127. There are 3 other system configure the same
and everything is
2001 Mar 23
1
SSH Conections being dropped.
We are having problems with SSH shells disconnecting.
We are replacing a older version of SSH (Non-Comercial Version which some
one installed in error, but it was working fine.) & Had been running
OpenSSH 2.3.0p? which had similar problems, some of the errors I was
seeing went away with OpenSSH 2.5.2.p1.
compiled against openssl-0.9.6, with SUNWspro & GCC281 on Solaris 2.8 &
Solaris
2001 Apr 24
1
HELP! sftp hangs on exit / Bug?
Hi,
The following discussion was posted to comp.security.ssh
however, it seems that my problems may be a bug in
SSH. Could someone please indicate whether there
is a bug fix, or perhaps whether I should go back a
version or so.
In summary:
- Win98 machine (client)
- OpenSSH as packaged with Cygwin tools 1.1.8
(openssh-2.5.2p2-3)
- Connecting to a Sun running Solaris.
ssh: SSH Secure Shell
2000 Jun 12
2
problems with scp
I have an openssh server running on solaris 7 and the client running on
a clean RH linux 6.1 box. I am using the latest release (2.1.1p1 -- i
had the known solaris utmp problem and the read_key problem when using
2.1.0p2 so i upgraded).
scp from the linux machine to solaris machine gives a "lost connection"
message
[root at dog /root]# scp foo.bar solmachine:/tmp/
lost connection
the
2001 Mar 10
2
passphrase for non existent key?
Hi there. I'm being asked for a passphrase for a key file that does not exist.
See debug output below. Both client and server default to SSH2. Creating a DSA key without a password and copying the public
portion to the server's authorized_keys2 allowed me to login w/o a password. I downloaded and installed the latest version of SSH
from OpenBSD CVS, and now its asking me for the
2016 Nov 16
4
long delay when logging in
I have a CentOS 7 system and when I login with putty or ssh there is a
long delay before I get the password prompt. I ran ssh -v and I found
that it gets up to this:
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
and then
2016 Jan 26
2
Questions about inferred state machines for OpenSSH
Dear all,
For my thesis, I've been working on automatic inference of state
machines for SSH servers. I ran into a couple of particularities
regarding OpenSSH's inferred state machine, and was hoping some of you
might be interested. Maybe you can even shed some light on it.
Setup: I'm using LearnLib's (Java) version of the L* learning
algorithm [1] to come up with sequences of
2000 Jun 28
2
SSH-2.2.0 (for Windows) and OpenSSH-2.1.1p1
I just upgraded my Windows SSH client from the 2.1.x version (whatever it
was) to 2.2.0 and am now experiencing difficulties connecting to my
OpenSSH-2.1.1p1 Linux servers.
I'm not as up-to-speed as I should be on the inner workings of the
handshakes that go on, but from the debug logs and from trying different
connection methods, it seems to be isolated to using publickeys. This
2016 Aug 24
3
kex protocol error: type 7 seq xxx error message
Hi,
mancha and me debugged a problem with OpenSSH 7.3p1 that was reported on
the #openssh freenode channel. Symptoms were that this message was
popping on the console during a busy X11 session:
kex protocol error: type 7 seq 1234
I managed to reproduce the problem, it is related to the SSH_EXT_INFO
packet that is send by the server every time it is sending an
SSH_NEWKEYS packet, hence after
2002 Oct 08
2
Memory fault on HP-UX 11.0, 3.4p1
Is this a known issue? (ignore the pervasive MS-outlook capitalization)
Ssh-agent /bin/ksh
Ssh-add /root/.ssh/id_rsa
Blah blah
Ssh -vvv some_server date
...
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: Enabling compression at level 6.
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1:
2000 May 20
5
Kerberos V5 integration
Hi,
This is just a quick note to let people know that I've _almost_ got
Kerberos V5 working based on the patches posted to this list. I'm
currently at the stage where Kerberos principals can be used to verify
logins (ie Kerberos credentials are correctly passed), but I haven't
(yet) got ticket forwarding to work - this is the next step!
I've taken the original patches and updated
2015 Feb 02
4
[Bug 2348] New: allow ssh to connect to a unix domain socket
https://bugzilla.mindrot.org/show_bug.cgi?id=2348
Bug ID: 2348
Summary: allow ssh to connect to a unix domain socket
Product: Portable OpenSSH
Version: -current
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee: unassigned-bugs at
2015 Jul 18
2
How to ssh to a server via an intermediate server with X11 forwarding?
On Sun, Jul 5, 2015 at 3:26 AM, Damien Miller <djm at mindrot.org> wrote:
> On Sat, 4 Jul 2015, Peng Yu wrote:
>
>> I tried the following command.
>>
>> ssh -Y -t intermediate -- ssh -Y dest
>>
>> But it shows the following error message. Does anybody know how to fix
>> the problem? Thanks.
>
> ssh -oProxyCommand="ssh -W %h:%p
2016 Jun 08
5
Problem with Active Directory authentication
Hello --
We are running the 14.04.3 LTS 64-bit release as a virtual machine on a Vmware appliance. The goal of the installation is to create a Samba server that utilizes Active Directory authentication. To that end I utilized the following procedure:
2002 Dec 20
3
Bad packet length problem with "aes128-cbc" and openssh3.1p1
Hi,
I am trying to run openssh 3.1p1. But it is giving "Bad packet length" error
when I run sshd with default config file. On further investigation I found
that the error is coming only for the cipher algorithm "aes128-cbc". Also
the error comes only when I don't specify any protocol file
(/usr/local/etc/ssh_host_[rd]sa_key) or specify only "protocol 2" files.
I