Hi, We have upgraded the openssh 4.6P1 on Solaris 8 servers. After upgrade we get the below error message whenever we execute the remote commands using ssh. Please let me know what the fix is for this. Apr 8 03:03:43 dvsrv10 sshd[25379]: [ID 800047 auth.info] Accepted publickey for osteam from 10.0.93.31 port 35856 ssh2 Apr 8 03:03:50 dvsrv10 sshd[25381]: [ID 800047 auth.error] error: channel 0: chan_read_failed for istate 3 Apr 8 03:03:50 dvsrv10 last message repeated 1 time Apr 8 03:03:51 dvsrv10 sshd[25384]: [ID 800047 auth.info] Accepted publickey for osteam from 10.0.93.31 port 35857 ssh2 Apr 8 03:03:52 dvsrv10 sshd[25386]: [ID 800047 auth.error] error: channel 0: chan_read_failed for istate 3 Apr 8 03:03:52 dvsrv10 last message repeated 1 time Apr 8 03:03:52 dvsrv10 sshd[25389]: [ID 800047 auth.info] Accepted publickey for osteam from 10.0.93.31 port 35858 ssh2 Apr 8 03:03:53 dvsrv10 sshd[25391]: [ID 800047 auth.error] error: channel 0: chan_read_failed for istate 3 Apr 8 03:03:53 dvsrv10 last message repeated 1 time Apr 8 03:03:53 dvsrv10 sshd[25394]: [ID 800047 auth.info] Accepted publickey for osteam from 10.0.93.31 port 35859 ssh2 Apr 8 03:03:53 dvsrv10 sshd[25396]: [ID 800047 auth.error] error: channel 0: chan_read_failed for istate 3 Thanks, Sithesvaran Thirumaran Unix Administrator Internet Operations Unit Dubai Municipality Mobile: +971-50-5494352 Email: esquire_sithesvaran at dm.gov.ae <mailto:esquire_sithesvaran at dm.gov.ae> Our Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/
Hi, On Sun, Apr 08, 2007 at 12:01:38PM +0400, ESQUIRE Sithesvaran wrote:> We have upgraded the openssh 4.6P1 on Solaris 8 servers. After > upgrade we get the below error message whenever we execute the > remote commands using ssh. Please let me know what the fix is for > this.Please include debugging output, so the problem can be identified easier. Run sshd -ddd and ssh -vvv when connecting to get full debug output. Please also describe the problem as thorougly as possible. Do you know if the command actually does get executed, for example? //Peter
This sounds like the same error posted about by a coworker, in the thread here: <http://marc.info/?t=117469485700001&r=1&w=2> ... there is a patch in that thread, provided by Darren Tucker, that fixed the problem for us. -s- On Apr 8, 2007, at 1:01 AM, ESQUIRE Sithesvaran wrote:> Hi, > > > > We have upgraded the openssh 4.6P1 on Solaris 8 servers. After upgrade > we get the below error message whenever we execute the remote commands > using ssh. Please let me know what the fix is for this. > > > > Apr 8 03:03:43 dvsrv10 sshd[25379]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35856 ssh2 > > Apr 8 03:03:50 dvsrv10 sshd[25381]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > Apr 8 03:03:50 dvsrv10 last message repeated 1 time > > Apr 8 03:03:51 dvsrv10 sshd[25384]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35857 ssh2 > > Apr 8 03:03:52 dvsrv10 sshd[25386]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > Apr 8 03:03:52 dvsrv10 last message repeated 1 time > > Apr 8 03:03:52 dvsrv10 sshd[25389]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35858 ssh2 > > Apr 8 03:03:53 dvsrv10 sshd[25391]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > Apr 8 03:03:53 dvsrv10 last message repeated 1 time > > Apr 8 03:03:53 dvsrv10 sshd[25394]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35859 ssh2 > > Apr 8 03:03:53 dvsrv10 sshd[25396]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > > > Thanks, > > Sithesvaran Thirumaran > Unix Administrator > Internet Operations Unit > Dubai Municipality > Mobile: +971-50-5494352 > Email: esquire_sithesvaran at dm.gov.ae > <mailto:esquire_sithesvaran at dm.gov.ae> > > > > > Our Vision > To create an excellent city that provides the essence of success > and comfort of living. > > Disclaimer: > This Electronic Mail and any files transmitted with it are > confidential > and intended solely for the use of the individual or entity to > whom they > are addressed. If you are not an addressee, or have received the > message > by error, please notify the sender via E-Mail or over the > telephone and > delete this e-mail. You are not authorized to read, copy, > disseminate, > distribute or use this E-Mail or any of its attachment in any > way. Any > views or opinions presented in this email are solely those of the > author > and do not necessarily represent Dubai Municipality. The recipient > should > check this email and any attachments for the presence of viruses/ > worms. > Dubai Municipality accepts no liability for any damage caused > by any > virus/worms transmitted by this email. > > Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/ > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > http://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
Hi Sandor, I see the below solution for this issue. When I execute the below command, it is not giving command prompt after wards, it just keep running. Let me know which patch it reverts, what it does?> > I suspect this is related to the change for bug #52. You could try > > reverting the following patch ("patch -p1 -R") and see if the error > > messages stop. > > Yes, that eliminates the chan_read_failed error messages.Regds, Sithesvaran. -----Original Message----- From: Sandor W. Sklar [mailto:ssklar at stanford.edu] Sent: Sunday, April 08, 2007 9:29 PM To: ESQUIRE Sithesvaran Cc: OpenSSH Devel List Subject: Re: Error message after upgraing the openssh 4.6P1 This sounds like the same error posted about by a coworker, in the thread here: <http://marc.info/?t=117469485700001&r=1&w=2> ... there is a patch in that thread, provided by Darren Tucker, that fixed the problem for us. -s- On Apr 8, 2007, at 1:01 AM, ESQUIRE Sithesvaran wrote:> Hi, > > > > We have upgraded the openssh 4.6P1 on Solaris 8 servers. After upgrade > we get the below error message whenever we execute the remote commands > using ssh. Please let me know what the fix is for this. > > > > Apr 8 03:03:43 dvsrv10 sshd[25379]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35856 ssh2 > > Apr 8 03:03:50 dvsrv10 sshd[25381]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > Apr 8 03:03:50 dvsrv10 last message repeated 1 time > > Apr 8 03:03:51 dvsrv10 sshd[25384]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35857 ssh2 > > Apr 8 03:03:52 dvsrv10 sshd[25386]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > Apr 8 03:03:52 dvsrv10 last message repeated 1 time > > Apr 8 03:03:52 dvsrv10 sshd[25389]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35858 ssh2 > > Apr 8 03:03:53 dvsrv10 sshd[25391]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > Apr 8 03:03:53 dvsrv10 last message repeated 1 time > > Apr 8 03:03:53 dvsrv10 sshd[25394]: [ID 800047 auth.info] Accepted > publickey for osteam from 10.0.93.31 port 35859 ssh2 > > Apr 8 03:03:53 dvsrv10 sshd[25396]: [ID 800047 auth.error] error: > channel 0: chan_read_failed for istate 3 > > > > Thanks, > > Sithesvaran Thirumaran > Unix Administrator > Internet Operations Unit > Dubai Municipality > Mobile: +971-50-5494352 > Email: esquire_sithesvaran at dm.gov.ae > <mailto:esquire_sithesvaran at dm.gov.ae> > > > > > Our Vision > To create an excellent city that provides the essence of success > and comfort of living. > > Disclaimer: > This Electronic Mail and any files transmitted with it are > confidential > and intended solely for the use of the individual or entity to > whom they > are addressed. If you are not an addressee, or have received the > message > by error, please notify the sender via E-Mail or over the > telephone and > delete this e-mail. You are not authorized to read, copy, > disseminate, > distribute or use this E-Mail or any of its attachment in any > way. Any > views or opinions presented in this email are solely those of the > author > and do not necessarily represent Dubai Municipality. The recipient > should > check this email and any attachments for the presence of viruses/ > worms. > Dubai Municipality accepts no liability for any damage caused > by any > virus/worms transmitted by this email. > > Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/ > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > http://lists.mindrot.org/mailman/listinfo/openssh-unix-devOur Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/
Hi Darren, Thanks for your response. But really I don't understand you are talking about which patch file. Can you please explain me in detail? Thanks, Sithesvaran. -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tuesday, April 10, 2007 5:58 AM To: ESQUIRE Sithesvaran Cc: OpenSSH Devel List Subject: Re: Error message after upgraing the openssh 4.6P1 ESQUIRE Sithesvaran wrote:> Hi Sandor, > > I see the below solution for this issue. When I execute the below > command, it is not giving command prompt after wards, it just keep > running. Let me know which patch it reverts, what it does? > >>> I suspect this is related to the change for bug #52. You could try >>> reverting the following patch ("patch -p1 -R") and see if the error >>> messages stop. >> Yes, that eliminates the chan_read_failed error messages.You need to feed the patch file into patch's standard input. If you're using a mailer such as mutt you can just pipe it ("| patch -p1 -R"), however if you save the patch to a file you need to do redirect it in, eg "patch -p1 -R <patchfile". BTW since there are at least 2 threads about this, I have opened a bugzilla bug for this problem. I suggest that you (and anyone else interested) add themselves to the cc: list of the bug. http://bugzilla.mindrot.org/show_bug.cgi?id=1306 -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. Our Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/
Is it final fix or it is just workaround? Because I need to implement it in PROD environment. -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tuesday, April 10, 2007 5:58 AM To: ESQUIRE Sithesvaran Cc: OpenSSH Devel List Subject: Re: Error message after upgraing the openssh 4.6P1 ESQUIRE Sithesvaran wrote:> Hi Sandor, > > I see the below solution for this issue. When I execute the below > command, it is not giving command prompt after wards, it just keep > running. Let me know which patch it reverts, what it does? > >>> I suspect this is related to the change for bug #52. You could try >>> reverting the following patch ("patch -p1 -R") and see if the error >>> messages stop. >> Yes, that eliminates the chan_read_failed error messages.You need to feed the patch file into patch's standard input. If you're using a mailer such as mutt you can just pipe it ("| patch -p1 -R"), however if you save the patch to a file you need to do redirect it in, eg "patch -p1 -R <patchfile". BTW since there are at least 2 threads about this, I have opened a bugzilla bug for this problem. I suggest that you (and anyone else interested) add themselves to the cc: list of the bug. http://bugzilla.mindrot.org/show_bug.cgi?id=1306 -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. Our Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/
On Tue, Apr 10, 2007 at 12:45:46PM +0400, ESQUIRE Sithesvaran wrote:> Is it final fix or it is just workaround? Because I need to implement it > in PROD environment.I would consider the patch in the previous mail to be experimental. For production use , the safest thing to do would be to revert the change. The attached patch is against 4.6p1 and does that. To use, save the attachment to /tmp, change to a freshly unpacked openssh-4.6p1 directory, do "patch -p0 </tmp/openssh-4.6p1-chan_read_failed.patch" and then rebuild. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. -------------- next part -------------- Index: channels.c ==================================================================RCS file: /usr/local/src/security/openssh/cvs/openssh/channels.c,v retrieving revision 1.251 diff -u -p -r1.251 channels.c --- channels.c 28 Jan 2007 23:16:28 -0000 1.251 +++ channels.c 10 Apr 2007 08:58:39 -0000 @@ -1449,11 +1449,10 @@ channel_handle_rfd(Channel *c, fd_set *r int len; if (c->rfd != -1 && - (c->detach_close || FD_ISSET(c->rfd, readset))) { + FD_ISSET(c->rfd, readset)) { errno = 0; len = read(c->rfd, buf, sizeof(buf)); - if (len < 0 && (errno == EINTR || - (errno == EAGAIN && !(c->isatty && c->detach_close)))) + if (len < 0 && (errno == EINTR || errno == EAGAIN)) return 1; #ifndef PTY_ZEROREAD if (len <= 0) { @@ -1605,12 +1604,11 @@ channel_handle_efd(Channel *c, fd_set *r c->local_consumed += len; } } else if (c->extended_usage == CHAN_EXTENDED_READ && - (c->detach_close || FD_ISSET(c->efd, readset))) { + FD_ISSET(c->efd, readset)) { len = read(c->efd, buf, sizeof(buf)); debug2("channel %d: read %d from efd %d", c->self, len, c->efd); - if (len < 0 && (errno == EINTR || - (errno == EAGAIN && !c->detach_close))) + if (len < 0 && (errno == EINTR || errno == EAGAIN)) return 1; if (len <= 0) { debug2("channel %d: closing read-efd %d", Index: serverloop.c ==================================================================RCS file: /usr/local/src/security/openssh/cvs/openssh/serverloop.c,v retrieving revision 1.151 diff -u -p -r1.151 serverloop.c --- serverloop.c 28 Jan 2007 23:16:28 -0000 1.151 +++ serverloop.c 10 Apr 2007 08:58:39 -0000 @@ -280,7 +280,6 @@ wait_until_can_do_something(fd_set **rea struct timeval tv, *tvp; int ret; int client_alive_scheduled = 0; - int program_alive_scheduled = 0; /* * if using client_alive, set the max timeout accordingly, @@ -318,7 +317,6 @@ wait_until_can_do_something(fd_set **rea * the client, try to get some more data from the program. */ if (packet_not_very_much_data_to_write()) { - program_alive_scheduled = child_terminated; if (!fdout_eof) FD_SET(fdout, *readsetp); if (!fderr_eof) @@ -364,16 +362,8 @@ wait_until_can_do_something(fd_set **rea memset(*writesetp, 0, *nallocp); if (errno != EINTR) error("select: %.100s", strerror(errno)); - } else { - if (ret == 0 && client_alive_scheduled) - client_alive_check(); - if (!compat20 && program_alive_scheduled && fdin_is_tty) { - if (!fdout_eof) - FD_SET(fdout, *readsetp); - if (!fderr_eof) - FD_SET(fderr, *readsetp); - } - } + } else if (ret == 0 && client_alive_scheduled) + client_alive_check(); notify_done(*readsetp); } @@ -417,8 +407,7 @@ process_input(fd_set *readset) if (!fdout_eof && FD_ISSET(fdout, readset)) { errno = 0; len = read(fdout, buf, sizeof(buf)); - if (len < 0 && (errno == EINTR || - (errno == EAGAIN && !child_terminated))) { + if (len < 0 && (errno == EINTR || errno == EAGAIN)) { /* do nothing */ #ifndef PTY_ZEROREAD } else if (len <= 0) { @@ -436,8 +425,7 @@ process_input(fd_set *readset) if (!fderr_eof && FD_ISSET(fderr, readset)) { errno = 0; len = read(fderr, buf, sizeof(buf)); - if (len < 0 && (errno == EINTR || - (errno == EAGAIN && !child_terminated))) { + if (len < 0 && (errno == EINTR || errno == EAGAIN)) { /* do nothing */ #ifndef PTY_ZEROREAD } else if (len <= 0) {
Shall I use this attached patch for production? -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tuesday, April 10, 2007 1:22 PM To: ESQUIRE Sithesvaran Cc: OpenSSH Devel List Subject: Re: Error message after upgraing the openssh 4.6P1 On Tue, Apr 10, 2007 at 12:45:46PM +0400, ESQUIRE Sithesvaran wrote:> Is it final fix or it is just workaround? Because I need to implementit> in PROD environment.I would consider the patch in the previous mail to be experimental. For production use , the safest thing to do would be to revert the change. The attached patch is against 4.6p1 and does that. To use, save the attachment to /tmp, change to a freshly unpacked openssh-4.6p1 directory, do "patch -p0 </tmp/openssh-4.6p1-chan_read_failed.patch" and then rebuild. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. Our Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/
ESQUIRE Sithesvaran wrote:> Shall I use this attached patch for production?Yes, unless the hang-on-exit bug (#52) is/was a killer for you. If 4.5 and below worked for you then the safest thing to do at this time is apply the patch in my previous mail (openssh-4.6p1-chan_read_failed.patch). -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
Yes. We were using openssh 3.5P1 and it was working fine without any issue. So for my servers, it is better to apply the patch u have given in your previous mail. -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tuesday, April 10, 2007 1:33 PM To: ESQUIRE Sithesvaran Cc: OpenSSH Devel List Subject: Re: Error message after upgraing the openssh 4.6P1 ESQUIRE Sithesvaran wrote:> Shall I use this attached patch for production?Yes, unless the hang-on-exit bug (#52) is/was a killer for you. If 4.5 and below worked for you then the safest thing to do at this time is apply the patch in my previous mail (openssh-4.6p1-chan_read_failed.patch). -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. Our Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/
Hi Darren, I executed as per your below mail, it is asking for File to Patch: please let me know what I need to give there. Here is the screen shot. Please let me know if I am wrong anywhere. bexml20: /root/ssh_latest_packages#ls 112438-03 openssh-4.6p1-sol8-sparc-local 112438-03.zip openssl-0.9.8e-sol8-sparc-local libgcc-3.4.6-sol8-sparc-local zlib-1.2.3-sol8-sparc-local bexml20: /root/ssh_latest_packages#ls /tmp/open* /tmp/openssh-4.6p1-chan_read_failed.patch bexml20: /root/ssh_latest_packages#patch -p0 </tmp/openssh-4.6p1-chan_read_failed.patch Looks like a unified context diff. File to patch: Thanks, Sithesvaran. -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tuesday, April 10, 2007 1:22 PM To: ESQUIRE Sithesvaran Cc: OpenSSH Devel List Subject: Re: Error message after upgraing the openssh 4.6P1 On Tue, Apr 10, 2007 at 12:45:46PM +0400, ESQUIRE Sithesvaran wrote:> Is it final fix or it is just workaround? Because I need to implementit> in PROD environment.I would consider the patch in the previous mail to be experimental. For production use , the safest thing to do would be to revert the change. The attached patch is against 4.6p1 and does that. To use, save the attachment to /tmp, change to a freshly unpacked openssh-4.6p1 directory, do "patch -p0 </tmp/openssh-4.6p1-chan_read_failed.patch" and then rebuild. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. Our Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/
Yes. I got it from Sun Freeware. Is there any fix for these packages? Or should I use only source files and build. Then why they have kept these packages for downloading? Thanks, -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Wednesday, April 11, 2007 2:36 PM To: ESQUIRE Sithesvaran Cc: OpenSSH Devel List Subject: Re: Error message after upgraing the openssh 4.6P1 ESQUIRE Sithesvaran wrote:> I executed as per your below mail, it is asking for File to Patch:> please let me know what I need to give there. Here is the screen shot.> Please let me know if I am wrong anywhere.Those look like binary packages from sunfreeware or similar, and you can't patch those. You need to either build from the source[1] or ask whoever built your packages to apply the patch and rebuild. [1] eg from ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/ -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement Our Vision To create an excellent city that provides the essence of success and comfort of living. Disclaimer: This Electronic Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, or have received the message by error, please notify the sender via E-Mail or over the telephone and delete this e-mail. You are not authorized to read, copy, disseminate, distribute or use this E-Mail or any of its attachment in any way. Any views or opinions presented in this email are solely those of the author and do not necessarily represent Dubai Municipality. The recipient should check this email and any attachments for the presence of viruses/worms. Dubai Municipality accepts no liability for any damage caused by any virus/worms transmitted by this email. Dubai Municipality, Dubai, UAE, http://www.dm.gov.ae/