The .bash_history that Never Heard Anything at All

Andrew "Tuna" Harris tuna at supertunaman.com
Sun Apr 26 19:22:26 MST 2009


Excerpts from phrkonaleash's message of Sun Apr 26 17:57:55 -0700 2009:
> On Sun, Apr 26, 2009 at 6:56 AM, Andrew "Tuna" Harris <tuna at supertunaman.com
> > wrote:
> 
> > Top-posting 'cuz you did
> >
> > The .bash_profile thing works beautifully, except I found that I had to
> > add it to .bashrc for it to work with my aterms and xterms too. Thanks!
> >
> 
> So, now about that ascii art pr0n you promised me...
> 
>  ./pr0n.sh was it?
>

No, it's elinks http://asciipr0n.com #nsfw

> >
> > Excerpts from Lisa Kachold's message of Sun Apr 26 05:27:52 -0700 2009:
> > > Hey SuperTunaMan,
> > >
> > > By default, all commands you type in are stored in the history. You can
> > pick
> > > and chose the commands you want to store by putting the option
> > >
> > > export HISTCONTROL=ignorespace
> > >
> > > in your ~/.bash_profile file. This will *make sure that bash dont store
> > any
> > > command beginning with the space character*. So if you want bash to
> > forget
> > > that you typed in ls, just type in  ls(<space>ls).
> > >
> > > As far as I know, command substitution [backtics] and sub-command setup
> > also
> > > can be torqued (and cause a nice Snort IDS alert) to do this nicely:
> > >
> > http://www.linuxtopia.org/online_books/advanced_bash_scripting_guide/commandsub
> > .
> > > html
> > >
> > > Custom variables are available for bash HIST:
> > > http://sock-raw.org/papers/bash_history
> > >
> > > Or a separate logfile for each term:
> > >
> > http://www.ducea.com/2006/05/15/linux-tips-take-control-of-your-bash_history/
> > >
> > > I also suggest a keylogger:
> > >
> > http://www2.packetstormsecurity.org/cgi-bin/search/search.cgi?searchvalue=linux+
> > > bash+keyloggers&type=archives&[search].x=0&[search].y=0
> > >
> > >
> > > On Sun, Apr 26, 2009 at 4:44 AM, Andrew "Tuna" Harris <
> > tuna at supertunaman.com
> > > > wrote:
> > >
> > > > Herroes
> > > >
> > > > There are some seekrit things that I would rather not have my
> > > > .bash_history knowing. Is there a way to set rules that prevent
> > commands
> > > > containing a certain word like, say, "angry_watermelon" from being
> > stored?
> > > >
> > > > Also, are things that are sent to standard out logged anywhere?
> > > > ---------------------------------------------------
> > > > PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> > > > To subscribe, unsubscribe, or to change your mail settings:
> > > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> > > >
> > >
> > ---------------------------------------------------
> > PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> 


More information about the PLUG-discuss mailing list