Closed bamos closed 10 years ago
The mmcblk0.bson
file contains the following:
src/gammaray [master] » ./bin/tools/bson-printer /tmp/mmcblk0.bson
BSON Printer -- By: Wolfgang Richter <wolf@cs.cmu.edu>
Analyzing BSON File: /tmp/mmcblk0.bson
{
'type' : [BSON_STRING, 3] 'mbr'
'gpt' : [BSON_BOOLEAN] true
'sector' : [BSON_INT32] 0
}
{
'type' : [BSON_STRING, 15] 'metadata_filter'
'bitarray' : [BSON_BINARY, 0]
}
Great, I've modified gray-crawler
to transmit the result over the network.
On the server, run ncat -l 32000 > test.bson
,
and give gray-crawler
an IP address.
./gray-crawler /dev/block/mmcblk0 192.168.1.3
test.bson
now has the same contents as mmcblk0.bson
from above.
I'm still not sure if this is the right block device.
src/gammaray [master] » bin/tools/bson-printer /tmp/test.bson
BSON Printer -- By: Wolfgang Richter <wolf@cs.cmu.edu>
Analyzing BSON File: /tmp/test.bson
{
'type' : [BSON_STRING, 3] 'mbr'
'gpt' : [BSON_BOOLEAN] true
'sector' : [BSON_INT32] 0
}
{
'type' : [BSON_STRING, 15] 'metadata_filter'
'bitarray' : [BSON_BINARY, 0]
}
I've built
gray-crawler
to run on Android. Modifications still need to be made to stream the BSON across the network.I'm currently only exporting the metadata of
/dev/block/mmcblk0
.All of the mounts are on these devices, which isn't evident by the
by-name
paths output by themount
command:The following command exports the block device metadata as BSON.
mmcblk0.bson
only consumes 83 bytes, so I'm not sure how representative it is of the block devices we're interested in on Android. I also expect all 13 partitions to show up in the metadata.