Reply to thread

Message

<blockquote data-quote="HarborFront" data-source="post: 919148" data-attributes="member: 55987">Some info on QUIC here[URL unfurl=&quot;true&quot;]https://security.stackexchange.com/questions/122361/is-quic-quick-udp-internet-connections-safe-to-allow-through-firewall[/URL][URL unfurl=&quot;true&quot;]https://www.fastvue.co/fastvue/blog/googles-quic-protocols-security-and-reporting-implications/[/URL][URL unfurl=&quot;true&quot;]https://ma.ttias.be/googles-quic-protocol-moving-web-tcp-udp/[/URL]The question is should one enables QUIC in the browser despite the slight performance it gains over privacy issue and does your firewall inspect QUIC traffic?Quote from commentThe ‘QUIC’ protocol (Google originated BTW) appears to be insecure against webtracking by commercial as well as govt. trackers &amp; surveillance. A user/browser may be (passively) uniquely tracked across a browsing session (and possibly across multiple sessions in some instances), without the need for cookies, other trackers, or fingerprinting, according to a recent University of Hamburg paper:<a href="https://content.sciendo.com/downloadpdf/journals/popets/2019/3/article-p255.pdf" target="_blank">https://content.sciendo.com/downloadpdf/journals/popets/2019/3/article-p255.pdf</a>Thus, probably best not to enable this in your browser if you are privacy-minded, until this hole is patched … (I haven’t been able to find any mention that browser vendors have even addressed this to-date)QUIC has already been enabled in Chrome for quite some time, surprise, surprise (Google builds in yet another hidden, powerful privacy-shredding tracker into its next-generation web technology and as well as its 60%-market-share-browser?? There’s a shocker for ya…)You can disable this in most Chromium-based browsers, tho’, and/or otherwise at your OS firewall:<a href="https://www.bitdefender.com/support/how-to-disable-quic-protocol-in-google-chrome-1669.html" target="_blank">How to disable QUIC protocol in Google Chrome</a>Unquote</blockquote>

[QUOTE="HarborFront, post: 919148, member: 55987"] Some info on QUIC here [URL unfurl="true"]https://security.stackexchange.com/questions/122361/is-quic-quick-udp-internet-connections-safe-to-allow-through-firewall[/URL] [URL unfurl="true"]https://www.fastvue.co/fastvue/blog/googles-quic-protocols-security-and-reporting-implications/[/URL] [URL unfurl="true"]https://ma.ttias.be/googles-quic-protocol-moving-web-tcp-udp/[/URL] The question is should one enables QUIC in the browser despite the slight performance it gains over privacy issue and does your firewall inspect QUIC traffic? Quote from comment The ‘QUIC’ protocol (Google originated BTW) appears to be insecure against webtracking by commercial as well as govt. trackers & surveillance. A user/browser may be (passively) uniquely tracked across a browsing session (and possibly across multiple sessions in some instances), without the need for cookies, other trackers, or fingerprinting, according to a recent University of Hamburg paper: [URL]https://content.sciendo.com/downloadpdf/journals/popets/2019/3/article-p255.pdf[/URL] Thus, probably best not to enable this in your browser if you are privacy-minded, until this hole is patched … (I haven’t been able to find any mention that browser vendors have even addressed this to-date) QUIC has already been enabled in Chrome for quite some time, surprise, surprise (Google builds in yet another hidden, powerful privacy-shredding tracker into its next-generation web technology and as well as its 60%-market-share-browser?? There’s a shocker for ya…) You can disable this in most Chromium-based browsers, tho’, and/or otherwise at your OS firewall: [URL='https://www.bitdefender.com/support/how-to-disable-quic-protocol-in-google-chrome-1669.html']How to disable QUIC protocol in Google Chrome[/URL] Unquote [/QUOTE]

Verification