description: a file that stores the command line history in Unix and Unix-like operating systems
14 results
by Noah Gift and Jeremy M. Jones · 29 Jun 2009 · 603pp · 141,814 words
by Jacqueline Kazil · 4 Feb 2016
:45 00:07 00:35 00:08 09:49 23:47 00:29 09:49 09:49 09:49 09:49 . .. .CFUserTextEncoding .DS_Store .Trash .bash_history Applications Desktop Documents Downloads Library Movies Music Pictures Public We do not have a .bashrc file, so we will have to create one. If you
by Richard Petersen · 15 May 2015
slightly different syntax, described in its Man pages). Filename Function BASH Shell .profile Login initialization file .bashrc BASH shell configuration file .bash_logout Logout name .bash_history History file /etc/profile System login initialization file /etc/bash.bashrc System BASH shell configuration file /etc/profile.d Directory for specialized BASH shell configuration
by Raphaal Hertzog and Roland Mas · 24 Dec 2013 · 678pp · 159,840 words
timestamps of access to files) or running compromised programs by mistake. Retracing an attack scenario usually involves looking for everything that was modified and executed: .bash_history files often provide for a very interesting read; so does listing files that were recently created, modified or accessed; the strings command helps identifying programs
by Drew Neil · 2 May 2018 · 241pp · 43,252 words
by Stuart McClure, Joel Scambray and George Kurtz · 15 Feb 2001 · 260pp · 40,943 words
appear as well. ------------[SYN] (slot 1) pc6 => target3 [23] %&& #'$ANSI"!guest guest ls cd / ls cd /etc cat /etc/passwd more hosts.equiv more /root/.bash_history Like most powerful tools in the network administrator’s toolkit, this one was also subverted over the years to perform duties for malicious hackers. You
…
and repetition. For example, the Bourne again shell (/bin/bash) keeps a file in the user’s directory (including root’s in many cases) called .bash_history that maintains a list of the recently used commands. Usually as the last step before signing off, attackers will want to remove their entries. For
…
example, the .bash_history may look something like this: tail -f /var/log/messages vi chat-ppp0 kill -9 1521 logout < the attacker logs in and begins his work
…
feature of the shell by setting unset HISTFILE; unset SAVEHIST Additionally, an intruder may link .bash_history to /dev/null: [rumble]# ln -s /dev/null ~/.bash_history [rumble]# ls -l .bash_history lrwxrwxrwx 1 root root 9 Jul 26 22:59 .bash_history -> /dev/null Cleaning Countermeasure U Log It is important to write log file information to
by Peter Kovac · 10 Dec 2014 · 200pp · 54,897 words
by Michael Lewis · 30 Mar 2014 · 250pp · 87,722 words
by Heather Adkins, Betsy Beyer, Paul Blankinship, Ana Oprea, Piotr Lewandowski and Adam Stubblefield · 29 Mar 2020 · 1,380pp · 190,710 words
how an attacker could carry out each stage of an attack. For example, in the Credential Access stage, ATT&CK describes how a user’s .bash_history may contain accidentally typed passwords that an attacker could obtain by simply reading the file. The ATT&CK framework lays out hundreds (potentially thousands) of
by Geoff Cox and Alex McLean · 9 Nov 2012
script is run, it could cause damage to the user’s system.9 #!/usr/bin/perl sub relive {$command = shift;print `$command`;} $bash_history = $ENV{ HOME }."/.bash_history"; while(1){ open(HISTORY, $bash_history); while($moment = <HISTORY>){ relive($moment); } } 42 Chapter 2 As evident if it is run, the source code expresses both what it will
by Justin Schuh · 20 Nov 2006 · 2,054pp · 359,149 words
by Ken Kocienda · 3 Sep 2018 · 255pp · 76,834 words
by Bryan O'Sullivan, John Goerzen, Donald Stewart and Donald Bruce Stewart · 2 Dec 2008 · 1,065pp · 229,099 words
by Scott Patterson · 11 Jun 2012 · 356pp · 105,533 words