Hi forum friends,
What is: -https://blogger.googleusercontent.com/tracker/1582059931508490185-578113533223987097?l=blog.uncommonsensesecurity.com
It is a GIF89a!,D;? Is it a trash tracker?
How can I block this? It is a red rimmed green square image,
polonus
I think now these are finds from this extension in my GoogleChrome: http://userscripts.org/scripts/show/35051
So these are webbugs for google tracking in the blogosphere: one may notice a blank 1x1 gif at the end of the post that originates from: -https://blogger.googleusercontent.com/tracker
The first number is your unique blogID and the second number your unique postID. Interesting read here: http://crsouza.blogspot.com/2010/03/partial-least-squares-analysis-and.html (link article author = Cesar Roberto de Souza)
This all in the light of what we read here from link article author Moxie Marlinspike: http://www.itpro.co.uk/638533/moxie-marlinspike-pans-google-privacy-changes
Moxie Marlinspike is the well-known developer of the GoogleSharing privacy add-on for fx.
Alas haven’t seen that coming to GoogleChrome yet. Anyone knows of some extension that does the same. That is one of the reasons why I always launch myGoogleChrome via ChromePrivacyGuard!
With the mentioned webbug detection in Google Chrome installed you can see some of these footer-blogger tracking examples on this page e.g.: http://www.ecademy.com/module.php?mod=extprofile&fid=60263
for instance: -https://blogger.googleusercontent.com/tracker/8164550789765287262-3514269153307000741?l=lavaroomrecording.blogspot.com
So the individual blogger ID and posting ID after March1 coming will be bundled with all tracking for all 60 or so Google documents, and with no opt out any longer for a particular document. So if you are a google blogger and Gmail user your profile data are going to be combined.
In what way the user can anonymize here and is any escape of this constant logging and profiling still possible. Google once promished never to go evil, didn’t they?
polonus
Something different here, see: http://jsunpack.jeek.org/?report=b79a8397dcf4ccbc943ff408a053db06a97e1211 (go there with ample script protection and in a VM)
here I find: -http://www.file.net/favicon.ico and space.gif (1x1) decodes to
(( OO
This could be used a foothold for a PHP backdoor hack. So there are also various malcious favicon.ico uses. Malicious web_bugs, so to say. Webmasters should not use JavaScript to call favicon.ico files or write the link tag with JavaScript, so hackers could not run or install malcious software!
polonus