Displaying 20 results from an estimated 2000 matches similar to: "Bad packet length in 2.5.1 with rijndael (fwd)"
2001 Feb 27
4
Bad packet length in 2.5.1 with rijndael
it seems that this check does not work on solaris
#if BYTE_ORDER != LITTLE_ENDIAN
#define BYTE_SWAP
#endif
could you please check that BYTE_SWAP is defined
in rijndael.c
-m
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
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 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
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 19
1
FreeBSD 4.2 OpenSSH2.3.0 client vs Red Hat 6.2 OpenSSH2.5.1p1 sshd
mdb-bsd is a FreeBSD 4.2-STABLE box morpheus is a Red Hat Linux 6.2
box with openssl 0.9.6 on it.
Attempts to use SSHv2 fail. Using SSHv1 succeeds.
sshd from OpenSSH2.5.1p1 is getting a
fatal: xfree: NULL pointer given as argument
Full client and server interaction given below.
-- Mark
Script started on Mon Feb 19 10:47:01 2001
1:mdb at mdb-bsd$ ssh -v -v -v -2 -x morpheus date
SSH Version
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 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 Apr 04
0
Heh?
On Tue, 3 Apr 2001, Niels Provos wrote:
> Paul, something is broken in your openssh install.
Definately. But is it the client or the server?
I've sent it to the portable OpenSSH bug address.
I'm using OpenSSH 2.5.2p2-1.7 on a RedHat 7.0 with all updates.
Sometimes I can login fine, and sometimes I can't. It actually seems to
almost alternate,
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 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 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
2002 Apr 24
1
Fwd: need help in ssh client: key exchange
This is debugs seen on server, whose keys are
not accepted by the client:
debug1: Seeding random number generator
debug1: sshd version OpenSSH_2.5.2p2
debug1: load_private_key_autodetect: type 0 RSA1
debug1: read SSH2 private key done: name rsa w/o
comment success 1
debug1: load_private_key_autodetect: type 1 RSA
debug1: read SSH2 private key done: name dsa w/o
comment success 1
debug1:
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
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
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 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 Mar 29
1
OpenSSH 2.5.2p2 client to 2.5.1p1 server problem
I'm trying to connect from OpenSSH clients that are version 2.5.2p2 to
several different HP-UX 11.00 machines that are running 2.5.1p1, but
cannot. I can, however, connect to a Linux machine running 2.5.1p1
without problem. I get this message from both a Solaris 2.7 (x86)
machine and a Solaris 2.6 (SPARC) machine.
>From the x86 machine, I get
ssh dozer
51 f6 46 8d 9d 98 17 a6 b6 10 79
2001 Feb 20
0
sftd problem on Tru64 Unix
I have a Digital Unix Version 4.0B and openssh works fine excect for
sftpd. I can do most things things with sftp (copy files, change
directories) but when I do an ls it drops the connection. This is with the
most recent version of openssh "OpenSSH_2.5.1p1". I have included the
output of sftpd -v -v . OpenSSH was complied with the gcc version 2.95.2 19991024
Byron Jennings
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