I struggle to find if it uses DNSSEC or even a change log. If it does, contact the maintainer and disable DNSSEC (if you can) until a fix is released.
I struggle to find if it uses DNSSEC or even a change log. If it does, contact the maintainer and disable DNSSEC (if you can) until a fix is released.
They maintain their own resolver, so they have to patch it if not done already.
It’s the latter. Unless you run your own DNS resolver, most people are safe
I’m not familiar with off-the-shelf DNS filtering on mobile, but since running a DNS resolver on-device would be impractical, I think they must be using a DNS server that they maintain. Which means that unless I’m wrong, the vulnerability lies on their end, you should be fine.
Exactly, I don’t get the “Mastodon as a poor man’s RSS agregator” trend
TrueNAS SCALE as host with an Ubuntu LTS VM running Docker containers.
Original I went with only containers running on top of SCALE but both iX and TrueCharts made it harder to run plain Docker Compose on TrueNAS.
Someone should create a leaderboard of websites sharing data with the most “partners”, this week I saw someone on Mastodon posting a screenshot of a website sharing to 1700+ third-parties.
It was already bad enough when they advertised for their own shows at the beginning of episodes…
Anyway, I stopped subscribing to Prime years ago, didn’t want to give my money to Amazon unless I have no other place to purchase some items.
And replace them with walled-garden devices that don’t allow you to do anything besides a restricted set of uses defined by manufactures and right holders.
If you use a third-party’s DNS server (such as Cloudflare, Quad9 or Google) as your upstream DNS server, you only have to update PiHole.
If you have set up your own upstream DNS server using a DNS resolver like unbound or Bind9, update it as well as your PiHole.