Cookie deletion faces new challenge
Uncle Jean
they stay around a lot longer. They come with PIE, or
Persistent Identification Element, a technology that evades
deletion."
<http://www.indystar.com/apps/pbcs.dll/article?
AID=/20050501/BUSINESS/505010356>
OR
<http://makeashorterlink.com/?G2B912FFA>
UJ
Vanguard
news:7D2de.59$Id6....@weber.videotron.net...
Oh boy, yet another "the sky is falling" doomsayer (but then your
Organization header says it all). Already discussed here (see
http://snipurl.com/elh5). Just configure the cache (to zero) if you
don't want to have .sol files saved on your disk. A cookie (.sol file)
saved but isn't cached disappears and so it cannot be used for tracking.
The article mentioned in the other linked thread was more responsible in
that it had a link to Macromedia's web page where you can see how to
configure your Flash cache, or just right-click on any Flash content and
select Properties to set the cache to zero.
--
____________________________________________________________
** Post your replies to the newsgroup - Share with others **
For e-mail Reply: remove "DELETE", add "~VN56~" to Subject.
____________________________________________________________
David Arnstein
<vangua...@comcastDELETE.net> wrote:
>Oh boy, yet another "the sky is falling" doomsayer (but then your
>Organization header says it all). Already discussed here (see
>http://snipurl.com/elh5).
I started that thread. It is named "Flash Is Evil."
>Just configure the cache (to zero) if you
>don't want to have .sol files saved on your disk. A cookie (.sol file)
>saved but isn't cached disappears and so it cannot be used for tracking.
What you fail to mention is that in the above thread, I reported that
the configuration you describe is NOT saved by the Flash software. So
it is useless. You can configure zero cache until your hands wear
out. The cache size will return to its default (non-zero) value the
next time you use Flash.
>The article mentioned in the other linked thread was more responsible in
>that it had a link to Macromedia's web page where you can see how to
>configure your Flash cache, or just right-click on any Flash content and
>select Properties to set the cache to zero.
You really love Flash software, don't you? Do you have a stake in the
success of this product? Or are you just anti-privacy in general?
--
David Arnstein
arnstei...@pobox.com
Vanguard
news:d53vcu$5hb$1...@reader1.panix.com...
> In article <a8KdnXMnVId...@comcast.com>,
> <vangua...@comcastDELETE.net> wrote:
>>Oh boy, yet another "the sky is falling" doomsayer (but then your
>>Organization header says it all). Already discussed here (see
>>http://snipurl.com/elh5).
>
> I started that thread. It is named "Flash Is Evil."
>
>>Just configure the cache (to zero) if you
>>don't want to have .sol files saved on your disk. A cookie (.sol
>>file)
>>saved but isn't cached disappears and so it cannot be used for
>>tracking.
>
> What you fail to mention is that in the above thread, I reported that
> the configuration you describe is NOT saved by the Flash software. So
> it is useless. You can configure zero cache until your hands wear
> out. The cache size will return to its default (non-zero) value the
> next time you use Flash.
Your experience, not mine. My settings stick. The problem is likely
that you have another instance of Internet Explorer loaded when changing
the settings. I've noticed that the settings might not stick and where
the last instance of IE will have its Flash settings retained. If you
have only one instance of IE open and configure the per-site settings
then those settings will stick. If you have only one instance of IE
open that is showing the session manager then those settings will stick.
The problem with the settings not sticking is when you have multiple
instances of IE that are battling over whose settings get retained.
Make sure there is only one instance of IE loaded when making changes to
Flash settings, especially for global settings.
To prevent the last instance's settings from overriding those changes
made in another instance, their session manager would have to forcibly
close all other instances of IE. Or, their session manager would have
to forcibly refresh every instance of IE everytime you made any change.
Imagine trying to move the cache size slider when you have to wait for
every instance of IE, including the one in which you are using the
session manager, to get refreshed. Don't have multiple instances of IE
battling over whose settings get retained. My popup blocker program,
PopUpCop, lets me configure an option where a change in its settings
will: (1) Refresh all instances of IE; (2) Prompts me if I want each
instance refreshed; or, (3) Doesn't refresh any instances of IE. Looks
like Macromedia chose method #3.
It is rather stupid that Macromedia opens a second instance of IE when
you click on the Advanced button when right-clicking on Flash content
and changing its Settings. Instead make sure no instances of IE are
loaded (check Task Manager's Processes tab) and then directly visit
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager03.html
so only that one instance of IE is running, or close the first instance
of IE. This is poor design and may cause settings to not stick.
I did complain to Macromedia of having to visit their web pages in order
to change the global settings for Flash. Their response is that they
are working on a local session manager (i.e., a downloadable program
that runs from your hard disk and doesn't even need the browser to be
open). This would make it pretty easy to have it close all instances of
IE (although that could now be done - except, of course, for the
instance running the session manager). It would also make it possible
to allow changes without the interference of constant refreshes of the
browser as it would have a Save function to save your pending changes
and then also apply them to all instances of the browser. So, yeah,
their session manager does need work, and a local utility would
eliminate even having to be online to make those changes.
>>The article mentioned in the other linked thread was more responsible
>>in
>>that it had a link to Macromedia's web page where you can see how to
>>configure your Flash cache, or just right-click on any Flash content
>>and
>>select Properties to set the cache to zero.
>
> You really love Flash software, don't you? Do you have a stake in the
> success of this product? Or are you just anti-privacy in general?
Or are you just pro-extremist in general?
It is irresponsible to tell users they must not use Flash because some
joker decided to finally get around to abusing Flash cookie files but
for which there exists a workaround. Until anti-virus software started
checking Word files for malicious macros and signing support was added,
no one gave up Word but instead just disabled macros. The workaround is
easy: zero out the cache (and change settings when only 1 instance of IE
is loaded).
If you are using only 1 instance of IE to make Flash setting changes and
those settings are okay on the next immediate load of IE but somehow get
changed days later then perhaps you should check what you run or have
scheduled to run on your machine that is wiping out the .sol files. You
do need to keep the one at "%userprofile%\Application
Data\Macromedia\Flash
Player\macromedia.com\support\flashplayer\sys\settings.sol" because that
has your customized settings. If that file is missing or rebuilt then
obviously you are back to the defaults. You can use SysInternals'
FileMon to watch that file (just watch for writes). You do realize
there is a "Never ask again" checkbox when making changes to the
settings, right?