• scytale@piefed.zip
    link
    fedilink
    English
    arrow-up
    15
    ·
    4 days ago

    Google said it does not consider browser fingerprinting to be a security vulnerability.

    Apple described the attack as “currently out of scope,” with possible mitigations in the future.

    Mozilla acknowledged the findings but has not implemented any fix.

    Well Firefox should get a fix because the other two don’t give a shit. Hopefully DDG does too.

  • SayCyberOnceMore@feddit.uk
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 days ago

    So, it needs time to fill a large chunk of my SSD then use AI to guess what my specific machine is doing after that… when I’ve probably closed the FROST web page…

    Ok, if I’m a “person of interest” that they’re going to spend a lot of time looking at then I’d bear this in mind… for me, you & joe public… it’s not a thing.

  • unitedwithme@lemmy.today
    link
    fedilink
    English
    arrow-up
    4
    ·
    4 days ago

    Wire, such trash! So, using multiple browsers like Firefox and any fork, technically separate programs, aren’t even safe. So a hardened browser isn’t sage from an untrustworthy one.

    Like the article says:

      • Look into tighter OPFS quotas where possible. The researchers’ own headline suggestion is for browser vendors to clamp the maximum OPFS size, restrict high-resolution timers when OPFS is in use, or require explicit permission. Until that ships, some browsers and policy controls (particularly for managed Chromium environments) let you tighten the ceiling yourself.*
      • Treat browser hardening as a habit, not a one-off. A VPN will not save you from this one, because the leak is happening locally on your machine, not on the wire. Keep your attack surface small, do not leave sessions running indefinitely, do not blindly trust a tab from yesterday.*