Earlier quoted context omitted.
Can you give any more detail on how you did this? Is squid the proxy? How does it know which traffic is doh? What do you do with those requests?
Yes, I've installed my own cert to negotiate HTTPS connections, then proxy through software to check the contents being sent. Basically the same process that some companies use for similar purposes.
The FBI now recommends using an ad blocker when searching the web
391–400 of 445 posts
Re: The FBI now recommends using an ad blocker when searching the web
#392Earlier quoted context omitted.
Waiting for the day when augmented reality glasses let you block irl ads. Realistically it'll be the opposite first of course.
I think the technology is actually more or less there already. We just need a few enterprising individuals to come up with a polished device for that.
Re: The FBI now recommends using an ad blocker when searching the web
#393Earlier quoted context omitted.
The only "good" ads are those you have to specifically go out of your way to view because you want to view them; such as product catalogues. All other ads are physiological assault and should be made illegal. Particularly those ads which exist "IRL" and can't otherwise be blocked, such as billboards.
Waiting for the day when augmented reality glasses let you block irl ads. Realistically it'll be the opposite first of course.
Re: The FBI now recommends using an ad blocker when searching the web
#394Earlier quoted context omitted.
If there's any non-English-speaking culture that embraced IDNs, I'd love to hear it. E.g. in my experience as a Russian speaker, Cyrillic very rarely shows up in domain names for legitimate websites, and correlates strongly with malware.
The numbers agree. Only 69 Cyrillic domains (second-level) registered last year. Chinese is the most popular, but only 760 for 2022 and the aggregate trend is down: 2016: 2378 2018: 2252 2020: 1675 2022: 1518 Internationalized Domain Name (IDN) Annual Report 2022 [1] https://www.icann.org/en/system/files/files/idn-annual-repor...
Re: The FBI now recommends using an ad blocker when searching the web
#395Earlier quoted context omitted.
Why did you bother to register your phone then? I've used many smartphones and never registered any of them. I wouldn't give the time of day to Google or Apple let alone my personal details. Similarly, I use Firefox on Linux but I also regularly browse the web or post to HN on a phone that's been heavily deloused of Google using Firefox and other browsers—but never Chrome.
I've used many smartphones and never registered any of them. When I say register, I meant sign up for the wireless service. I did not already have an account. I was on my wifi and browsed to the wireless provider to activate my sim card and get a phone number. I could have done this on my PC but doing that on my cell verified with the vendor that my phone was supported since I am using an off-brand device. It was eas…
Re: The FBI now recommends using an ad blocker when searching the web
#396There are a lot of great addons that improve browsing immensely. I'll dump mine: * ublock origin: block ads * uBlacklist: block domains from Google search results * SponsorBlock: skip sponsored segments in youtube videos * Thumbnail Rating Bar for YouTube™: show a rating bar along the bottom of each YouTube search result * Firefox Multi-Account containers: Site storage segmentation * Bypass Paywalls Clean: bypass sit…
You have to get updates here: https://gitlab.com/magnolia1234/bypass-paywalls-firefox-clea...
Re: The FBI now recommends using an ad blocker when searching the web
#397Earlier quoted context omitted.
Except that it does not block first party ads by default (and also makes money by serving their own first party ads to users).
I don't see any ads. You can turn them off.
Re: The FBI now recommends using an ad blocker when searching the web
#398Earlier quoted context omitted.
I use uBlock Origin's element picker and element blocker features to just make the popup notices disappear, without accepting them. But that's mostly just a habit of mine that I know is pretty useless, as websites don't need cookies to track you, and I really don't know why they even bother anymore.
Try using the extension "I don't care about cookies" It's excellent. I have needed to disable it occasionally to make basic site functionality work on some sites that I absolutely need to use, though I'm forgetting which ones.
https://www.androidpolice.com/i-dont-care-about-cookies-acqu...
Re: The FBI now recommends using an ad blocker when searching the web
#399Earlier quoted context omitted.
I use uBlock Origin's element picker and element blocker features to just make the popup notices disappear, without accepting them. But that's mostly just a habit of mine that I know is pretty useless, as websites don't need cookies to track you, and I really don't know why they even bother anymore.
Try using the extension "I don't care about cookies" It's excellent. I have needed to disable it occasionally to make basic site functionality work on some sites that I absolutely need to use, though I'm forgetting which ones.
Re: The FBI now recommends using an ad blocker when searching the web
#400Earlier quoted context omitted.
While these are all good practices, killing DoH conclusively on your home network is more difficult than you've made it seem, as ultimately all you can really do is use domain blacklists at your firewall. It's no longer as straight forward as just control port 53 traffic, not like you can realistically shut down 443... Blocking DoH is largely whack-a-mole and I think is only going to get worse as this and similar tec…
DoH uses UDP, not TCP. Unless you're using HTTP3/QUIC, you can block port 443/UDP. And hey, maybe one day advertisements will be served directly via IP addresses, not domains:)
DoH is literally just "DNS over HTTPS" (hence the TCP a lot of the time) and you can build this a ton of different ways, including as a basic RESTful API. Local javascript on the page could literally just call any old HTTPS web API to get hostnames resolved, and thanks to HTTPS is much harder to detect, inspect and interfere with than traditional DNS. Fundamentally, a DNS request is a really basic API to implement.
This is why DoH is so hard to conclusively block - its by design to look like "normal" web traffic so bad actors are prevented from manipulating your DNS responses, and the implementation can be done pretty much anyway you want - there are a million different ways to pass a message over HTTPS, and to a firewall they all look like the exact same normal HTTPS traffic if you don't explicitly block the IP or domain serving the DoH.