Displaying 20 results from an estimated 1000 matches similar to: "X11-Forwarding OpenSSH 2.1.1p4 problem"
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 Jul 20
1
Incompatibility with free version
First off, I am not a subscriber, so please CC replies to my
email address. The problem I am having -- I do not know who is to blame,
but am just covering all angles. I run OpenSSH 2.1.1 on FreeBSD. When I
try to connect to a server running ssh2d from ftp.ssh.com, it fails
saying corrupted MAC on input. I am including a log of my connection
below:
% ssh -v -l diwanh tomcat
SSH Version
2000 Jun 28
2
SSH-2.2.0 (for Windows) and OpenSSH-2.1.1p1
I just upgraded my Windows SSH client from the 2.1.x version (whatever it
was) to 2.2.0 and am now experiencing difficulties connecting to my
OpenSSH-2.1.1p1 Linux servers.
I'm not as up-to-speed as I should be on the inner workings of the
handshakes that go on, but from the debug logs and from trying different
connection methods, it seems to be isolated to using publickeys. This
2000 Jun 13
2
SCP Problems.
Just added myself to the list, and I saw that somebody else had the same
problem that I have, namely that I can't get "scp" to work. The similarities I
could see was that we both use linux as the platform for issuing the command
"scp", however I also use linux on the destination. The other similarity is that
we both are using strictly version 2 of the ssh protocol. I've
2000 Jul 05
1
some problems reading rsa/dsa keys
Hi people,
Please excuse this rather long debug output...
$ uname -a
SunOS echelon 5.6 Generic_105181-17 sun4u sparc SUNW,Ultra-Enterprise
$ /usr/local/openssh/bin/ssh -v x.x.x.x
SSH Version OpenSSH_2.1.1, protocol versions 1.5/2.0.
Compiled with SSL (0x0090581f).
debug: Reading configuration data /usr/local/etc/ssh_config
debug: Applying options for *
debug: ssh_connect: getuid 1002 geteuid 0
2000 Sep 27
2
trouble logging out when using protocol version 2
Dear OpenSSH gurus,
My machine is running Red Hat Linux 6.1 and has installed all of the
6.binary rpms generated from the source rpms openssh-2.2.0p1-2.src.rpm
6.and openssl-0.9.5a-3.src.rpm.
When I use protocol version 2 (by specifying "Protocol 2,1" in
~/.ssh/config), I can establish connections properly, but they do not
shut down properly. When I run a remote command by "ssh
2000 Jun 21
1
SSH 2.2.0
Yo All!
I have been playing with SSH 2.2.0 from www.ssh.com. I can not
connect to openssh 2.2.1p1 using Ver 2 protocol from ssh Ver 2.2.0.
Ver 1 works fine.
See below for the debug output from both ends
If I force hmac-md5 (-m hmac-md5) from the sender it works!
The other 3 choices fail: hmac-sha1; hmac-md5-96; and none.
I have no problem connecting to this openssh host (hobbes) from
2000 Aug 31
1
slightly overzealous RNG seeding?
Hello again,
I was testing today's SNAP (openssh-SNAP-20000830.tar.gz) in my
Solaris 2.6-8 environment, when I found some problems with the ssh2
support.
While connecting, it seeds the RNG something like 32 times! And then
once connected, it seeds again 2 or 3 times with *every* keystroke! This
makes for some slow going. This happens on all of the Solaris boxes I
tried. Binary was
2000 Jun 06
0
SCO Openserver 5.0.5 ssh2 problem.
I just finished compiling openssh-2.1.0p3 on a SCO openserver system. I
generated the keys fine and genereated the host keys both rsa and dsa
without problems.
ssh (version1) works great.
I tried to use ssh (version 2) and after being prompted to login, it
quits. I am attaching a script file of...
ssh -v -2 root at sco to see if you can find the problem. Let me know how I
can help.
[root at
2000 May 28
1
Protocol error's with 2.1.0p2
I'm getting "Protocol errors" when trying to scp files from my
laptop to my desktop (only when trying to scp root at laptop:/path/file, not
vis-vis). See screen dump's at end of e-mail for exact details. The most
confusing thing about this problem (to me anyway), is that this is a
one-way problem. I can log into the laptop and scp files down from the
desktop no problems.
2000 Jul 15
0
openssh-2.1.1p3 - problem with -i option
Greetings:
I've just attempted to upgrade from openssh-2.1.1p1 to openssh-2.1.1p3
and I'm having problems with the server component. My system runs RedHat
Linux 6.2 (x86 version) with all currently released updates applied.
The sshd daemon is being spawned by xinetd with the -i option and worked
fine with the p1 level release.
Now, when a remote client attempts to connect to the daemon,
2000 May 19
0
openSSH2.1.0
Hi,
I just installed openSSH2.1.0 an a linux system and tried to connect to a
server running an SSH2 server.
Unfortunately I wasn't able to connect because of a signature error.
I am connecting to the host for the first time.
Does anybody know, why I have this problem and why I can't connect?
Thanks,
Stefan Mangard
Here is the debug output:
[smang at grad1 bin]$ ssh -2 -v
2000 Sep 06
0
2.1.1p4: sessions automatically closed, if sshd is run from inetd
Hi all,
I have noticed a problem with the newly released version 2.1.1p4 (as well
as with 2.1.1p3) :
If sshd is run from inetd, all interactive sessions are automatically closed
right after (successful) login.
The problem disappears, if sshd is run from the command line (ie. no -i option)
and did not exist in 2.1.1p2.
This was noticed on a linux x86 box. I have appended a typescript of the
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 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 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 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,
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
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 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