Difference between pages "USBCrypt" and "Google Chrome"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Created the page)
 
(Open Source)
 
Line 1: Line 1:
{{Infobox_Software |
+
Google Chrome is a [[Web Browser|web browser]] developed by Google Inc.
  name = USBCrypt |
+
  maintainer = WinAbility Software |
+
  os = {{Windows}} |
+
  genre = {{Encryption}} |
+
  license = WinAbility Software License |
+
  website = [http://www.winability.com/usbcrypt/ winability.com/usbcrypt] |
+
}}
+
  
'''USBCrypt''' is a commercial (closed source) software intended primarily to encrypt external USB drives. (However, the encryption is not limited to the external drives or to the USB connection: any drive that is recognized by Windows as a valid drive with read-write access can be encrypted with USBCrypt.) USBCrypt software is [[Windows|Windows 7, Vista, XP, 2000]]-only. It supports [[AES]], and [[Twofish]] encryption with the 128- and 256-bit keys, in the [[XTS]] and [[CBC]] encryption modes.
+
== Configuration ==
 +
The Google Chrome configuration can be found in the '''Preferences''' file.
  
== Recognizing drives encrypted with USBCrypt ==
+
On Linux
 +
<pre>
 +
/home/$USER/.config/google-chrome/Default/Preferences
 +
</pre>
  
USBCrypt encrypts drives by creating the file-based Virtual Encrypted Disks on them. In addition to one or more files that contain the encrypted data, USBCrypt also puts a portable software on the drive, to enable its use on other computers. While the encrypted data files contain no identifying information (and thus support [[plausible deniability]]), the presence of other supporting files makes it easy to identify the drives encrypted with USBCrypt: the root folder of the encrypted drive contains the file USBCrypt.exe as well as a folder named USBCrypt-system. The latter contains the encrypted data files as well as USBCrypt soiftware files (DLL and SYS). The file USBCrypt.ini is a text-only file that contains settings as well as license information (including the name of the person or business who has purchased the software).
+
On MacOS-X
 +
<pre>
 +
/Users/$USER/Library/Application Support/Google/Chrome/Default/Preferences
 +
</pre>
  
== Spare-key file ==
+
On Windows XP
 +
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default\Preferences
 +
</pre>
  
When the user is encrypting a drive with USBCrypt software, s/he has the option to create a "spare key" file on the user's computer. This file contains a copy of the encryption key that can be used by the user if s/he forgets the main encryption password. Or, it can be used by a system administrator to get access to the encrypted data in case the employees leave the company and take the passwords with them. Each spare key file contains a copy of just one encryption key for the specific encrypted drive it was created for. It cannot be used to decrypt any other drive, even if the user has used the same password and encryption algorithm. USBCrypt can automatically detect whether it can decrypt a specific drive with a spare key.
+
On Windows Vista and later
 +
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Preferences
 +
</pre>
  
== Forensic Acquisition ==
+
Or for '''Chrome SxS''' (Chrome side-by-side)
  
If you encounter a system that has a live USBCrypt drive, it is imperative that you capture the contents of the encrypted drive before disconnecting the drive or shutting down the system. Once the system is shutdown, the contents becomes inaccessible unless you have the proper encryption key generated by a user's password. If the encrypted drive in not live, it is imperative to secure access to the user's computer that was used to encrypt the drive: there is a possibility that the computer still has the "spare key" file stored on its hard drive, assuming the user has the selected the option to create such a file when encrypting the drive. 
+
<pre>
 +
C:\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\User Data\Default\Preferences
 +
</pre>
  
== Attacks ==
+
Or for '''Chromium'''
If the "spare key" file for the encrypted drive has not been obtained, then the only option for acquiring the content of a dismounted USBCrypt drive is to do a brute-force password guessing attack. USBCrypt software itself contains a built-in command to perform the brute-force attack on the drives it encrypts.
+
 
 +
On Linux
 +
<pre>
 +
/home/$USER/.config/chromium/Default/Preferences
 +
</pre>
 +
 
 +
On MacOS-X
 +
<pre>
 +
/Users/$USER/Library/Application Support/Chromium/Default/Preferences
 +
</pre>
 +
 
 +
On Windows XP
 +
<pre>
 +
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Chromium\User Data\Default\Preferences
 +
</pre>
 +
 
 +
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.
 +
 
 +
If enabled the Preferences file contains:
 +
<pre>
 +
  "dns_prefetching": {
 +
      "enabled": true,
 +
</pre>
 +
 
 +
If disabled the Preferences file contains:
 +
<pre>
 +
  "dns_prefetching": {
 +
      "enabled": false,
 +
</pre>
 +
 
 +
== Start-up DNS queries ==
 +
 
 +
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>
 +
 
 +
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>
 +
 
 +
<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 uses the [[Chrome Disk Cache Format]] and can be found in:
 +
 
 +
On Linux
 +
 
 +
<pre>
 +
/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>
 +
/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>
 +
/home/$USER/.config/chromium/$PROFILE/Application Cache/Cache/
 +
/home/$USER/.config/google-chrome/$PROFILE/Application Cache/Cache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.config/chromium/$PROFILE/GPUCache/
 +
/home/$USER/.config/google-chrome/$PROFILE/GPUCache/
 +
</pre>
 +
 
 +
<pre>
 +
/home/$USER/.cache/chromium/PnaclTranslationCache/
 +
/home/$USER/.cache/google-chrome/PnaclTranslationCache/
 +
</pre>
 +
 
 +
On MacOS-X
 +
<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.
 +
 
 +
== 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 ==
 +
* [[Chrome Disk Cache Format]]
 +
* [[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://www.winability.com/usbcrypt/ Official website]
+
== Tools ==
* [http://www.usbcrypt.com/ USBCrypt web site]
+
=== Open Source ===
 +
* [https://code.google.com/p/hindsight-internet-history/ hindsight-internet-history]
 +
* [[plaso]]
  
[[Category:Encryption]]
+
[[Category:Applications]]
[[Category:Disk encryption]]
+
[[Category:Web Browsers]]

Revision as of 04:45, 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 uses the Chrome Disk Cache Format and 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.

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