search for: ostate

can someone confirm this? it does not happen on openbsd. -------------- next part -------------- An embedded message was scrubbed... From: Florian Wunderlich <fwunderlich at devbrain.de> Subject: Re: fds closed after SIGCHLD bug still in newest version Date: Wed, 22 Nov 2000 14:44:17 +0100 Size: 3926 Url:

...utdown_read(Channel *c) { debug("channel %d: shutdown_read", c->self); if (shutdown(c->sock, SHUT_RD) < 0) error("chan_shutdown_read failed for #%d/fd%d [i%d o%d]: %.100s", c->self, c->sock, c->istate, c->ostate, strerror(errno)); } Although the self and sock fields vary, ostate is 128 and istate is 1 in the warning messages. ======================================== Where does ostate get set? ---------------------------------------- grep ostate *.c *.h channels.c: chan_init_iostates(c); channels.c:...

Log snippet: channel 10: istate 4 != open channel 10: ostate 64 != open channel 11: istate 4 != open channel 11: ostate 64 != open channel 12: istate 4 != open channel 12: ostate 64 != open channel 13: istate 4 != open channel 13: ostate 64 != open channel 14: istate 4 != open channel 14: ostate 64 != open channel 15: istate 4 != open channel 15: ostate 64 !...

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 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

...2 @@ /* events concerning the INPUT from socket for channel (istate) */ chan_event_fn *chan_rcvd_oclose = NULL; chan_event_fn *chan_read_failed = NULL; +chan_event_fn *chan_wont_read = NULL; chan_event_fn *chan_ibuf_empty = NULL; /* events concerning the OUTPUT from channel for socket (ostate) */ chan_event_fn *chan_rcvd_ieof = NULL; chan_event_fn *chan_write_failed = NULL; +chan_event_fn *chan_wont_write = NULL; chan_event_fn *chan_obuf_empty = NULL; /* * ACTIONS: should never update the channel states @@ -137,6 +139,28 @@ } } static void +chan_wont_read_12(Channel *c)...

...lose_read", c->self); if (c->sock != -1) { - if (shutdown(c->sock, SHUT_RD) < 0) + /* shutdown(sock, SHUT_READ) may return ENOTCONN if the + write side has been closed already. */ + if (shutdown(c->sock, SHUT_RD) < 0 + && (errno != ENOTCONN + || c->ostate == CHAN_OUTPUT_OPEN + || c->ostate == CHAN_OUTPUT_WAIT_DRAIN)) error("channel %d: chan_shutdown_read: shutdown() failed for fd%d [i%d o%d]: %.100s", c->self, c->sock, c->istate, c->ostate, strerror(errno)); } else {

As of Sunday evening, OpenSSH has an interactive sftp client. It should be in the more recent snapshots. It would be appreciated if you could test new client and find all the bugs :) Please also have a read of the manpage and ensure that it matches what is implemented. I am working on fixing the ones that I know about, so please try to stay up to date with the snapshots. Thanks, Damien

The command "ssh ls -l /doesnotexist" gives various responses: Running from a 200 MHz PentiumPro with dsa key added to ssh-agent: Mistakes worst to fast machine: To a faster 600 MHz dual processor i686 600 MHz machine: ls: /doesnotexist: No such file or directory -- correct nothing at all -- wrong ls: select: Bad file descriptor -- wrong

...orwarding on both the client and server side. When I connect to the other side and run an X app, I get two errors and it fails. Example: [mhw at alcove mhw]$ ssh canyon Last login: Mon May 15 05:41:07 2000 from alcove.wittsend.com [mhw at canyon mhw]$ xterm channel 0: istate 4 != open channel 0: ostate 64 != open X connection to canyon:10.0 broken (explicit kill or server shutdown). [mhw at canyon mhw]$ echo $DISPLAY canyon:10.0 [mhw at canyon mhw]$ Sooo.... Offset is 10 and DISPLAY is getting set properly, but I get these istate and ostate errors on channel 0. What have I got screwed up her...

...ot sure what is going wrong here, but could you please try a > snapshot? We fixed a long-existing race in the efd handling @ close > case and the fix may serendibitously fix your case :) > Is this race condition check the changes in channel_register_cleanup(), where c->istate and c->ostate are being interrogated? I'd really like to avoid having to add all the changes in channel.c (the queueing, changed external interfaces, etc...) if I could avoid it.

Using OpenSSH_8.3p1 I had an open (working) connection to some other box; after a bit of inactivity, some device in the middle seems to have forgotten about the TCP connection (NAT) and broke it. I've got an EscapeChar defined, though; so first I tried to send a BREAK and, when that didn't help (TCP already gone, packets get lost!), I tried (just out of curiosity) a Rekey. Now I can see

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=448 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|ip_conntrack |nf_conntrack ------- Additional Comments From laforge@netfilter.org 2006-02-14 09:05 MET ------- ipv6 conntrack is

