sshd/Linux problems
Michael P. Rogers
I'm using Redhat 6.2 and sshd 2.1.1p1, or trying to. When I connnect
(using F-Secure SSH client) I get a message in the log that says:
[sshd]: Protocol Error: Packet too long -234245325 (or some other long
negative number).
I just used Redhat's rpms, rather than compile anything myself.
Any idea what's causing this problem? I've inquired in
comp.security.ssh, but nobody there seemed to know :-(
TIA,
Michael
--
Michael P. Rogers
Millikin University
mpro...@mail.millikin.edu
217-424-6327 (W) 217-424-3993 (F)
http://math.millikin.edu/mprogers
Andrew N. McGuire
~~ Date: Sun, 13 Aug 2000 19:31:35 -0500
~~ From: Michael P. Rogers <mpro...@mail.millikin.edu>
~~ Newsgroups: comp.os.linux.security, comp.os.linux.misc
~~ Subject: sshd/Linux problems
~~
~~ Hello,
~~
~~ I'm using Redhat 6.2 and sshd 2.1.1p1, or trying to. When I connnect
~~ (using F-Secure SSH client) I get a message in the log that says:
~~
~~ [sshd]: Protocol Error: Packet too long -234245325 (or some other long
~~ negative number).
Are you using the a ssh 1.x client and a ssh 2.x server?
That would seem to explain the protocol error. I have
used fsecure before, but can't recall if all versions
support both 1.x and 2.x or if you have to configure it.
~~ I just used Redhat's rpms, rather than compile anything myself.
That could be a problem, but I doubt it.
~~ Any idea what's causing this problem? I've inquired in
~~ comp.security.ssh, but nobody there seemed to know :-(
telnet host 22
will tell you what version of the protocol the server is running.
Make sure your client supports that version, that is all I can think
of for now.
anm
--
/*-----------------------------------------------------------------------.
| Andrew N. McGuire |
| anmc...@ce.mediaone.net |
| "Plan to throw one away; you will, anyhow." - Frederick P. Brooks, Jr. |
`-----------------------------------------------------------------------*/
Xiaotian Sun
each other. I think F-Secure is running ssh1 protocol. I'll
suggest you to change to ssh1 server, which is free, while
ssh2 is not. Or change to OpenSSH, which is free too.
If for some reason, you still want to use ssh2, in order to
make the server compatible with ssh1 client, you'll have to
still install ssh1 server, and configure the ssh2 config file.
For details, please refer to the document.
Xiaotian
In comp.os.linux.security Michael P. Rogers <mpro...@mail.millikin.edu> wrote:
> Hello,
> I'm using Redhat 6.2 and sshd 2.1.1p1, or trying to. When I connnect
> (using F-Secure SSH client) I get a message in the log that says:
> [sshd]: Protocol Error: Packet too long -234245325 (or some other long
> negative number).
> I just used Redhat's rpms, rather than compile anything myself.
> Any idea what's causing this problem? I've inquired in
> comp.security.ssh, but nobody there seemed to know :-(
> TIA,
David Steuber
' For details, please refer to the document.
Which, with all due respect to the authors, sucks. I couldn't get SSH
to work at all. I ended up going with OpenSSH which has the benifit
of being free. The docs for OpenSSH are worse. However, I can do SSH
logins and scp, so I've gotten farther with it.
In both cases, I built from source rather than going with RPMs.
I am wondering what will happen when I move my server over to my ISP
and the name and IP address change. I hope to use the same
certificate on the server.
Isn't configuring a Linux system fun when you have no clue? (referring
to me, not you)
--
David Steuber | Hi! My name is David Steuber, and I am
NRA Member | a hoploholic.
http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=hoplite&submit=Look+it+up
The problem with AI is that it has a mind of its own
--- Devon Miller