similar to: Stalls and closes

Displaying 20 results from an estimated 2000 matches similar to: "Stalls and closes"

2005 Jun 16
2
FreeBSD ssh AD authentication
After reading the related chapter in the Samba-3 HOWTO document I've tried to put the AD authentication in place in our network on two systems and I got stuck in exactly the same place. Here are the software configs I was using : Sys 1 FreeBSD 4.11 release sshd version OpenSSH_3.5p1 FreeBSD-20030924 Samba Version 3.0.10 Sys 2 FreeBSD 5.4-RELEASE FreeBSD amd64 OpenSSH_3.8.1p1
2007 Feb 27
1
What would cause keyboard-interactive packet connection close
Hi, I've got a remote system that was down and came back up. I'm trying to get into the system, but when I do I get timed out. I forced it to a keyboard interactive to speed things up: ssh -o PreferredAuthentications=keyboard-interactive -vvv tuc at 10.2.0.2 but I get : debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done:
2004 Apr 29
1
OpenSSH bug: server debug output sent to client
Hello SSH developers, When using the sshd '-d' switch, then the following problem occurs when a connecting client uses the ssh1 protocol: part of the server's debug output is not printed to (the server's) stderr, but delivered to the client (to the client's stderr). Verified with the FreeBSD version of sshd, and with sshd-3.7.1p2 --snip--server: # /usr/sbin/sshd -ddd debug1:
2003 Feb 05
0
openssh 3.5p1 hostbased authentication
hello, i did some debugging today, here is the weird portion form sshd -d -d -d debug1: userauth-request for user jholland service ssh-connection method hostbased debug1: attempt 1 failures 1 debug2: input_userauth_request: try method hostbased debug1: userauth_hostbased: cuser jholland chost i2-0. pkalg ssh-dss slen 55 debug3: mm_key_allowed entering debug3: mm_request_send entering: type 20
2008 Mar 18
1
ssh: Disconnecting: Bad packet length
Hello, I have the following problem with ssh on Solaris 10, 64bitx86 systems: bash-3.00# ssh -v admin at 172.20.11.244 OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to 172.20.11.244 [172.20.11.244] port 22. debug1: Connection established. debug1: identity
2006 Nov 18
1
PEM_read_PrivateKey failed issue
Hello, I'm having a problem with my ssh client, on FreeBSD 5.4 and 6.1 the same issue. OpenSSH_3.8.1p1 FreeBSD-20040419, OpenSSL 0.9.7e 25 Oct 2004 but also same problem with OpenSSH_4.3 When I make a key, everything goes fine. When I try to change the password on the key it give me the 'PEM_read_PrivateKey failed' problem, this also prevents me from connecting to another host.
2003 Jan 07
0
Bug in Ossh3.5p1
We use OpenSSH 3.5p1 on an embedded system. OpenSSH is configured to not permit password logins, /etc/ssh/sshd_config: ... PasswordAuthentication no ... At the same time, since there is no console and no way to "log in" other than by ssh, /etc/passwd has an "open" root account: root::0:0:root:/root:/bin/sh nobody:x:65534:65534:nobody:/tmp:/usr/bin/bash Apparently
2002 Nov 20
0
[marco.ortisi@flashcom.it: Re: bug on openssh 3.5p1]
related to RST-based close in one case? can someone investigate or dup? ----- Forwarded message from marco.ortisi at flashcom.it ----- Date: Tue, 19 Nov 2002 11:49:30 GMT From: marco.ortisi at flashcom.it To: Kevin Steves <stevesk at pobox.com> Subject: Re: bug on openssh 3.5p1 Excuse me for delay...i have much work in this time...then >can you post to the list? i don't have
2003 Mar 21
5
[Bug 516] RhostsAuthentication failing under AIX 4.3.3
http://bugzilla.mindrot.org/show_bug.cgi?id=516 Summary: RhostsAuthentication failing under AIX 4.3.3 Product: Portable OpenSSH Version: 3.5p1 Platform: PPC OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:
2004 Jun 26
1
unexpected problem
I've had a dedicated box running for ages in my LAN without any kind of problems. Ssh has been installed and useable till tomorrow when a problem pop up. KERNEL: 2.6.5 no server or client settings have been changed. I can ping and nmap the host without any kind of problems. Bellow I'll paste a verbosed ssh try. bkw at tellus ~ $ ssh -vvv neptune OpenSSH_3.8p1, SSH protocols 1.5/2.0,
2002 Dec 11
4
OpenSSH-3.5p1: sshd fails at run-time
Here's what I get: bash-2.02# sshd -ddd -p 1234 debug3: Seeding PRNG from /usr/local/libexec/ssh-rand-helper debug1: sshd version OpenSSH_3.5p1 debug1: private host key: #0 type 0 RSA1 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM
2002 Oct 16
3
ssh-3.5p1 core dumps on Solaris 2.6
Hi, I've reported this problem a month ago on this list, and probably no-one is interested? Binaries were configured with krb4 and afs enabled. However, only the second crash seems to be related to krb4. Any thoughts? I had to add one line to includes.h: #include <sys/types.h> #include <sys/socket.h> #include <sys/ioctl.h> +#include <sys/ioccom.h> #include
2006 Nov 30
0
Issue while Running SSH from a Windows Service
Hi All - It seems to be an odd scenario. I have a simple ssh command which establishes connection with a UNIX machine and executes some commands over there. When I ran the command from command window, I was able to successfully run them. In reality I wanted the ssh command to be invoked by a windows 2003 service. I tried to debug the ssh command while running from a service and I get the below
2008 Sep 15
3
ssh to FreeBSD 4 systems: xmalloc: zero size
Hi, With the latest FreeBSD 7.1 PRE-RELEASE, I am having trouble ssh'ing to FreeBSD 4 systems. I am getting this error: OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connection established. debug1: identity file /homes/rodrigc/.ssh/identity type -1 debug1: identity file
2004 Jun 24
1
[Bug 886] Unable to scp from OPenSSH to Commercial SSH
http://bugzilla.mindrot.org/show_bug.cgi?id=886 Summary: Unable to scp from OPenSSH to Commercial SSH Product: Portable OpenSSH Version: 3.8.1p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy:
2005 Apr 28
1
ssh 4.0 under AIX 5.3 password expiration
I have a user who's password has expired (ADMCHG) flag is set in /etc/security/passwd under AIX 5.3. For some reason it is not prompting for new passwd. This worked in 3.9. Any ideas? Thanks, Ryan # /usr/sbin/sshd -d debug1: sshd version OpenSSH_4.0p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read
2004 May 06
2
ID mismatch
Hi, When do the sftp to remote server with file system full, sftp connection get "ID mismatch" and connection closed. Is it supposed to get the "sftp>" prompt back? I try with V3.7.1p2 and V3.8.1p1 and have the same result. Please help. rdsosl.sef_cdf-831# sftp -v edosuser at rdsosl Connecting to rdsosl... OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading
2003 Feb 24
1
[Bug 502] New: sshd fails when "Compression yes" set on HPUX
http://bugzilla.mindrot.org/show_bug.cgi?id=502 Summary: sshd fails when "Compression yes" set on HPUX Product: Portable OpenSSH Version: 3.5p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org
2016 Feb 03
3
[Bug 2538] New: openssh v7 config parse regression
https://bugzilla.mindrot.org/show_bug.cgi?id=2538 Bug ID: 2538 Summary: openssh v7 config parse regression Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: All Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org
2005 Feb 01
2
Rsync and SSH on Windows
I am writing a program that synchronizes my companies Windows laptops with our home server. Due to the nature of our proxy/firewall, I must use SSH with port forwarding to achieve this goal. Currently I establish the SSH connection using the following command: ssh ssh_user@proxy.example.com -i file_name -L 873:200.200.60.60:7000 -N and then run rsync with the following command: rsync