Displaying 20 results from an estimated 6000 matches similar to: "sftp problem"
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 Apr 24
1
HELP! sftp hangs on exit / Bug?
Hi,
The following discussion was posted to comp.security.ssh
however, it seems that my problems may be a bug in
SSH. Could someone please indicate whether there
is a bug fix, or perhaps whether I should go back a
version or so.
In summary:
- Win98 machine (client)
- OpenSSH as packaged with Cygwin tools 1.1.8
(openssh-2.5.2p2-3)
- Connecting to a Sun running Solaris.
ssh: SSH Secure Shell
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 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 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
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 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 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
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 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 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 Apr 09
2
"X11Forwarding yes" causes "error: socket: Protocol not supported"
Greetings,
I'm running OpenSSH_2.5.2p2, and OpenSSL-0.9.6a, on BSD/OS 4.0.
Following the FAQ, I added the following line to my sshd_config
in order to enable X11 forwarding:
X11Forwarding yes
Now openssh is disconnecting my sessions immediately after
authentication and login with the following error messages:
"error: socket: Protocol not supported"
"Disconnecting: Command
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
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 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
2016 Sep 21
2
Where to look next?
Hello,
I'm looking for your insight about the log below. We have an SFTP server (IBM Sterling File Gateway) and we're connecting from an OpenSSH SFTP client but something fails during KEX.
Complete client-side debug output is below, but I believe the relevant part is:
debug1: kex: server->client cipher: aes192-cbc MAC: hmac-sha1 compression: none
debug1: kex: client->server
2016 Sep 21
3
Where to look next?
Thanks for your suggestion! It seems to have gone a little further this time, but isn't accepting the key and is failing back on password-based auth.
We're double-checking that the public key was correctly configured with the account, and also trying a DSA key to see if it behaves differently.
Is there anything you'd suggest we look at or try at this point, and thank you very much
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"
2017 Nov 01
2
Winbind, Kerberos, SSH and Single Sign On
Hi,
at first I'm not sure if this is the correct list to ask this question.
But since I'm using winbind I hope you can help me.
I try to realize a kerberized ssh from one client to another. Both
clients are member of subdom2.subdom1.example.de and joined to it. The
users are from example.de, where subdom1.example.de is a subdomain
(bidirectional trust) of example.de and
2016 Aug 24
3
kex protocol error: type 7 seq xxx error message
Hi,
mancha and me debugged a problem with OpenSSH 7.3p1 that was reported on
the #openssh freenode channel. Symptoms were that this message was
popping on the console during a busy X11 session:
kex protocol error: type 7 seq 1234
I managed to reproduce the problem, it is related to the SSH_EXT_INFO
packet that is send by the server every time it is sending an
SSH_NEWKEYS packet, hence after