Difference between pages "How to intercept ATA commands using AoE" and "Google Chrome"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
m (Client configuration)
 
(Disk Cache)
 
Line 1: Line 1:
ATA over Ethernet (''AoE'') is a network protocol designed for accessing ATA storage devices over Ethernet networks.
+
Google Chrome is a [[Web Browser|web browser]] developed by Google Inc.
  
This "How To" explains the process of using ATA over Ethernet protocol to intercept ATA commands from a Linux system (called Linux client) using [[Wireshark]] for diagnostic and testing purposes.
+
== Configuration ==
 +
The Google Chrome configuration can be found in the '''Preferences''' file.
  
== Linux server - Linux client configuration ==
+
On Linux
 +
<pre>
 +
/home/$USER/.config/google-chrome/Default/Preferences
 +
</pre>
  
First, make sure that Linux server and Linux client are connected to the same network and can exchange packets with each other.
+
On MacOS-X
 +
<pre>
 +
/Users/$USER/Library/Application Support/Google/Chrome/Default/Preferences
 +
</pre>
  
=== Server configuration ===
+
On Windows XP
 +
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default\Preferences
 +
</pre>
  
Make sure that your server has [http://packages.debian.org/en/lenny/vblade ''vblade''] tool installed. Then run the following command:
+
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Preferences
 +
</pre>
  
# vblade 0 0 eth0 /dev/sda
+
Or for '''Chromium'''
  
Where:
+
On Linux
* eth0 - your network interface;
+
<pre>
* /dev/sda - a block device you want to be accessible through a network.
+
/home/$USER/.config/chromium/Default/Preferences
 +
</pre>
  
=== Client configuration ===
+
On MacOS-X
 +
<pre>
 +
/Users/$USER/Library/Application Support/Chromium/Default/Preferences
 +
</pre>
  
Make sure that your Linux client has [http://packages.debian.org/en/lenny/aoetools ''aoe tools''] installed. Then run the following command:
+
On Windows XP
 +
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Default\Preferences
 +
</pre>
  
# modprobe aoe
+
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Chromium\User Data\Default\Preferences
 +
</pre>
  
Make sure your vblade device is available on the client by running:
+
=== Plugins ===
  
# aoe-stat
+
Information about plugins can be found under the "plugins section" of the Preferences file.
  
The following block devices would be available:
+
=== DNS Prefetching ===
  
* /dev/etherd/e0.0 - the whole disk (corresponds to /dev/sda on the server);
+
DNS is prefetched for related sites, e.g. links on the page.
* /dev/etherd/e0.0p1 - first partition on the disk (corresponds to /dev/sda1 on the server);
+
This behavior is controlled by the setting "Predict network actions to improve page load performance", which is enabled by default.
* /dev/etherd/e0.0p2 - second partition on the disk (corresponds to /dev/sda2 on the server);
+
* etc.
+
  
== Intercepting ATA commands ==
+
If enabled the Preferences file contains:
 +
<pre>
 +
  "dns_prefetching": {
 +
      "enabled": true,
 +
</pre>
  
Launch [[Wireshark]] on a client and start a capture on ''eth0''. You can apply the following display filter to analyse AoE packets only:
+
If disabled the Preferences file contains:
 +
<pre>
 +
  "dns_prefetching": {
 +
      "enabled": false,
 +
</pre>
  
eth.type == 0x88a2
+
== Start-up DNS queries ==
  
Here is a screenshot of [[grml]] client running in VirtualBox:
+
When Chrome starts it queries for several non-existing hostnames that consists of a 10 random characters, E.g.
 +
<pre>
 +
ttrgoiknff.mydomain.com
 +
bxjhgftsyu.mydomain.com
 +
yokjbjiagd.mydomain.com
 +
</pre>
  
[[Image:Ataoe.png|thumb|none|Using [[grml]] to capture ATA commands]]
+
This is used to determine if your ISP is hijacking NXDOMAIN results [http://www.google.com/support/forum/p/Chrome/thread?tid=3511015c72a7b314&hl=en].
 +
 
 +
== Disk Cache ==
 +
Google Chrome uses multiple caches, from [http://src.chromium.org/viewvc/chrome/trunk/src/net/base/cache_type.h?view=markup]:
 +
<pre>
 +
// The types of caches that can be created.
 +
enum CacheType {
 +
    DISK_CACHE,  // Disk is used as the backing storage.
 +
    MEMORY_CACHE,  // Data is stored only in memory.
 +
    MEDIA_CACHE,  // Optimized to handle media files.
 +
    APP_CACHE,  // Backing store for an AppCache.
 +
    SHADER_CACHE, // Backing store for the GL shader cache.
 +
    PNACL_CACHE, // Backing store the PNaCl translation cache
 +
};
 +
</pre>
 +
 
 +
The Google Chrome disk cache can be found in:
 +
 
 +
On Linux
 +
 
 +
<pre>
 +
/home/$USER/.cache/chromium/Default/Cache/
 +
/home/$USER/.cache/google-chrome/Default/Cache/
 +
/home/$USER/.config/chromium/Default/Cache/
 +
/home/$USER/.config/google-chrome/Default/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.cache/chromium/Default/Media Cache/
 +
/home/$USER/.cache/google-chrome/Default/Media Cache/
 +
/home/$USER/.config/chromium/Default/Media Cache/
 +
/home/$USER/.config/google-chrome/Default/Media Cache/
 +
</pre>
 +
 
 +
 
 +
<pre>
 +
/home/$USER/.config/chromium/Default/Application Cache/Cache/
 +
/home/$USER/.config/google-chrome/Default/Application Cache/Cache/
 +
</pre>
 +
 
 +
 
 +
<pre>
 +
/home/$USER/.config/chromium/Default/GPUCache/
 +
/home/$USER/.config/google-chrome/Default/GPUCache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.cache/chromium/PnaclTranslationCache/
 +
/home/$USER/.cache/google-chrome/PnaclTranslationCache/
 +
</pre>
 +
 
 +
On MacOS-X
 +
<pre>
 +
/Users/$USER/Caches/Chromium/Default/Cache/
 +
/Users/$USER/Caches/Google/Chrome/Default/Cache/
 +
</pre>
 +
 
 +
On Windows XP
 +
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Cache\
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Cache\
 +
</pre>
 +
 
 +
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\Default\Cache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Cache\
 +
</pre>
 +
 
 +
The Chrome Cache contains different files with the following file names:
 +
* index
 +
* data_#; where # contains a decimal digit.
 +
* f_######; where # contains a hexadecimal digit.
 +
 
 +
For more info see Chrome developers site [http://www.chromium.org/developers/design-documents/network-stack/disk-cache].
 +
 
 +
== History ==
 +
Chrome stores the history of visited sites in a file named '''History'''. This file uses the [[SQLite database format]].
 +
 
 +
The '''History''' file can be found in same location as the '''Preferences''' file.
 +
 
 +
There is also '''Archived History''' that predates information in the '''History''' file.
 +
Note that the '''Archived History''' only contains visits.
 +
 
 +
=== Timestamps ===
 +
The '''History''' file uses the different timestamps.
 +
 
 +
==== visits.visit_time ====
 +
 
 +
The '''visits.visit_time''' is in (the number of) microseconds since January 1, 1601 UTC
 +
 
 +
Some Python code to do the conversion into human readable format:
 +
<pre>
 +
date_string = datetime.datetime( 1601, 1, 1 )
 +
            + datetime.timedelta( microseconds=timestamp )
 +
</pre>
 +
 
 +
Note that this timestamp is not the same as a Windows filetime which is (the number of) 100 nanoseconds since January 1, 1601 UTC
 +
 
 +
==== downloads.start_time ====
 +
 
 +
The '''downloads.start_time''' is in (the number of) seconds since January 1, 1970 UTC
 +
 
 +
Some Python code to do the conversion into human readable format:
 +
<pre>
 +
date_string = datetime.datetime( 1970, 1, 1 )
 +
            + datetime.timedelta( seconds=timestamp )
 +
</pre>
 +
 
 +
=== Example queries ===
 +
Some example queries:
 +
 
 +
To get an overview of the visited sites:
 +
<pre>
 +
SELECT datetime(((visits.visit_time/1000000)-11644473600), "unixepoch"), urls.url, urls.title FROM urls, visits WHERE urls.id = visits.url;
 +
</pre>
 +
 
 +
Note that the visit_time conversion looses precision.
 +
 
 +
To get an overview of the downloaded files:
 +
<pre>
 +
SELECT datetime(downloads.start_time, "unixepoch"), downloads.url, downloads.full_path, downloads.received_bytes, downloads.total_bytes FROM downloads;
 +
</pre>
 +
 
 +
How the information of the downloaded files is stored in the database can vary per version of Chrome as of version 26:
 +
<pre>
 +
SELECT datetime(((downloads.start_time/1000000)-11644473600), "unixepoch"), downloads.target_path, downloads_url_chains.url, downloads.received_bytes, downloads.total_bytes \
 +
FROM downloads, downloads_url_chains WHERE downloads.id = downloads_url_chains.id;
 +
</pre>
 +
 
 +
== See Also ==
 +
 
 +
* [[SQLite database format]]
  
 
== External Links ==
 
== External Links ==
 +
* [http://en.wikipedia.org/wiki/Google_Chrome Wikipedia article on Google Chrome]
 +
* [http://www.chromium.org/user-experience/user-data-directory The Chromium Projects - User Data Directory]
 +
* [http://www.chromium.org/developers/design-documents/network-stack/disk-cache Chrome Disk Cache]
 +
* [http://www.google.com/support/forum/p/Chrome/thread?tid=3511015c72a7b314&hl=en Chrome support forum article random 10 character hostnames on startup]
 +
* [http://www.useragentstring.com/pages/Chrome/ Chrome User Agent strings]
 +
* [http://computer-forensics.sans.org/blog/2010/01/21/google-chrome-forensics/ Google Chrome Forensics] by [[Kristinn Guðjónsson]], January 21, 2010
 +
* [http://linuxsleuthing.blogspot.ch/2013/02/cashing-in-on-google-chrome-cache.html?m=1 Cashing in on the Google Chrome Cache], [[John Lehr]], February 24, 2013
 +
* [http://www.obsidianforensics.com/blog/history-index-files-removed-from-chrome/ History Index files removed from Chrome v30], by Ryan Benson, October 2, 2013
 +
* [https://hindsight-internet-history.googlecode.com/files/Evolution_of_Chrome_Databases.png Evolution of Chrome Databases], by Ryan Benson, November 12, 2013
  
* [http://buffalo.nas-central.org/index.php/Vblade_-_ATA_over_Ethernet Vblade - ATA over Ethernet]
+
== Tools ==
 +
=== Open Source ===
 +
* [https://code.google.com/p/hindsight-internet-history/ hindsight-internet-history]
  
[[Category:Howtos]]
+
[[Category:Applications]]
 +
[[Category:Web Browsers]]

Revision as of 03:50, 30 April 2014

Google Chrome is a web browser developed by Google Inc.

Configuration

The Google Chrome configuration can be found in the Preferences file.

On Linux

/home/$USER/.config/google-chrome/Default/Preferences

On MacOS-X

/Users/$USER/Library/Application Support/Google/Chrome/Default/Preferences

On Windows XP

C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default\Preferences

On Windows Vista and later

C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Preferences

Or for Chromium

On Linux

/home/$USER/.config/chromium/Default/Preferences

On MacOS-X

/Users/$USER/Library/Application Support/Chromium/Default/Preferences

On Windows XP

C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Default\Preferences

On Windows Vista and later

C:\Users\%USERNAME%\AppData\Local\Chromium\User Data\Default\Preferences

Plugins

Information about plugins can be found under the "plugins section" of the Preferences file.

DNS Prefetching

DNS is prefetched for related sites, e.g. links on the page. This behavior is controlled by the setting "Predict network actions to improve page load performance", which is enabled by default.

If enabled the Preferences file contains:

   "dns_prefetching": {
      "enabled": true,

If disabled the Preferences file contains:

   "dns_prefetching": {
      "enabled": false,

Start-up DNS queries

When Chrome starts it queries for several non-existing hostnames that consists of a 10 random characters, E.g.

ttrgoiknff.mydomain.com
bxjhgftsyu.mydomain.com
yokjbjiagd.mydomain.com

This is used to determine if your ISP is hijacking NXDOMAIN results [1].

Disk Cache

Google Chrome uses multiple caches, from [2]:

// The types of caches that can be created.
enum CacheType {
    DISK_CACHE,  // Disk is used as the backing storage.
    MEMORY_CACHE,  // Data is stored only in memory.
    MEDIA_CACHE,  // Optimized to handle media files.
    APP_CACHE,  // Backing store for an AppCache.
    SHADER_CACHE, // Backing store for the GL shader cache.
    PNACL_CACHE, // Backing store the PNaCl translation cache
};

The Google Chrome disk cache can be found in:

On Linux

/home/$USER/.cache/chromium/Default/Cache/
/home/$USER/.cache/google-chrome/Default/Cache/
/home/$USER/.config/chromium/Default/Cache/
/home/$USER/.config/google-chrome/Default/Cache/
/home/$USER/.cache/chromium/Default/Media Cache/
/home/$USER/.cache/google-chrome/Default/Media Cache/
/home/$USER/.config/chromium/Default/Media Cache/
/home/$USER/.config/google-chrome/Default/Media Cache/


/home/$USER/.config/chromium/Default/Application Cache/Cache/
/home/$USER/.config/google-chrome/Default/Application Cache/Cache/


/home/$USER/.config/chromium/Default/GPUCache/
/home/$USER/.config/google-chrome/Default/GPUCache/
/home/$USER/.cache/chromium/PnaclTranslationCache/
/home/$USER/.cache/google-chrome/PnaclTranslationCache/

On MacOS-X

/Users/$USER/Caches/Chromium/Default/Cache/
/Users/$USER/Caches/Google/Chrome/Default/Cache/

On Windows XP

C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Cache\
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Cache\

On Windows Vista and later

C:\Users\%USERNAME%\AppData\Local\Google\Chromium\Default\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Cache\

The Chrome Cache contains different files with the following file names:

  • index
  • data_#; where # contains a decimal digit.
  • f_######; where # contains a hexadecimal digit.

For more info see Chrome developers site [3].

History

Chrome stores the history of visited sites in a file named History. This file uses the SQLite database format.

The History file can be found in same location as the Preferences file.

There is also Archived History that predates information in the History file. Note that the Archived History only contains visits.

Timestamps

The History file uses the different timestamps.

visits.visit_time

The visits.visit_time is in (the number of) microseconds since January 1, 1601 UTC

Some Python code to do the conversion into human readable format:

date_string = datetime.datetime( 1601, 1, 1 )
            + datetime.timedelta( microseconds=timestamp )

Note that this timestamp is not the same as a Windows filetime which is (the number of) 100 nanoseconds since January 1, 1601 UTC

downloads.start_time

The downloads.start_time is in (the number of) seconds since January 1, 1970 UTC

Some Python code to do the conversion into human readable format:

date_string = datetime.datetime( 1970, 1, 1 )
            + datetime.timedelta( seconds=timestamp )

Example queries

Some example queries:

To get an overview of the visited sites:

SELECT datetime(((visits.visit_time/1000000)-11644473600), "unixepoch"), urls.url, urls.title FROM urls, visits WHERE urls.id = visits.url;

Note that the visit_time conversion looses precision.

To get an overview of the downloaded files:

SELECT datetime(downloads.start_time, "unixepoch"), downloads.url, downloads.full_path, downloads.received_bytes, downloads.total_bytes FROM downloads;

How the information of the downloaded files is stored in the database can vary per version of Chrome as of version 26:

SELECT datetime(((downloads.start_time/1000000)-11644473600), "unixepoch"), downloads.target_path, downloads_url_chains.url, downloads.received_bytes, downloads.total_bytes \
FROM downloads, downloads_url_chains WHERE downloads.id = downloads_url_chains.id;

See Also

External Links

Tools

Open Source