similar to: debug output when ssh'ing a remote host

When I encounter the problem with TCP port forwarding locking up, I'll see this on the client window (if I haven't invoked ssh with -q): chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected This is with Blowfish encryption. I have to kill and restart the client when this happens. Phil

Hi, I'm running OpenSSH-1.2.2p1 under RH Linux 6.1. One of my machines is a laptop, and its IP address tends to change as I move it around. I have set its kernel hostname to "vaio.linnet.org", and have the following in /etc/hosts to ensure this name is always usable: 127.0.0.1 localhost.localdomain localhost vaio.linnet.org Now, the problem is with X forwarding. If I ssh into

I'm logging in from an irix machine to a linux machine (both running openssh-2.5.1p2) and am unable to run any X applications. I ran a verbose session and this happens: debug: fd 6 IS O_NONBLOCK debug: channel 0: new [X11 connection from host port 4572] debug: X11 connection uses different authentication protocol. debug: X11 rejected 0 i1/o16 debug: channel 0: read failed debug: channel 0:

The Linux implementation of TCP sockets has a bug which causes shutdown(sock, SHUT_RD) to fail spuriously (ENOTCONN) if the write side of the socket has already been shut down. If you are using SSH port forwarding to tunnel HTTP through a firewall, nchan.c will tickle this bug once for every HTTP exchange. You will therefore get lots of useless, annoying error messages: channel 2:

When I run this command: ssh -1 -v -n -l root njdb1b /usr/bin/X11/xterm -sb -sl 1000 -T njdb1b -e find /etc An xterm appears on my screen, the contents of /etc scroll by and then ssh exits. When I invoke the same command with the -2 option, the xterm appears (and disappears) but ssh never exits. netstat says the (ssh) connection is still established but the xterm is no longer

Hi, FYI - don't sue me for posting this here - I know, everyone who needs this info *should* have it already, but maybe not ;-) Kind regards, B. Courtin -- OpenSSL Security Advisory [30 July 2002] This advisory consists of two independent advisories, merged, and is an official OpenSSL advisory. Advisory 1 ========== A.L. Digital Ltd and The Bunker (http://www.thebunker.net/) are

Hi, I'm wondering whether it is possible to log the key fingerprint (or, the comment of the key) that was used for authentication) with the actual available openssh v3.4p1 on solaris? (with Solaris 8 / UsePrivilegeSeparation yes, if this might be relevant, it seems not) -Is it possible at all? How? -Is there a special sshd configuration option neccessary to use? -Does is only work with a

Hi! I have problems with connections being left open with both 2.2.0p1 and the latest snapshot when using agent-forwarding. (I didn't use this with older versions, so I don't know whether this problem is older.) Scenario: I have a secret key that I run with ssh-agent on host "host-A". I then connect to "host-B" using 'slogin -A host-B'. When executing a

http://bugzilla.mindrot.org/show_bug.cgi?id=413 Summary: Port forwarding: [localhost:]localport:remotehost:remoteport Product: Portable OpenSSH Version: older versions Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo:

Hello, I have encountered a problem using ssh-2.1.1p1 on HP-UX 11.00: Everything else seems to work but running scp results in processes staying open: On the server there are 2 processes still running after copying a file: "scp -v -t /tmp" and one sshd. On the client also a ssh-process stays running until killing one of the processes manually... The copying works fine however.

This to announce a test release of 2.1.0p1 before making it widely available. This release includes many fixes to problems reported over the last week. In particular: - spurious error and coredumps caused by the inbuilt entropy gathering - RSAref detection - Compilation fixes for Solaris and others It also contains (completely untested) support for compiling without RSA support. This may be

http://bugzilla.mindrot.org/show_bug.cgi?id=185 Summary: --with-ipv4-default breaks X11-forwarding on HP-UX 10.20 Product: Portable OpenSSH Version: 3.1p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

Anybody seen this error before and know how to fix it? I only seem to get this under AIX (AIX 4.2.1 - haven't tried higher levels yet). I have not seen this under Solaris and Linux yet. debug1: Received X11 open request. debug1: fd 4 setting O_NONBLOCK debug1: fd 4 IS O_NONBLOCK debug1: channel 0: new [X11 connection from 127.0.0.1 port 3419] debug1: X11 connection uses different

http://bugzilla.mindrot.org/show_bug.cgi?id=176 Summary: OpenSSH_3.1p1 gives X_ShmAttach error on forwarded X11 channel Product: Portable OpenSSH Version: 3.1p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: sshd AssignedTo:

Hi, using OpenSSH_2.1.1 p4 i have problems with X11 forwarding. I used the same sources for Solaris and Linux. Tried nearly every combination, but it seems that the "opensshd" for Solaris has some problems. Of course i tried to connect with "ssh -X", the server has in its /etc/sshd_config: X11Forwarding yes X11DisplayOffset 10 XAuthLocation /usr/openwin/bin/xauth The client

Dear openssh-unix-dev list, in OpenSSH 5.1 you introduced CIDR address/masklen matching for "Match address" blocks in sshd_config as well as supporting CIDR matching in ~/.ssh/authorized_keys from="..." restrictions in sshd. I wonder whether CIDR address/masklen matching will be implemented for permitopen="host:port" restrictions in sshd as well, that would be quite

When permissions on /dev/tty are crw------- and owner root:root, ssh-add will echo passwords to the terminal (sudo does not) and ssh fails with a "Host key verification failed." error. ssh -v -v -v provided a "debug1: read_passphrase: can't open /dev/tty: Permission denied" which is how I figured out that /dev/tty had weird permission issues. I would have expected that

Hello, Being new to the list i hope this question has not been asked before.... As you might know Solaris 9 supportes /dev/random and /dev/urandom bij default and earlier version need to install a patch to have these devices.... But the configuration script under Solaris (Sparc/X86) does not test the existing of the devices... is this to be known as a error/bug? and is there a patch? thanks --

Hi... I have tumpled over quite a big problem on my machine. I'm running Debian Potato with OpenSSH-1.2.3 protocol 1.5 installed from the debian packages. When I ssh from any computer (including my own) then I can't get any programs to display X. I have turned ForwardAgent and ForwardX11 on in my ssh_config. When I turn on debugging this is what I get: 17:14 simpsons at lada% ssh -v

Hello I have this fly::create_dir { "/usr/share/mysql-zrm/pkgs" : mode => 0755, owner => bin, group => bin } ==> creates the directory and parents .. it just does a mkdir -p with couple test so I have file { "$client_package_file" : path => "/usr/share/mysql-zrm/pkgs/$client_package_file",