New css attack

[Itachi587 (Bud)]

I'm not using private browsing, but I am using custom settings for history.

[call me daddy x]

Mozilla definitely needs to address this soon, as it is starting to get out of hand if you ask me....

Well all browser makers are going to have to come up with something, and that probably means the w3c coming up with a new css spec for a:visited that disables background-urls that aren't inherited from a:link. :wacko:

[mogley]

That site and What The Internet Knows About You still shows that I haven't visited anything.

I'm using Opera 10.60, the css fix, and history disabled.

[TheFamilyAccount]

You absolutely have to love that extra security you're getting from disabling history.

Shame only Firefox users seem to be able to claim that :ermm:

[Nicole]

I'm missing how this is mozilla specific.
It will have the same effect in every browser that supports css a:visited. :wacko:

Yes, I know but Mozilla is the only one who will address this within the next year :P

IE will allow this to go on for ages, as they most likely don't care at all.

[viky_khanna]

For a second there I thought about moving this thread to a more relevant forum.

Then I realized that this probably is the most relevant forum, as this is the forum where the people who visit are most likely to get their IP phished, and at the same time, most likely to care about getting their IP phished.

Isn't BT great.

:dabs:

[Allisonツ☮]

For a second there I thought about moving this thread to a more relevant forum.

Then I realized that this probably is the most relevant forum, as this is the forum where the people who visit are most likely to get their IP phished, and at the same time, most likely to care about getting their IP phished.

Isn't BT great.

:dabs:

Lol I was debating on putting it in Internet, Programming and Graphics...

[MELANiE♥]

Here are my settings in case anybody wishes to try them out...


Let us (FST) know if it works for you so we can spread the word. :P

[arturo m]

As I understand it, disabling history prevents this attack, so that would explain it.

Is there a CSS fix you'd be able to employ against this, or is disabling history the only fix?

[Fluffy Hamster]

So what precisely is this detecting? Your browse history rather than the presence of a:visited? Because the description implied it was catching a cascaded event during the click of a link, but the test page did correctly detect a link visited while NOT viewing the page itself so that seems unlikely.