...; wait_oclose debug: channel 0: send ieof debug: channel 0: write failed debug: channel 0: output open -> wait_ieof debug: channel 0: send oclose debug: channel 0: close_write debug: X11 closed 0 i4/o64 debug: channel 0: rcvd ieof debug: channel 0: non-open channel 0: istate 4 != open channel 0: ostate 64 != open debug: channel 0: rcvd oclose debug: channel 0: input wait_oclose -> closed X connection to pc07:10.0 broken (explicit kill or server shutdown). X forwarding is configured for both the servers and clients on both systems...and they have access through tcpwrappers for forwarding. Al...

...e have to remove the fd's from the select mask diff -u openssh-2.9.9p2/channels.h openssh-2.9.9p2J/channels.h --- openssh-2.9.9p2/channels.h Mon Sep 17 23:51:14 2001 +++ openssh-2.9.9p2J/channels.h Thu Sep 27 22:16:44 2001 @@ -219,6 +219,7 @@ void chan_mark_dead(Channel *); void chan_init_iostates(Channel *); void chan_init(void); +void chan_shutdown_read(Channel *); typedef void chan_event_fn(Channel *); diff -u openssh-2.9.9p2/clientloop.c openssh-2.9.9p2J/clientloop.c --- openssh-2.9.9p2/clientloop.c Mon Sep 17 23:51:14 2001 +++ openssh-2.9.9p2J/clientloop.c Fri Sep 28 12:47:0...

...et, writeset); + } channel_garbage_collect(c); } } diff -ur openssh-3.0p1/channels.h openssh-3.0p1J/channels.h --- openssh-3.0p1/channels.h Thu Oct 11 19:35:06 2001 +++ openssh-3.0p1J/channels.h Tue Nov 13 15:55:52 2001 @@ -218,6 +218,7 @@ void chan_mark_dead(Channel *); void chan_init_iostates(Channel *); void chan_init(void); +void chan_shutdown_read(Channel *); typedef void chan_event_fn(Channel *); diff -ur openssh-3.0p1/clientloop.c openssh-3.0p1J/clientloop.c --- openssh-3.0p1/clientloop.c Thu Oct 11 19:36:09 2001 +++ openssh-3.0p1J/clientloop.c Tue Nov 13 16:06:36 2001...

...and then exit, that is to say, it exits until sleep 50 secs. and when i use an infinite loop and make it run background, and then use exit to logout, ssh will still hang there. i debug the code, and found in channel_garbage_collect(channels.c), chan_is_dead is return 1 for c->isatate and c->ostate equals CHAN_INPUT_OPEN. so the channel remains open. Can someone help me check this problem. the script i use is just this: #! /sbin/sh while (( 1 )) do sleep 10 >/dev/null 2>&1 done -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email ------- You are receiving...

Hi! Our computer center is currently examining registered servers (offering services passing the firewall) using Nessus. Yesterday I had a ssh-connection closing on one host. Today I have seen serv01 155: channel 0: istate 4 != open channel 0: ostate 64 != open popping up, the connection survived however... In both cases the client host was not scanned but the server host (one was Linux, one was HP-UX). Any ideas what's going on? Lutz -- Lutz Jaenicke Lutz.Jaenicke at aet.TU-Cottbus.DE BTU Cottbus...

...amp;stderr_buffer, buf, strlen(buf)); +#endif quit_pending = 1; return; } diff -ur openssh-3.0.2p1/session.c openssh-3.0.2p1J2/session.c --- openssh-3.0.2p1/session.c Sat Dec 1 16:37:08 2001 +++ openssh-3.0.2p1J2/session.c Sat Jan 19 15:56:32 2002 @@ -1929,6 +1929,8 @@ */ if (c->ostate != CHAN_OUTPUT_CLOSED) chan_write_failed(c); + if (s->ttyfd != -1 && c->istate == CHAN_INPUT_OPEN) + chan_read_failed(c); s->chanid = -1; }

...-------- There is another not-so-serious problem. When I logged in this host from another host with 'ssh -X', some X applications get error. For example, nakaji at clare:nakaji$ echo $DISPLAY localhost:11.0 nakaji at clare:nakaji$ /usr/bin/X11/xterm channel 0: istate 8 != open channel 0: ostate 64 != open X connection to localhost:11.0 broken (explicit kill or server shutdown). And some other X applications do not. The difference between them is that the former (error) is preinstalled with this OS and it is X11R5, and the latter is installed with X11R6. Strange... Any hint? Thanks in ad...