Maybe also interesting and related: Google is internally using the protocol buffer [1] a lot for serialization. Could it be that the request is serialized with this protocol? As you mentioned, beginning the request with "\xc4" indicates an information to the receiver about the content. Could that hint to a binary encoding -- or do you rather think it's encoded with an algorithm such as base64? - Chris [1] http://code.google.com/p/protobuf/ Thomas R. Koll wrote:
Output (with repr): '\n\xc4\x02\n \xe0\x01DQAAAJwAAADBuNClm8PAy5Hr393OZSI8DrglXLMTgVM5hn0glGaTY4Xj7lLGN_v1DgUDySiUWo5PITOmJU7CdEhXzpHr9s40OMGNDdHxoPmgck3DBMCcd53rWJiNW0xpar5-DIcmuEikPiBTD-R4BA143JOtl7nUSkmcHf2axnyQQYLPncTDEFsRsh7L_jSIqZCAyRj27Cx4BBh-TyXSlieTGEpSXNe0\x10\x00\x18\xea\x07"\x10200145da90c86e5f*\x07dream:32\x02en:\x02GBB\x10T-Mobile AustriaJ\x00R\x0523203Z\x0523203b\x15am-android-tmobile-at\x13"\n \x08\x048\x01@\x00H\nP\x00\x14'
So these are a lot of hex characters which are not inside the ascii character map. I don't know if this is the right trail, but here is where I don't know how to proceed on myself. It would be very interesting to see how the G1's communicate with Google!
\xc4 mean 244 characters. \x02GBB is 2 chars: that's GB plus that B? But in generalthat explains the hexcodes quite well. So, the only real interesting thing is this string: "DQAAAJwAAADBuNClm8PAy5Hr393OZSI8DrglXLMTgVM5hn0glGaTY4Xj7lLGN_v1DgUDySiUWo5PITOmJU7CdEhXzpHr9s40OMGNDdHxoPmgck3DBMCcd53rWJiNW0xpar5 -DIcmuEikPiBTD- R4BA143JOtl7nUSkmcHf2axnyQQYLPncTDEFsRsh7L_jSIqZCAyRj27Cx4BBh- TyXSlieTGEpSXNe0"
I expect it to be a unique session key not containing any information at all (or at least that's what I'd claim if I'd was Google).
ciao, tom
-- Thomas R. "TomK32" Koll <> http://ananasblau.com just a geek trying to change the world http://github.com/TomK32
_______________________________________________ Metalab mailing list Metalab@lists.metalab.at http://lists.metalab.at/mailman/listinfo/metalab