Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 11 Sep 2001 11:19:46 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Virus Found Message-ID: <20010911111946.A1285@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <20010911004146 DOT H937 AT cygbert DOT vinschen DOT de> <8F23E55D511AD5119A6800D0B76FDDE101A26A59 AT cpex3 DOT channelpoint DOT com> <20010911004146 DOT H937 AT cygbert DOT vinschen DOT de> <59jqpt4f25eochmtlslvv9nodngnkeeo3d AT 4ax DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010911020929 DOT 00ac0fc0 AT imap DOT local DOT mscha DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.2.20010911020929.00ac0fc0@imap.local.mscha.com>; from cygwin@mscha.com on Tue, Sep 11, 2001 at 02:10:00AM +0200 On Tue, Sep 11, 2001 at 02:10:00AM +0200, Michael Schaap wrote: > At 01:36 11-9-2001, Mark Gordon wrote: > > >On Mon, Sep 10, 2001 at 04:27:40PM -0600, Troy Noble wrote: > > >> Hah! That's good. > > >> > > >> And I also saw Chuck's note about scp working... so maybe it's a > > non-issue. > > > > > >But that's not quite true. This was a long discussed topic on > > >the openssh-usinx-dev mailing list about the unluck interference > > >of profile output and scp... Hrm, it's some months ago, I > > >wonder if it's solved somehow and I didn't pay attention... > > > >I was recently (within the past few weeks) having problems with scp > >due to this, so it is still a potential problem with some systems. > > > >If people are seriously interested I can investigate this further. It > >may be that one of the systems involved has an old version of ssh > >causing the problem. > > I don't think this should be a problem - /etc/profile is only called for > login shells. Eventually I figured that out. The problem is ~/.bashrc. If your login shell is bash and bash has been started by rshd/sshd, it executes ~/.bashrc. So the rule is, no output in ~/.bashrc. And, IIRC, the same rule applies for tcsh and ~/.cshrc. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/