X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: FW: Potential bug in sshd Date: Wed, 27 Sep 2006 12:20:45 +0100 Message-ID: <009601c6e226$fa22d820$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I was sent the following mail off-list, and am forwarding it (with permission), because it contains a useful workaround for people having problems with McAffee: disable the "buffer overrun protection". On 27 September 2006 11:40, Michael Teske wrote: > Hi! > > I'm not subscribed to the cygwin mailing list but found your message in > http://www.mail-archive.com/cygwin AT cygwin DOT com/msg72341.html > while searching "linked dll data write copy failed" on google. I just > wanted to report a similar problem, that happens if sshd runs together > with McAffee virus checker. Somehow then sshd has the same problems - > only after reboot, not if restarted later. The problems vanish if one > disables the "buffer overrun protection". > My suspicion is that this happens because sshd is started before the > McAffee service and thus McAffee gets confused. Unfortunately there's no > way to determine the starting order of services... > > Greetings, > Michael Not being a McAffee user[*], (and not often running a sshd on my own box), I haven't been able to test this, but it seems worth trying for anyone who's having sshd problems that might be related. cheers, DaveK [*] - to put it mildly! -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/