Hi, What about taking a step against the js audio fingerprint issue in Qubes? At this moment it beats all protection as this can fingerprint on hardware level, nearly on any OS.
Ref.: https://audiofingerprint.openwpm.com/ Example: visit twitter on your laptop through open internet, then visit twitter again without logging in through the same laptop, but Tails. Result is that twitter identify you based on the js audio fingerprint and knows it's the same computer. Note: if you want to test the fingerprinting throguh different virtual machines/tails/tor browser/etc, you better get the code from github and run for yourself. https://github.com/Valve/fingerprintjs2 -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/574C1256.7010705%40onenetbeyond.org. For more options, visit https://groups.google.com/d/optout.
