<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ClearNet Security: Tag bash</title>
    <link>http://blog.clearnetsec.com/articles/tag/bash</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>quick tip:  bash 3.x supports timestamps in history entries</title>
      <description>&lt;p&gt;
This is worth the extra effort -- ensuring you have bash 3.x installed (3.2 is the current version).  It enables you to set an environment variable to record the time and date of executed commands.
&lt;/p&gt;

&lt;blockquote&gt;
$ export HISTTIMEFORMAT="%h/%m - %H:%M:%S "&lt;br /&gt;
&lt;br /&gt;
$ history | tail -2&lt;br /&gt;
 1006  Jan/01 - 19:24:02 ls&lt;br /&gt;
 1007  Jan/01 - 19:24:07 history | tail -2&lt;br /&gt;
&lt;/blockquote&gt;
&lt;p&gt;
A potential forensic treasure when needed.
&lt;/p&gt;

</description>
      <pubDate>Tue, 30 Jan 2007 19:07:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:281f10c5-11d4-40f8-9eac-20e756a38b8c</guid>
      <author>tate@ClearNetSec.com (Tate Hansen)</author>
      <link>http://blog.clearnetsec.com/articles/2007/01/30/quick-tip-bash-3-x-supports-timestamps-in-history-entries</link>
      <category>ClearNet</category>
      <category>ClearNet Security</category>
      <category>Tate Hansen</category>
      <category>bash</category>
      <category>history</category>
      <category>timestamps</category>
    </item>
  </channel>
</rss>
