similar to: [OpenSSH_5.1] Untrusted X11 forwarding (ssh -X) no longer works?

Hello! scp hangs while copying file over a certain size. Here's the output of scp in verbose mode: scp -v test.pdf pc: Executing: program /usr/bin/ssh host pc, user (unspecified), command scp -v -t . OpenSSH_5.1p1, OpenSSL 0.9.8j 07 Jan 2009 debug1: Reading configuration data /home/user/.ssh/config debug1: Applying options for pc debug1: Reading configuration data

Alan Coopersmith (4): Mark usage as noreturn, as suggested by -Wmissing-noreturn configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 xeyes 1.1.2 Emil Velikov (1): autogen.sh: use quoted string variables Gaetan Nadon (2): config: replace deprecated AC_HELP_STRING with AS_HELP_STRING config: move man pages into their own directory Mihail

This issue has been discussed here and elsewhere a fair bit in the past year or so, but to re-address the issue... As of OpenSSH 2.9.something the ability to have an Xauthority located in /tmp was removed, with the following description in the ChangeLog : - markus at cvs.openbsd.org 2001/06/12 21:21:29 [session.c] remove xauth-cookie-in-tmp handling. use default $XAUTHORITY, since

in reply to: 5.1p1 and X11 forwarding failing http://lists.mindrot.org/pipermail/openssh-unix-dev/2009-February/027183.html I have the impression that SSH is running xauth with a filename in a temporary directory that does not exist: local:~ $ ssh -vv user at remote ... debug2: x11_get_proto: /usr/bin/xauth -f /tmp/ssh-VskgWb3776/xauthfile generate :0 MIT-MAGIC-COOKIE-1 untrusted timeout 1200

I was trying an assortment of things to get a remote X session working (where I had forgotten to install the xauth package...) and noticed that running xeyes kills my freenx session. This happened whether in the NX/freenx session itself or when run on a remote machine via 'ssh -Y', started from a window in a freenx session. Is that a known problem or do I have something set up wrong?

Hello, I know this is likely to give me a brute force attack hit, but the only thing anyone can accomplish by ssh-ing to my machine is to provide me with a tunnel into your machine. So don't bother. Anyway, my server machine is running this: /usr/bin/ssh -X -R ${port}:localhost:22 -o BatchMode=yes \ -o StrictHostKeyChecking=no ${user}@${my_home_machine} On my local machine: ssh -vvv -X

Hello, I am experiencing some strange behaviour that I am hoping someone can shed some light on. OS and kernel: Red Hat Enterprise Linux AS release 4 (Nahant Update 5) Linux host135 2.6.9-67.9hp.7sp.XCsmp #1 SMP Thu Jul 3 18:55:59 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux built both openssh-5.0p1 and openssh-5.1p1 with the following options: ./configure --prefix=/usr

Hello, I have been having issues with x11 forwarding using my linux-mandrake based servers. I checked my XAUTHORITY variable and it was set to ~/.Xauthority ... After reading the mail archives, I found the /tmp/ssh* directory created during my ssh session, and did this: export XAUTHORITY="/tmp/ssh-hzuA1805/cookies" xeyes ...and the X11 forwarding worked! I'm using the

Hi, i'm using Cygwin under Win2000 to ssh Debian-Linux. I've changed die /etc/sshd_config file, to enable X11UseLocalhost no. But die Remoteserver said wenn launch xeyes: X11 connection rejected because of wrong authentication. X connection to localhost:10.0 broken (explicit kill or server shutdown) Pls help me.Thanks! regards lingli

From: Chris Barker <barker at ling.ucsd.edu> To: openssh-unix-dev at mindrot.org Subject: X forwarding (still) broken on Linux This may be a lack-of-adequate-documentation problem rather than a bug, but I can't get X forwarding to work: localhost$ set | grep DIS DISPLAY=localhost.localdomain:11.0 localhost$ set | grep XA XAUTHORITY=/tmp/ssh-gzg13204/cookies localhost$ ssh -v

Well this is weird... when I connect via SSH Secure Shell PC client 3.0.0, the server hangs and the client sees a disconnect as soon as the user activates certain X programs. But not all of them! For instance, xeyes and xlogo are fine... but emacs and xterm are not. This is 3.0.2p1 on Solaris 2.5.1. When the client runs xterm the output of sshd -d -d -d is: debug1: X11 connection

Hi ! I promised to report the result to the list. Here it is: Damien Miller [SMTP:djm at mindrot.org] wrote yesterday on his keyboard: > On Mon, 8 Jan 2001, Bladt Norbert wrote: [...] >> During the last week I did some investigations why the X11 forwarding >> on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box >> with OpenSSH-2.3.0p1. >> >> The

After upgrading to 5.1, connections to our Juniper E-Series routers fail with: $ ssh -v eseries OpenSSH_5.1p1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh_config debug1: Applying options for *-lns* debug1: Applying options for * debug1: Connecting to eseries [1.2.3.4] port 22. debug1: fd 3 clearing O_NONBLOCK debug1: Connection established. debug1: identity file

Here's a patch for a feature I'm used to having in the old commercial ssh. It checks for usernames the file /etc/nologin.allow when /etc/nologin is in place, and lets the users mentioned in /etc/nologin.allow in regardless of /etc/nologin. This is very usefull for remote administration of servers. Please consider applying this. -jf -------------- next part -------------- ---

On Sun, 9 Apr 2000, barker at ling.ucsd.edu wrote: > This may be a lack-of-adequate-documentation problem rather than a bug, > but I can't get X forwarding to work: > > localhost$ set | grep DIS > DISPLAY=localhost.localdomain:11.0 > localhost$ set | grep XA > XAUTHORITY=/tmp/ssh-gzg13204/cookies > localhost$ ssh -v localhost > SSH Version

I've running a rsyncd and ssh port forwarding (-R 12345:localhost:873 backup@server) on a client because the client should not reachable but over ssh. The rsyncd should acessible because I can backup and restore files with backuppc (a wonderfull program which use perl::rsync) And I can "ssh -p 12345 backup@localhost" to this client too. If I try to connect (from the machine/user

Hello list! So I recently reconfigured our office network to allow a permanent VPN connection to our data center. This consists of a Juniper SSG-520 connected via a tunnel to a Juniper Netscreen-25 over a 100M leased NTT VPN (yes I'm tunneling over the VPN as it's the only way to make it routable.) Here is where OpenSSH come in. When I try and ssh to a machine on the other end

sshd also dies when certain other kinds of traffic is generated, such as `man pw' using the most pager[1], and many x11 apps such as emacs. However, it is stable when running simple x11 apps such as xeyes, and the link its self is stable -- a terminal will stay connected without issue for days, as long as not much happens in it. Also a sshfs connection dies immediately. ssh -Y karren gkrellm

https://bugzilla.mindrot.org/show_bug.cgi?id=1549 Summary: change in remote command execution behavior Product: Portable OpenSSH Version: 5.1p1 Platform: amd64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy:

Referring to "CLOSED FIXED" Bug 85: https://bugzilla.mindrot.org/show_bug.cgi?id=85 Assuming that you have your machine setup so that the following commands run without prompting: ssh -2 localhost pwd ssh -1 localhost pwd Then this command: ssh -1 localhost yes | true always produces this output: Write failed flushing stdout buffer. write stdout: Broken pipe Yet