Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Chet Ramey <chet.ramey@case.edu>
Newsgroups: gnu.bash.bug
Subject: Re: Feature Request re: syslog and bashhist
Date: Wed, 12 Aug 2015 09:19:54 -0400
Lines: 20
Approved: bug-bash@gnu.org
Message-ID: <mailman.8198.1439385607.904.bug-bash@gnu.org>
References: <55C78FC8.1050609@gmail.com> <55C9073C.3030203@case.edu> <mailman.8184.1439375524.904.bug-bash@gnu.org> <mqfd1l$flc$1@dont-email.me>
Reply-To: chet.ramey@case.edu
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Trace: usenet.stanford.edu 1439385607 9597 208.118.235.17 (12 Aug 2015 13:20:07 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: chet.ramey@case.edu
To: Aharon Robbins <arnold@skeeve.com>, bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
In-Reply-To: <mqfd1l$flc$1@dont-email.me>
X-Junkmail-Status: score=10/50, host=mpv5.cwru.edu
X-Junkmail-Whitelist: YES (by domain whitelist at mpv1.tis.cwru.edu)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic]
X-Received-From: 129.22.105.36
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.14
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: <http://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>
Xref: csiph.com gnu.bash.bug:11331

On 8/12/15 8:09 AM, Aharon Robbins wrote:
> In article <mailman.8184.1439375524.904.bug-bash@gnu.org>,
> aixtools  <aixtools@gmail.com> wrote:
>> In short, having it included in ./configure simply give it much more 
>> visibility - and perhaps adoption.
> 
> Personally, I think that having bash send executed commands to syslog
> is an invasion of privacy; I'm surprised such a feature is even there
> at all...

And this is why it's not easy to turn on.  It's there for that small
set of system administrators who need it to satisfy some external
auditing requirement (in some cases legally required) -- that's why it's
available in the first place.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/