Difference between pages "Linux Logical Volume Manager (LVM)" and "Google Chrome"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Changing, since got no reply on the talk page)
 
(Disk Cache)
 
Line 1: Line 1:
{{expand}}
+
Google Chrome is a [[Web Browser|web browser]] developed by Google Inc.
  
The [[Linux]] Logical Volume Manager, is commonly abbreviated to LVM. Although LVM can used for other [http://en.wikipedia.org/wiki/Logical_Volume_Management Logical Volume Management] variants as well.
+
== Configuration ==
 +
The Google Chrome configuration can be found in the '''Preferences''' file.
  
Not all forensic tools have support for Linux Logical Volume Manager (LVM) volumes, but most modern Linux distributions do.
+
On Linux
 +
<pre>
 +
/home/$USER/.config/google-chrome/Default/Preferences
 +
</pre>
  
== Forensic analysis ==
+
On MacOS-X
The metadata area of a LVM Physical Volume can contain multiple versions of metadata section that contains the LVM Volume Group definitions, including a creation date and time value.
+
<pre>
 +
/Users/$USER/Library/Application Support/Google/Chrome/Default/Preferences
 +
</pre>
  
== Mounting an LVM ==
+
On Windows XP
=== Mounting an LVM from an image ===
+
If you have an image mount the LVM read-only on a loopback device (e.g. /dev/loop1) by:
+
 
<pre>
 
<pre>
sudo losetup -r -o $OFFSET /dev/loop1 image.raw
+
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default\Preferences
 
</pre>
 
</pre>
  
Note that the offset is in bytes.
+
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Preferences
 +
</pre>
 +
 
 +
Or for '''Chrome SxS''' (Chrome side-by-side)
  
If you need to write to the image, e.g. for recovery, use [[xmount]] to write the changes to a [[shadow file]] (or cachefile in xmount terminology).
 
 
<pre>
 
<pre>
sudo xmount --in dd --cache sda.shadow sda.raw image/
+
C:\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\User Data\Default\Preferences
 
</pre>
 
</pre>
  
You can then safely mount the LVM in read-write mode (just omit the -r in the previous losetup command).
+
Or for '''Chromium'''
  
To remove this mapping afterwards run:
+
On Linux
 
<pre>
 
<pre>
sudo losetup -d /dev/loop1
+
/home/$USER/.config/chromium/Default/Preferences
 
</pre>
 
</pre>
  
To scan for new physical volumes:
+
On MacOS-X
 
<pre>
 
<pre>
lvm pvscan
+
/Users/$USER/Library/Application Support/Chromium/Default/Preferences
 
</pre>
 
</pre>
  
You cannot unmount an active volume group. To detach (or deactivate) the volume group:
+
On Windows XP
 
<pre>
 
<pre>
vgchange -a n $VOLUMEGROUP
+
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Default\Preferences
 
</pre>
 
</pre>
  
Where $VOLUMEGROUP is the corresponding name of the volume group
+
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Chromium\User Data\Default\Preferences
 +
</pre>
 +
 
 +
=== 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.
  
The individual volume devices are now available in:
+
If enabled the Preferences file contains:
 
<pre>
 
<pre>
/dev/mapper/$VOLUMEGROUP-$VOLUMENAME
+
  "dns_prefetching": {
 +
      "enabled": true,
 
</pre>
 
</pre>
  
=== Mounting an LVM from a device ===
+
If disabled the Preferences file contains:
 +
<pre>
 +
  "dns_prefetching": {
 +
      "enabled": false,
 +
</pre>
  
To list the Volume Groups (VG) run:
+
== Start-up DNS queries ==
 +
 
 +
When Chrome starts it queries for several non-existing hostnames that consists of a 10 random characters, E.g.
 
<pre>
 
<pre>
pvs
+
ttrgoiknff.mydomain.com
 +
bxjhgftsyu.mydomain.com
 +
yokjbjiagd.mydomain.com
 
</pre>
 
</pre>
  
To list information about a Volume Group (VG) run:
+
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>
 
<pre>
lvdisplay $VOLUMEGROUP
+
// 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>
 
</pre>
  
The field "LV Name" provides the volume name
+
<b>Note that $PROFILE (or %PROFILE%) the paths below is the profile dependent subdirectory which is normally Default but also could be Profile1, Profile2, etc.</b>
 +
 
 +
The Google Chrome disk cache can be found in:
 +
 
 +
On Linux
  
To make the volume group known to the system (only if it was previously exported using ''vgexport'' command, note that ''vgimport'' would alter the data in the LVM2 header):
 
 
<pre>
 
<pre>
vgimport $VOLUMEGROUP
+
/home/$USER/.cache/chromium/$PROFILE/Cache/
 +
/home/$USER/.cache/google-chrome/$PROFILE/Cache/
 +
/home/$USER/.config/chromium/$PROFILE/Cache/
 +
/home/$USER/.config/google-chrome/$PROFILE/Cache/
 
</pre>
 
</pre>
  
And active the volumes in the volume group:
 
 
<pre>
 
<pre>
vgchange -a y $VOLUMEGROUP
+
/home/$USER/.cache/chromium/$PROFILE/Media Cache/
 +
/home/$USER/.cache/google-chrome/$PROFILE/Media Cache/
 +
/home/$USER/.config/chromium/$PROFILE/Media Cache/
 +
/home/$USER/.config/google-chrome/$PROFILE/Media Cache/
 
</pre>
 
</pre>
  
The individual volume devices are now available in:
 
 
<pre>
 
<pre>
/dev/mapper/$VOLUMEGROUP-$VOLUMENAME
+
/home/$USER/.config/chromium/$PROFILE/Application Cache/Cache/
 +
/home/$USER/.config/google-chrome/$PROFILE/Application Cache/Cache/
 
</pre>
 
</pre>
  
These now can be analyzed with e.g. a tool like the [[Sleuthkit]] or loop-back mounted.
+
<pre>
 +
/home/$USER/.config/chromium/$PROFILE/GPUCache/
 +
/home/$USER/.config/google-chrome/$PROFILE/GPUCache/
 +
</pre>
  
To read-only loop-back mount an individual volume:
 
 
<pre>
 
<pre>
mount -o ro,loop /dev/mapper/$VOLUMEGROUP-$VOLUMENAME filesystem/
+
/home/$USER/.cache/chromium/PnaclTranslationCache/
 +
/home/$USER/.cache/google-chrome/PnaclTranslationCache/
 
</pre>
 
</pre>
  
== Also see ==
+
On MacOS-X
* [[:Category:File Systems | File Systems]]
+
<pre>
 +
/Users/$USER/Library/Caches/Chromium/$PROFILE/Cache
 +
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Cache
 +
</pre>
 +
 
 +
<b>TODO confirm the following paths</b>
 +
<pre>
 +
/Users/$USER/Caches/Chromium/$PROFILE/Cache/
 +
/Users/$USER/Caches/Google/Chrome/$PROFILE/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Caches/Chromium/$PROFILE/Media Cache
 +
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Media Cache
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Application Support/Chromium/$PROFILE/Application Cache/Cache/
 +
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/Application Cache/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Application Support/Chromium/$PROFILE/GPUCache/
 +
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/GPUCache/
 +
</pre>
 +
 
 +
<pre>
 +
/Users/$USER/Library/Caches/Chromium/PnaclTranslationCache/
 +
/Users/$USER/Library/Caches/Google/Chrome/PnaclTranslationCache/
 +
</pre>
 +
 
 +
On Windows XP
 +
 
 +
<b>TODO confirm the following paths</b>
 +
<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\%PROFILE%\Cache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Cache\
 +
</pre>
 +
 
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Application Cache\Cache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Application Cache\Cache\
 +
</pre>
 +
 
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Media Cache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Media Cache\
 +
</pre>
 +
 
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\GPUCache\
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\GPUCache\
 +
</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 Disk Cache Format]].
 +
 
 +
== 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>
 +
 
 +
== Cookies ==
 +
Chrome stores the cookies in a file named '''Cookies'''. This file uses the [[SQLite database format]].
 +
 
 +
=== Extension Cookies ===
 +
Chrome stores the cookies used by extensions in a file named '''Extension Cookies'''. This file uses the [[SQLite database format]].
 +
 
 +
<pre>
 +
SELECT datetime(((cookies.creation_utc/1000000)-11644473600), "unixepoch"), cookies.host_key, cookies.name, cookies.value, cookies.path, \
 +
datetime(((cookies.expires_utc/1000000)-11644473600), "unixepoch"), cookies.secure, cookies.httponly, datetime(((cookies.last_access_utc/1000000)-11644473600), "unixepoch"), \
 +
cookies.has_expires, cookies.persistent, cookies.priority FROM cookies;
 +
</pre>
 +
 
 +
== See Also ==
 +
 
 +
* [[SQLite database format]]
  
 
== External Links ==
 
== External Links ==
* [http://en.wikipedia.org/wiki/Logical_Volume_Manager_%28Linux%29 Wikipedia article on Logical Volume Manager]
+
* [http://en.wikipedia.org/wiki/Google_Chrome Wikipedia article on Google Chrome]
* [http://www.tldp.org/HOWTO/LVM-HOWTO/ LVM Howto], by [http://www.tldp.org/ The Linux Documentation Project]
+
* [http://www.chromium.org/user-experience/user-data-directory The Chromium Projects - User Data Directory]
* [http://www.sourceware.org/lvm2/ LVM2 Resource Page]
+
* [http://www.chromium.org/developers/design-documents/network-stack/disk-cache Chrome Disk Cache]
* [http://www.redhat.com/magazine/009jul05/features/lvm2/ The Linux Logical Volume Manager], by Heinz Mauelshagen and Matthew O'Keefe
+
* [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.datadisk.co.uk/html_docs/redhat/rh_lvm.htm LVM cheatsheet], by [[RedHat]]
+
* [http://www.useragentstring.com/pages/Chrome/ Chrome User Agent strings]
* [http://content.hccfl.edu/pollock/aunix1/lvm.htm Unix/Linux Administration Logical Volume Management Guide], by Wayne Pollock, 2005
+
* [http://computer-forensics.sans.org/blog/2010/01/21/google-chrome-forensics/ Google Chrome Forensics] by [[Kristinn Guðjónsson]], January 21, 2010
* [http://lvb.sti.fce.vutbr.cz/public/LinuxAlt_2009/2009_11_08_LA_04_LVM/2009_11_08_LA_04_LVM.pdf LVM2 – data recovery], by Milan Brož, LinuxAlt 2009
+
* [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
 +
 
 +
== Tools ==
 +
=== Open Source ===
 +
* [https://code.google.com/p/hindsight-internet-history/ hindsight-internet-history]
  
[[Category:Volume Systems]]
+
[[Category:Applications]]
 +
[[Category:Web Browsers]]

Revision as of 03:42, 22 June 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 Chrome SxS (Chrome side-by-side)

C:\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\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
};

Note that $PROFILE (or %PROFILE%) the paths below is the profile dependent subdirectory which is normally Default but also could be Profile1, Profile2, etc.

The Google Chrome disk cache can be found in:

On Linux

/home/$USER/.cache/chromium/$PROFILE/Cache/
/home/$USER/.cache/google-chrome/$PROFILE/Cache/
/home/$USER/.config/chromium/$PROFILE/Cache/
/home/$USER/.config/google-chrome/$PROFILE/Cache/
/home/$USER/.cache/chromium/$PROFILE/Media Cache/
/home/$USER/.cache/google-chrome/$PROFILE/Media Cache/
/home/$USER/.config/chromium/$PROFILE/Media Cache/
/home/$USER/.config/google-chrome/$PROFILE/Media Cache/
/home/$USER/.config/chromium/$PROFILE/Application Cache/Cache/
/home/$USER/.config/google-chrome/$PROFILE/Application Cache/Cache/
/home/$USER/.config/chromium/$PROFILE/GPUCache/
/home/$USER/.config/google-chrome/$PROFILE/GPUCache/
/home/$USER/.cache/chromium/PnaclTranslationCache/
/home/$USER/.cache/google-chrome/PnaclTranslationCache/

On MacOS-X

/Users/$USER/Library/Caches/Chromium/$PROFILE/Cache
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Cache

TODO confirm the following paths

/Users/$USER/Caches/Chromium/$PROFILE/Cache/
/Users/$USER/Caches/Google/Chrome/$PROFILE/Cache/
/Users/$USER/Library/Caches/Chromium/$PROFILE/Media Cache
/Users/$USER/Library/Caches/Google/Chrome/$PROFILE/Media Cache
/Users/$USER/Library/Application Support/Chromium/$PROFILE/Application Cache/Cache/
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/Application Cache/Cache/
/Users/$USER/Library/Application Support/Chromium/$PROFILE/GPUCache/
/Users/$USER/Library/Application Support/Google/Chrome/$PROFILE/GPUCache/
/Users/$USER/Library/Caches/Chromium/PnaclTranslationCache/
/Users/$USER/Library/Caches/Google/Chrome/PnaclTranslationCache/

On Windows XP

TODO confirm the following paths

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\%PROFILE%\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Application Cache\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Application Cache\Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\Media Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\Media Cache\
C:\Users\%USERNAME%\AppData\Local\Google\Chromium\%PROFILE%\GPUCache\
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\%PROFILE%\GPUCache\

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 Disk Cache Format.

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;

Cookies

Chrome stores the cookies in a file named Cookies. This file uses the SQLite database format.

Extension Cookies

Chrome stores the cookies used by extensions in a file named Extension Cookies. This file uses the SQLite database format.

SELECT datetime(((cookies.creation_utc/1000000)-11644473600), "unixepoch"), cookies.host_key, cookies.name, cookies.value, cookies.path, \
datetime(((cookies.expires_utc/1000000)-11644473600), "unixepoch"), cookies.secure, cookies.httponly, datetime(((cookies.last_access_utc/1000000)-11644473600), "unixepoch"), \
cookies.has_expires, cookies.persistent, cookies.priority FROM cookies;

See Also

External Links

Tools

Open Source