Displaying 20 results from an estimated 8000 matches similar to: "Openssh-2.3.0p1 protocol 2 problem"
2000 Nov 08
1
openssh-2.3.0p1-1 with RedHat 6.2 - Bad packet length
I haven't been able to get scp to work with RedHat 6.2 (select: Bad file
descriptor), so... I tried upgrading with openssh-2.3.0p1-1.src.rpm and
openssl-0.9.5a-3.src.rpm No joy. When running just ssh, I get
"Disconnecting: Bad packet length 795178083."
This seems to be a problem with sshd, since the 2.3 ssh client will work
fine with a 2.1 server (but not scp, which still gives
2001 Mar 23
1
openssh 2.3.0p1-5 loses stdout
Hello all
In a recent spate of paranoia we set our server (SuSE Linux 7.0, kernel
2.2.16) to use SSH version 2 and not SSH1. With openssh 2.3.0p1-5 running
as client and server, we find that stdout output is occasionally dropped:
ssh server echo "JJJ"
usually emits JJJ, but sometimes returns nothing -- although the command
is apparently performed.
In the happy case the server logs
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
2000 Dec 06
1
openssh-2.3.0p1 (Linux) fails using options with dss key
I'm trying to change my local setup from ssh2 to openssh-2.3.0p1. I need
captive comands and specific environments for each key, i.e. the
"command=XXX" and "environment=X=y" options. Unfortunately I *also* need
to support the existing ssh2 client for a transition period, since it's
impractical to change all user's environments to openssh in one go.
I have converted
2000 Nov 22
0
openssh 2.3.0p1: chan_read_failed for istate 8
Hallo all!
I've found a repeatable problem concerning openssh 2.3.0p1 running on a
Linux-box with kernel 2.2.17. I compiled ssh from sources with
pam-support. Let me describe what I'm doing:
rsync -e ssh --delete --exclude "/Daten/test*" --exclude
/Daten/anonymous --exclude /Daten/comp_logs --exclude
/Daten/ehemalige_rwgsysm/cache --exclude
2001 Jan 17
1
couple of questions
This is regarding openssh 2.3.0p1 (the following problem was seen on
Linux client / server):
I have a problem with openssh when i don't "login": ie. i do the
following:
ssh -2 10.1.6.13 echo 0
It doesn't print the "0".
However, i can get it to print the "0" by doing the following:
ssh -2 10.1.6.13 echo 0 \; sleep 1
using "ssh -2 10.1.6.13"
2001 Mar 06
1
Segfaults with ssh from Red Hat 6.2 openssh-clients-2.5.1p2-1.i386.rpm
The segfault logged below occurs on two different Red Hat 6.2 systems
running OpenSSH installed from the 2.5.1p2 RPM. (Similar problems occured
with the 2.5.1p1 RPM.)
The most recent of the Red Hat 6.2 systems tested is stock except for an
upgrade of rpm-3.0.5-9.6x.i386.rpm and the install of Red Hat's release of
openssl-0.9.5a-3.i386.rpm, both necessary for the OpenSSH RPM install.
The
2001 Jan 18
0
OpenSSH v2.3.0p1 on Solaris 2.7/2.8 vs. OpenBSD 2.8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've seen a few posts, but no solutions as of yet. Here's a
bit more info.
BoxA - Solaris 2.7, Maintenance Update 01/09/2001, SunWorks cc compiler
BoxB - Solaris 2.8, gcc-2.95.2 gcc compiler
BoxC - Solaris 2.7, Maintenance Update 01/09/2001, gcc-2.95.2 gcc
compiler
BoxD - OpenBSD 2.8, patched to STABLE, gcc-2.95.2 _and_ BSD cc compilers
2001 Feb 12
1
OpenSSH 2.3.0p1 bug with SCO UnixWare 7.1.0
I wasn't sur if you're the right person to send the bug reports to...
SCO Unixware 7.1.0 (uname: UnixWare) and probably the 2.1.x versions
(uname: UNIX_SV)
requires also to have USE_PIPES defined.
Also when compiling with tcpwrap it doesn't link due to the fact that UW
doesn't have setenv() and libwrap have one built-in (duplicate
symbols)...
Also when using the SSH2 protocol to
2000 Nov 22
0
fds closed after SIGCHLD bug still in newest version
Attached is the stderr output of
ssh -v -v -v faxdial "dd if=/dev/zero bs=1c count=1000" 2> log1 | wc
-c
which leads to
423 (this time, it varies)
on stdout, which should obviously be
1000
instead.
Markus Friedl wrote:
>
> could you please try with 'ssh -v'
>
> i cannot reproduce this on openbsd.
>
> post the results to
2000 Dec 05
1
SSH_BUG_SIGBLOB?
Here are the details of my connection attempt:
my computer:
[jgrady at blarg jgrady]$ ssh -V
SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
Compiled with SSL (0x0090581f).
university server:
bash$ ssh -V
ssh: SSH Secure Shell 2.3.0 (non-commercial version) on mips-sgi-irix6.5
and the verbose output of my connection attempt:
[jgrady at blarg jgrady]$ ssh -v xxxxxx.xxx.xxx.xxx
SSH
2000 Nov 12
0
scp problems?
Hi. So I have been having problems using scp to copy
files between two of my machines, both of which are running OpenSSH
2.30p1 (though I've had the same problem with previous versions).
It is basically as simple as the file not being transferred after
authentication occurs. I can however use scp to copy files back and
forth from another machine using a SSH Communications version
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 Mar 15
3
Support for here documents with sftp client in OpenSSH 2.5.1p 1-1 (RH Linux 6.2 [2.2.x kernel])
Damien,
I was going down the path of public key authentication when I encountered
problems. I've been discussing it off-line using the simple example of
creating a key pair with no passphrase for an account on "myserver", then
trying to connect to myserver using the "ssh -i id_dsa myserver" command.
It's not working, so we're debugging now (see below). If you
2001 Apr 27
0
key_verify failed for server_host_key from Solaris 2.7 to non-Solaris hosts
Hi,
I am using OpenSSH 2.5.2p2 on Solaris 2.7 (Ultra 10) with 64bit support and
have the following problem when connecting with the ssh2 protocol to
non-solaris OS:
On the client side, I do:
/local/work/lysis/bin/slogin -v -2 -p 2222 rs30
On the server side (AIX 4.3), the sshd runs as follows:
aix/sbin/sshd -p 2222 -d
Full output follows at the end of this mail.
The server is compiled with
2003 Aug 26
6
Bad packet length error
Hi,
I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am
connecting from a ssh client (openssh-2.9p2) on an x86 Linux box.
This works fine for ssh protocol version 1, but am getting the below error
for ssh v2:
Disconnecting: Bad packet length -857542839.
I am also attaching the complete debug traces from sshd & ssh below.
I am not sure if this is an "endian" issue.
2001 Feb 20
0
Problem with 2.5.1p1 client protocol v2
I have installed 2.5.1p1 on two systems, one running Digital Unix 4.0F
and the other running Red Hat Linux 7.0. I am having trouble connecting
using the 2.5.1p1 client and the version 2 protocol.
Here is a connect attempt from the Linux box (this is after I blew away
my ~/.ssh directory to make sure there was no "cruft" in it). Note that
this also has the all zero key fingerprint that
2000 Oct 14
1
Key exchange/selection badly broken in SNAP1014?
Hello all,
It seems the overhaul on key exchange/selection broke it badly. I haven't
managed to use any other encryption method than 3des and blowfish when
connecting to SNAP -> SNAP. SNAP -> 2.2.0p1 will use arcfour
etc. quite cleanly.
How SNAP -> SNAP looks like:
---
debug: Local version string SSH-2.0-OpenSSH_2.2.0p2
debug: send KEXINIT
debug: done
debug: wait KEXINIT
debug:
2001 Feb 27
1
Bad packet length in 2.5.1 with rijndael (fwd)
I think we are not detecting and setting endianness properly for
rijndael.c.
Can someone on a big endian machine do a "ssh -2 -oCiphers=rijndael128-cbc
littleendianmachine" and vice versa?
-d
--
| Damien Miller <djm at mindrot.org> \ ``E-mail attachments are the poor man's
| http://www.mindrot.org / distributed filesystem'' - Dan Geer
----------
2001 Feb 20
2
Cannot connect to OpenSSH 2.5.1p1
I've installed today the openssh-2.5.1p1 from RPMS and I cannot use it
with protocol 2. It gives:
OpenSSH_2.5.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090600f
debug: Reading configuration data /etc/ssh/ssh_config
debug: Applying options for *
debug: ssh_connect: getuid 500 geteuid 0 anon 0
debug: Connecting to int [10.1.1.1] port 22.
debug: Seeding random number generator
debug: Allocated local