Slashdot Mirror


Browser Privacy Test

lazyforker writes "A NYTimes blog post reports the results of security researcher Kate McKinley's tests of various browsers' (FireFox, Chrome, IE, Safari) privacy protection mechanisms. Specifically she tested their cookie handling. She also examined their handling of Flash's cookies. In summary: Safari on Mac OS X (in the 'private browsing' mode) is not so private ('quirky'). Safari on XP is not private at all. Flash behaves awfully everywhere."

5 of 133 comments (clear)

  1. One word by Anonymous Coward · · Score: 5, Informative

    Flash behaves awfully everywhere

    FlashBlock

    NoScript works too but I find it sort of annoying because it stops half the web from working.

  2. Fundamental flaw in survey by QuietLagoon · · Score: 3, Informative
    Since it appears that the author of the "study" chose the browsers to test based upon popularity, the "researcher" based the survey upon the mistaken assumption that popularity is an indication of security perception.

    Microsoft's Internet Explorer, as the mos tpopular browser, disproves tha tpopularity does not equate to the perception of security.

    A better basis for the selection of browsers would be to select those thought to be secure. That would eliminate IE and Safari at the start, and it might even add Opera.

  3. Re:cringe-inducing bug in konqueror by ScrewMaster · · Score: 3, Informative

    Posting this anonymously, for reasons that will soon be evident.

    You do realize that you didn't have to use your real sexual preferences as an example, don't you?

    --
    The higher the technology, the sharper that two-edged sword.
  4. Re:Clean out the '\Flash Player' folder by thePowerOfGrayskull · · Score: 3, Informative

    Actually for Flash you should take a look at these instructions which will work cross-platform.

  5. Re:cringe-inducing bug in konqueror by slash.duncan · · Score: 3, Informative

    WTF gave you the idea that's a konqueror bug? Why would opening a document in OOo, which isn't even developed/shipped by the same (upstream) people as konqueror, be a konqueror bug?

    No, rather, as AC already posted, konqueror will with default associations as shipped by upstream (KDE), using the "view source" function, open pages using kwrite or kate or kedit. Assuming it's not a PEBCAK issue of the local sysadmin or user, OOo at least as shipped by Ubuntu appears to change that default by associating HTML (or possibly XML) files with itself, at a higher priority than kwrite/whatever-else. That's either Ubuntu's fault or OOo's (or the sysadmin/user for overriding the distribution defaults, if that's why the associations are set the way they are), but it certainly isn't KDE/Konqueror's, as KDE isn't what setup those associations, it's just doing what it's supposed to and following the file associations config as setup on the system it's installed on, as overruled by the config of the user running it, if they have chosen to do so.

    Looked at a different way, it would be either OOo's bug, for having a recent documents history that can't be disabled (if that's indeed the case), or a user PEBCAK, for not disabling said history or wiping it out after opening a document they don't wish to appear in said history.

    --
    Duncan
    "Every nonfree program has a lord, a master,
    and if you use the program, he is your master."
    R Stallman