Thursday, November 26, 2009

Imaging a GoogleChromeOS with F-Response

After downloading the VMware image of the new released Beta version of GoogleChromeOS, I thought what can I use to image the new operating system?

clip_image002

So I figured F-Response would be my tool of choice to connect to the GoogleChromeOS running system and then use the great MAC Forensic Imager tool by Ryan Kubasiak.

Upon boot ChromeOS gives you a tabbed interface and not much else, but after a bit of digging I found access to the shell using ctrl/alt/T and up popped the shell. I guessed the root password “chronos” and logged in.

I had previously emailed the F-Response Field Kit Linux script to my gmail account and saved the attachment to the Downloads folder.

To get the F-Response Linux script to run I had to copy it to /tmp and run it using the command;

sudo ./f-response-fk-lin –u andyandy –p 12345678901234 –i 3260

Issue 1 IPtables

I then had some connection issues as GoogleChromeOS comes with IPtables configured so I removed all the iptables rules and changed the policy from Deny to Accept;

Comands;

iptables -L INPUT -n –linenumbers

iptables -D INPUT [line number here]

iptables -P INPUT ACCEPT

clip_image004

Now with connectivity I was able to reach my Macbookpro and start the connection process.

clip_image006

I then used the Globalscan ISCSI client on the Macbookpro to establish the connection.

clip_image008

The F-Response status then showed me that the connection was established;

clip_image010

The F-Response status then showed me that the connection was established;

clip_image012

The GoogleChromeOS disk showed up on my Mac as rdisk4 and contained 3 partitions;

Fdisk output from the shell on the Mac.

clip_image014

Output from the GUI Disk Util Tool

clip_image016

Mounted Partions on my Desktop;

clip_image017

File explorer view of each partition;

Root Partition;

clip_image019

Second Partition;

clip_image021

I then used the great MAC Forensic Imager tool by Ryan Kubasiak, to create an image of the GoogleChromeOS physical drive.

clip_image023

The imaging took no time at all to complete and successfully completed to E01 file format. The log recorded the imaging as follows;

Physical Disk Infoscheme: fdisk

block size: 512

_ ## Type_________________ Name_________________ Start___ Size____

+ MBR Master Boot Record 0 1

1 Linux_Ext2FS 1 1945600

2 Linux_Swap 1945601 1945600

3 Linux_Ext2FS 3891201 1945600

+ synthesized

ewfacquirestream 20080501 (libewf 20080501, zlib 1.2.3, libcrypto 0.9.7)

Using the following acquiry parameters:

Image path and filename: /Users/dougee/Desktop/GCOS-FRes.E01

Case number: 652

Description: GoogleChromeOsF-Response

Evidence number: 652

Examiner name: Dougee

Notes: GoogleChromeOs with F-Response Field Kit

Media type: fixed

Volume type: physical

Compression used: none

Compress empty blocks: no

EWF file format: EnCase 5

Acquiry start offet: 0

Amount of bytes to acquire: 0 (until end of input)

Evidence segment file size: 1.4 GiB (1572864000 bytes)

Block size: 64 sectors

Error granularity: 64 sectors

Retries on read error: 2

Wipe sectors on read error: no

Acquiry started at: Thu Nov 26 11:28:30 2009

2 comments:

  1. Quick question:

    Should the iptables be the same as what you show above or does something need changing? Sorry not that familiar with this stuff.

    ReplyDelete
  2. Hi Lee, on my install the IPtables were turned on which made it impossible for me to connect from my forensic machine across the network.

    If you can ping the machine across the network then you should be good to go, if not you may need to adjust the IPtable rules to open up the ports. If the ports policy (as mine was) are set to deny connections just use the command;

    sudo iptables -P INPUT ACCEPT

    To change the DENY to ACCEPT, you need to do this for each IP policy, mine actually had three DENY policy rules set. I am sure if you can PING the GoogleChromeOS from your analysis box you should be good to go.

    ReplyDelete