Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups: gnu.bash.bug
Subject: Re: First lines of examples/startup-files/bashrc
Date: Thu, 9 Apr 2020 08:27:14 -0400
Lines: 19
Approved: bug-bash@gnu.org
Message-ID: <mailman.402.1586435266.2644.bug-bash@gnu.org>
References: <20200408234241.84fa2643163cc7ec3aedc6ef@schrader-schulte.de> <CAOSMAuvsyHZ18kM6RaDfoCVynprvTkEbgtHsi9EX1JXcxs9rPg@mail.gmail.com> <20200409122714.GZ845@eeg.ccf.org>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1586435266 11192 209.51.188.17 (9 Apr 2020 12:27:46 GMT)
X-Complaints-To: action@cs.stanford.edu
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Mail-Followup-To: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <CAOSMAuvsyHZ18kM6RaDfoCVynprvTkEbgtHsi9EX1JXcxs9rPg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy]
X-Received-From: 139.137.100.1
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <20200409122714.GZ845@eeg.ccf.org>
X-Mailman-Original-References: <20200408234241.84fa2643163cc7ec3aedc6ef@schrader-schulte.de> <CAOSMAuvsyHZ18kM6RaDfoCVynprvTkEbgtHsi9EX1JXcxs9rPg@mail.gmail.com>
Xref: csiph.com gnu.bash.bug:16111

On Wed, Apr 08, 2020 at 04:46:19PM -0700, Eduardo Bustamante wrote:
> On Wed, Apr 8, 2020 at 2:42 PM Martin Schulte <gnu@schrader-schulte.de> wrote:
> (...)
> > But, as far as I understand, a non-interactive bash doesn't read
> > ~/.bashrc at all - so shouldn't we just omit them?
> 
> There are exceptions. One of them being SSH, see:
> https://git.savannah.gnu.org/cgit/bash.git/tree/shell.c?h=ea31c00845c858098d232bd014bf27b5a63a668b#n1095
> 
> > /* If we were run by sshd or we think we were run by rshd, execute
> > ~/.bashrc if we are a top-level shell. */

Another case would be someone setting BASH_ENV to force the file to be
dotted in by scripts.

Or, possibly, someone who drank the Oracle Kool-Aid and is using
su - someuser -c 'some command' to run stuff.  Which we all know is
utterly and completely terrible, and yet... people do it.