Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42C4BD5E.6000002@byu.net> Date: Thu, 30 Jun 2005 21:49:50 -0600 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Tom Rodman CC: Cygwin List Subject: Re: ssh localhost date # no startup files read: ~/{.bash_profile,.bash_login,.profile,.bashrc} References: <200506072010.j57KAKea003183@tigris.pounder.sol.net> <6.2.1.2.0.20050607192758.07159500@pop.prospeed.net> <200506101305.j5AD5DSq021970@tigris.pounder.sol.net> In-Reply-To: <200506101305.j5AD5DSq021970@tigris.pounder.sol.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Tom Rodman on 6/10/2005 7:05 AM: > Below are two tests cases for "ssh localhost date". The Linux > test shows that ~/.bashrc is read. The Cygwin case shows none of > ~/{.bash_profile,.bash_login,.profile,.bashrc} are read. Doesn't this > seem like a bug? Not so much a bug, as a lack of configuration. According to the upstream maintainer, bash has to be specially compiled to enable rshd snooping: http://lists.gnu.org/archive/html/bug-bash/2005-06/msg00042.html. And as the cygwin bash maintainer, I haven't yet tried to turn it on. If I can ever narrow down the heap corruption in bash-3.0-2, I will release 3.0-3 linked against libreadline and with SSH_SOURCE_BASHRC on. - -- Life is short - so eat dessert first! Eric Blake ebb9@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCxL1d84KuGfSFAYARAhbFAKDKMR+EJo+3r8UlySzszqwEFCMz4QCghVvu b658Pyp1xtH4JVrNIU3dWbM= =WrD8 -----END PGP SIGNATURE----- -- 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/