I am a computer security professional, when I'm not plotting Ley lines, and a very good freind of mine imparted this information to me about
super-cookies that are on your computer that you probably have no idea even exist. They cannot be removed normally, but I am supplying you with a
batch file that will remove them. They are called LSOs.
A LSO, or Local Shared Object, is a cookie installed by Macromedia Flash, but it is not stored in the same location as other cookies, does not have
the same constraints as other cookies, like text only and a size no larger than 1K, and are not deleted by using the browser option to Clear
These cookies can share data across domains, allowing unrelated web sites to know your browsing habits from other sites.
Even more insidious is that they are part of a P2P network. That's right, Adobe and other sites can store data on YOUR computer, without your
knowledge or permission, and then YOUR computer serves that data to other users on the internet, to take the load off of the web servers of the sites
that planted these cookies on your computer. Your computer becomes a robot, sending data to other computers, as part of a giant botnet.
This is not a WINDOWS issue. Linux and OSX users are susceptible to flash cookies just like Windows users, and they may be at an even greater risk,
because they are so entrenched in their belief that their OS is invulnerable to malware and spyware that they never even know that have these LSO's.
At least Windows users have a clue when they run a scan with any AV or Anti-Malware software because it reports the presence of tracking cookies. It
may not be able to remove them, but at least they know there is something there, and can seek assistance on removing it.
They can be manually removed, or a batch file can be created:
rem name this nukeflash.bat ============================================
rem :: nuke any existing cookies and subdirectories ::
rem cd "%APPDATA%MacromediaFlash Player#SharedObjects"
rem dir /b/s
rd /q/s "%APPDATA%MacromediaFlash Player#SharedObjects"
md "%APPDATA%MacromediaFlash Player#SharedObjects"
rem cd "%APPDATA%MacromediaFlash Playermacromedia.comsupportflashplayersys"
rem dir /b/s
rd /q/s "%APPDATA%MacromediaFlash Playermacromedia.comsupportflashplayersys"
md "%APPDATA%MacromediaFlash Playermacromedia.comsupportflashplayersys"
What makes this even more evil is that there is no setting or control on your computer that you can use to prevent or even delete these cookies. You
must visit the Macromedia web site at:
When you visit the site, Adobe attempts to disguise the settings control panel by making it appear to be a picture of a control panel, and in very
small print says “Note: The Settings Manager that you see above is not an image; it is the actual Settings Manager.”
To check the effectiveness of the Macromedia tool at removing these LSO’s, I removed all two hundred plus LSO’s on my computer, then I ran a
standalone LSO remover called KFC. (Kill Flash Cookies) KFC found seven additional LSO’s that the Macromedia Control Panel not only failed to
remove, but failed to report that they existed.
Trusting Macromedia to remove the cookies that they plant on your computer is like trusting a virus writer in the Ukraine to produce a tool that will
remove their own virus. In my opinion, this is worse than the Sony Root Kit debacle where playing a Sony DVD in your computer installed secret
anti-piracy software without notification or permission.
Hopefully, HTML5 will kill Flash, and there will be one less piece of bloatware from Adobe bogging down our systems.
NOTE: This thread was not moved into the "HOAX" forum because of the content on what locally stored objects are, but because of the notion that such
objects might be shared between website domains or that the objects are inherently bad, which is incorrect.
Additionally, the information on "Peer-Assisted Networking" (P2P) in this opening post is overly alarmist. The evolution of RTMFP in Flash allows for
client-to-client data transfer, such as Flash-based video or audio chat, not the hijacking of user bandwidth.
edit on 29-3-2011 by
SkepticOverlord because: (no reason given)