Thanks for the info BHP
Quote:
That's all, folks! The data included a source identifier (EEPE323, likely
BearShare's partner ID so that SaveNow knows who to pay) and an ID in the
format 4F8...8c. The ID is a 65-byte data chunk which is unintelligble but
may be Base64-encoded (note that 65 bytes is not much at all, and if it is
indeed Base64 encoded, the original unencoded data would be less than 64 bytes.)
NO PERSONAL INFORMATION WAS TRANSMITTED.
|
No personal information in the first transmission (or any it seems) but the question is the ID string that's transmitted a unique ID? That could cause problems.
Still reading - will add more to this post I'm sure.
Edit: more stuff...
Ok just read thru the whole thing. The packet log dump is only from the 20 minutes after orginal install. It's a start but not complete.
The unique ID number I understand when matched with the advertising partners request for the ability to track how useful the ads are in reaching the customers but I don't like the idea of a unique ID number that could be used in the future for less than helpful goals.
... paranoia - It's not just a job, it's an adventure. Mostly in one's own head, but that's not the point. :)