Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Privacy Your Rights Online

FTC Is In Talks With Adobe About the 'Flash Problem' 179

jamie links to news that the FTC is talking with Adobe about persistent Flash cookies. "Flash isn't actually necessary to watch YouTube videos, but the rest of this article is interesting."
This discussion has been archived. No new comments can be posted.

FTC Is In Talks With Adobe About the 'Flash Problem'

Comments Filter:
  • by 140Mandak262Jamuna ( 970587 ) on Sunday December 05, 2010 @06:50PM (#34454268) Journal
    Flash player settings has an option to set the amount of local storage permitted for the player. What happens if I set that amount to zero and mark it permanent (i.e. check box remember)? Would it remove the ability of the flash player to set cookies?
  • by characterZer0 ( 138196 ) on Sunday December 05, 2010 @06:56PM (#34454314)

    I have read that rm -rf ~/.adobe; mkdir ~/.adobe; chmod 000 ~/.adobe does the trick. Can anybody confirm?

  • by Anonymous Coward on Sunday December 05, 2010 @07:14PM (#34454448)

    I actually use Linux, what scares me is that the ONLY closed source piece of software on my computer is flash.
    I think Adobe knows, or hopes, that they will one day be providing massive amounts of video content from actual television channels and Cable Company's and the only way to build some kind of content protection system, DRM, or paid service model would be to keep Flash closed.

  • Probably would work... Well, I'd simply do "rm ~/.adobe/*; chmod 500 ~/.adobe/*", which would be shorter and keep read/access rights to said directory.

    That said, if Flash expects to be able to write to that directory, it might crash when it tries to utilize it. So it really isn't a foolproof method.

    As per this moment, under .adobe in my home directory exists the following structure: "~/.adobe/Flash_Player/AssetCache/VSUUJTSX/". The directory is probably randomly generated just like profile directories in Mozilla (harder to predict in case of a flaw in the plugin/browser). In there are just files with the extensions .swz and .heu and one file called "cacheSize.txt". None of these files seems to be human readable (well, okay cacheSize.txt makes somehow sense). Oddly enough, the oldest file is from 25th September 2010. As I use my browser daily and don't mind youtube or the odd flash game, this is strange indeed. I would nearly say that they stopped using it.

Get hold of portable property. -- Charles Dickens, "Great Expectations"

Working...