Displaying 20 results from an estimated 2000 matches similar to: "OpenSSH 2.3.0p1 protocol 2 problem with AIX"
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 Feb 24
1
scp user@host1 user@host2 broken?
Hello all,
Is it just me or is 'scp user at host1 user at host2' broken (if the server asks
you for the password)?
1) [password required]
>From OpenSSH 2.5.1p1 -> OpenSSH 2.5.1p1 -> OpenSSH 2.3.0, I get like:
> scp pekkas at xxx:~/*.patch psavola at yyy:~/temp/
psavola at xxx's password:
You have no controlling tty. Cannot read passphrase.
lost connection
2)
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 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 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 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
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 08
2
OpenSSH 2.3.0p4/2.2.0p1, Solaris 8, ssh-keygen bus error
Hi,
I'm having a problem with ssh-keygen on Solaris 8; upon running, it
produces a bus error due to a function call in OpenSSL (RC4_set_key):
[...]
(gdb) where
#0 0x3440c in RC4_set_key ()
#1 0x2b890 in arc4random_stir ()
at /merc/tools/src/openssh-2.3.0p1/bsd-arc4random.c:65
#2 0x23ca8 in main (ac=1, av=0xffbefb94)
at /merc/tools/src/openssh-2.3.0p1/ssh-keygen.c:720
I get
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
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
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 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 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
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
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 Feb 16
7
OpenSSH 2.5.0p1
Known issues:
1) Linux 'sleep 20' -- Unfixable before 2.5.0 (known work around)
2) HP/UX signal issue -- Patched and HP/UX 11 works in v2
3) SCO 2/ Native Compiler -- Unfixable before 2.5.0 (known work around)
4) NeXTStep -- Resynced, MAX_GROUPS vs NGROUPS unresolved (not major)
5) DG/UX regcomp/regexec -- Fixed.
6) Cray signal issues -- ???
7) Solaris '$PATH' issue -- ??
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