Reply to thread

Message

<blockquote data-quote="Lenny_Fox" data-source="post: 839127" data-attributes="member: 82776">In my minor IT-security this was an interesting discussion, that enhanced security always comes with the cost of lesser privacy, because you can&#039;t have one with out the other (remember the song love &amp; marriage: the URL has to be sent to server to check whether it is safe or not <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> ).The loss of privacy depends whether the URL is hashed or not and whether the check is on domain level or page levelWhen the URL is not hashed knowing on (visited) page level provides more insights in the users preferences, for instance when my extension knows that I often visit:Justanotherporndomain/tinyteens a lot and Consumergoodsportal/sextoys provides different insights as knowing I visit justanotherpornsite and consumergoodsportalSo the conclusion we draw: use the browsers build-in safety feature (and when using Chrome or Chromium based browser) use the site preferences settings for javascript to block javascript and allow only HTTPS://*&nbsp; (as explained by several members on this forum often). When you use an extension which supports adblock plus format, you could also add 1 line to implement that for third-party connections (||*^$third-party,~stylesheet,~image) as often advocated by user Windows_Security).As pointed out often on this forum 80 to 90 percent of the malware and phishing domains are from HTTP websites and 99% of the self respecting legal websites are on HTTPS nowadays.</blockquote>

[QUOTE="Lenny_Fox, post: 839127, member: 82776"] In my minor IT-security this was an interesting discussion, that enhanced security always comes with the cost of lesser privacy, because you can't have one with out the other (remember the song love & marriage: the URL has to be sent to server to check whether it is safe or not :) ). The loss of privacy depends whether the URL is hashed or not and whether the check is on domain level or page level When the URL is not hashed knowing on (visited) page level provides more insights in the users preferences, for instance when my extension knows that I often visit: Justanotherporndomain/tinyteens a lot and Consumergoodsportal/sextoys provides different insights as knowing I visit justanotherpornsite and consumergoodsportal So the conclusion we draw: use the browsers build-in safety feature (and when using Chrome or Chromium based browser) use the site preferences settings for javascript to block javascript and allow only HTTPS://* (as explained by several members on this forum often). When you use an extension which supports adblock plus format, you could also add 1 line to implement that for third-party connections (||*^$third-party,~stylesheet,~image) as often advocated by user Windows_Security). As pointed out often on this forum 80 to 90 percent of the malware and phishing domains are from HTTP websites and 99% of the self respecting legal websites are on HTTPS nowadays. [/QUOTE]

Verification