Displaying 20 results from an estimated 1000 matches similar to: "OpenSSH 2.5.0p1"
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 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 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 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 05
1
I have an odd OpenSSH compatablity issue
I am on Solaris 2.8 with openssh 2.3.0p1 and openssl 0.9.6.
The remote machine is running ssh.com 1.2.20 and Solaris 2.6.
I think the problem has to do with the 1.2.20 KeyRegeneration, because in
the next hour I will beable to get into the machine ok with openssh and
then later in the day I will not beable to ssh in again for another hour.
ssh -v -v sa at myhost.com
SSH Version OpenSSH_2.3.0p1,
2000 Jun 20
2
Critical EGD handling in 2.1.1p1
Hi,
when running OpenSSH with EGD as entropy source, the sshd server connects
to the EGD socket and leaves it open to re-seed on the fly.
Unfortunately the connection is not checked when re-seeding, so that
a failure or restart of EGD will lead to a "fatal()" abort of the sshd
server process.
Since a dying server process can not be accepted, I would recommend to
not have sshd call it
2002 Feb 12
3
Problem with ssh-keyscan: no hostkey alg
Hi,
I am using ssh-keyscan with a list of hosts, such as:
ssh-keyscan -t rsa -f hosts_for_keyscan
Some of the hosts in the list have dsa, but no rsa keys. For such
hosts, the command displays:
no hostkey alg
When this is the case for 2 hosts, this message appears twice AND
SSH-KEYSCAN STOPS QUERYING, which means that no keys at all are
returned for the following hosts.
Here is the part of the
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 22
11
Lets try this push again.. 2.5.1p2 bugs left.
Things that are still outstanding:
1) Solaris/Redhat/HPUX session.c patch. I've not seen a ya or na on
Kevin's pam patch from the Solaris group.
2) Odd Redhat/Debian scp/ssh issues. .. I'm baffled, and I can't
replicate the bug. Nor have I seen anything remotely like it reported.
3) SCO.. Is it happy yet for compiling? =)
Completed:
1) mdoc2man.pl .. Commited into
2000 Nov 15
4
Openssh-2.3.0p1 protocol 2 problem
Hi all,
I just implemented (compiled from tarball) Openssh-2.3.0p1 on two different
platform: an HP-UX 11.00 (the client) and a Redhat 6.2 (the server).
On server (Linux RH-6.2) side the following compile options are considered:
# CC="egcs" \
> ./configure \
> --prefix=/opt/openssh \
> --sysconfdir=/etc/opt/openssh \
> --with-tcp-wrappers \
> --with-ipv4-default \
>
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:
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,
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
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 Feb 19
7
Packet integrity error. (34)
Hi,
I am using Van Dyke SecureCRT 3.2.1 to access an AIX server running
OpenSSH-2.5.0p1. Using ssh1 with X11 forwarding enabled, the server
reports the following error (in the client session):
Packet integrity error. (34)
This problem was not evident in 2.3.0p1. Running sshd in debug gives the
output:
debug1: sshd version OpenSSH_2.5.1p1
debug1: load_private_key_autodetect: type 0 RSA1
2000 Jun 15
1
problem in entropy.c if no getrusage
entropy.c assumes RUSAGE_SELF and RUSAGE_CHILDREN
*** entropy.c.orig Thu Jun 15 13:57:28 2000
--- entropy.c Thu Jun 15 13:58:25 2000
***************
*** 201,207 ****
--- 201,209 ----
total_entropy_estimate += stir_gettimeofday(1.0);
total_entropy_estimate += stir_clock(0.2);
+ #ifdef HAVE_GETRUSAGE
total_entropy_estimate += stir_rusage(RUSAGE_SELF, 2.0);
+ #endif
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