search for: eakin

...nv, &envsize, "TERM", term); if (display) child_set_env(&env, &envsize, "DISPLAY", display); + if (original_command) /* LEE */ + child_set_env(&env, &envsize, "SSH_ORIGINAL_COMMAND", original_command); /* LEE */ #ifdef _AIX { -- Lee Eakin - leakin at ti.com - Naming Services, Texas Instruments -o) [ permanent e-mail: Lee at Eakin.Org ] /\\ _\_v echo "forgot::0:0::/:/bin/sh" >> /etc/passwd; echo "If you forgot y...

I'm using: % ssh -V SSH Version OpenSSH-1.2.3, protocol version 1.5. Compiled with SSL. % uname -a Linux gellar 2.2.13 #1 SMP Wed Dec 29 14:07:41 PST 1999 i686 unknown and am wondering whether it's a fundamental shortcoming of the SSH protocol that argument splitting is not preserved from client to server, but instead the argument list is re-split on whitespace. E.g., from my machine

I know that there was a discussion on this about a year back, and there is a bug 556 this week that mentions TCP_NODELAY. However, when I use ssh through a pipe (e.g., to tunnel through an HTTP proxy using CONNECT) I see: getsockopt TCP_NODELAY: Socket operation on non-socket How do I tell which end is generating this (I'm assuming the local side, which is running through the pipe). Also,

hi, I'm trying to compile OpenSSH, latest version on my Linux box. I know that it requires openssl and I've installed the 0.9.5a and it's working just fine. Now when I'm trying to ./configure the openssh with the options ./configure --prefix=/usr/local/bin/openssh/ --without-pam --without-shadow --with-tcp-wrappers It's giving me checking for openssl directory... configure:

Using OpenSSH_2.9p2 on Linux and Sparc Solaris. Trying to connect from Linux to Solaris, with remote port-forwarding i.e. On Linux, ssh -R 3000:Linux:23 Solaris The connection is established okay, but the port-forwarding does not work; on Solaris, the connection to localhost port 3000 is accepted, but it appears as if no data makes it back to port 23 on Linux. If an older 1.2.30 sshd is used

Hi all, I'm using openssh-2.9p2 on Solaris 2.8. I can get remote port forwarding to work using the -R flag, but only with ssh protocol 1 not ssh protocol 2. I've read that remote forwarding protocol 2 was not supported in earlier versions of openssh, but I'm wondering if this is still the case. Jarno Huuskonen [Jarno.Huuskonen at uku.fi], posted a patch in 2000 to add support for

...e message by skipping the call to error only if errno == ENOTSOCK. There is probably a better way to handle this, maybe not calling set_nodelay when a proxy is in use? I just figured reporting it was better than keeping silent. Apply, mangle, or ignore as you see fit. See attached. -- Lee Eakin - leakin at dfw.nostrum.com I think our coffee machine is networked -- I keep seeing these dropped sugar packets all around it. -------------- next part -------------- diff -u misc.c.ORIG misc.c --- misc.c.ORIG Sun Dec 22 20:44:36 2002 +++ misc.c Mon Mar 31 15:40:18 2003 @@ -97,7 +97,9 @@ opt...

I noticed a difference in verbose output that appears to be unintentional. it first prints 'receiving file list ...', then builds the list and prints 'done\n'. I haven't figured out the exact conditions yet, but with multiple remote sources (remote shell expands) it sometimes prints the 'done\n' message multiple times. I have a script I use to sync up my dot-files

On Thu, May 15, 2003 at 10:40:21PM -0500, Lee Eakin wrote: > > Date: Thu, 15 May 2003 20:11:09 -0700 > > From: jw schultz <jw@pegasys.ws> > > Subject: [RFC] report options > > > > I have hinted in the past of wanting to go to a more > > selective control of the output of rsync. Here it is. > > >...

Can't seem to find the answer anywhere... I'm currently using an rsync script on the source box to transfer some individual files to the destination box...all works well. The script: rsync -e ssh \ /var/qmail/control/file1 \ /var/qmail/control/file2 \ /var/qmail/control/file3 \ /var/qmail/control/file4 \ destination-box.xxxxx.com:/var/qmail/control Now, instead of "pushing"

I have hinted in the past of wanting to go to a more selective control of the output of rsync. Here it is. PROBLEMS with the existing --verbose et al. The simple incrementing verbose doesn't allow one to restrict stdout to what actually is of interest. For instance inside dirvish i don't care about directories, or any kind of non-regular file because they show up every time even if