pawal

The author merely suggests that those 29 or in someway trusted by a lot of people to handle DNS queries. Those 29 also publish information on what properties the service have. If you read the whole page, the author also lists other publi DNS resolvers worth a mention.

For the long tail of unknown open DNS resolvers, use Shodan. But I would not suggest that you use any findings from Shodan to trust your internet usage with.

Yes, SNI is a generic internet privacy problem. However, it is not a property of DNS. On the positive side, ECH has been pushed through the IETF and should slowly be available to the general user.

/ The author

Done, enjoy: https://evilbit.de/dns-resolver-guide.html#speedtest (DoH only)

Author here: Because of their continuing work on privacy, https://blog.cloudflare.com/1111-privacy-examination-2026/ However, as a EU citizen, I would not trust them anyway because of FISA 702.

Author here, I added this now: https://evilbit.de/dns-resolver-guide2.html#speedtest Only works for DoH though.

Interesting, but a Vectrex without a vector display is like a fish without water.

It seems like the development of SoftHSM2 has stalled quite a bit. There is still a lot of user interest, but very little action in terms of management of the project. There are many pull requests and issues raised by users, but very little in terms of taking care of those.

SoftHSM was originally developed as a PKCS#11 and HSM test platform for OpenDNSSEC, but later took on a life on itself. The reason for that is that there is a lot of need to use software that talks to Hardware Security Modules, but without actually spending the cash of buying one, mostly for development. But it has also become a cornerstone of a lot of other products, for example IBM Red Hat Identity Management.

NLNet Labs states in the GitHub issue linked: "Given the above, the current state is that development on SoftHSM v2 is dormant and not likely to pick up significantly in the near future. We are conferring as a team on how to proceed in the future, but this will likely take us until at least the summer of 2024."

So the future of SoftHSM does not look very great. Are there any organizations reading this willing to take up this challenge, and make the future of this small "insignificant" open source project great again?

Not if you want to deliver e-mail to Google, they recently added this as a requirement.

Me too. Still have a couple of books (in Swedish) on the subject. I don't have the heart to throw them away.

Yes, export regulations were heavy back then. To have proper SSL in your Netscape, you had to import this patch file from Australia. And then we had this whole Crypto Wars thing going on. Look at Steven Levy's excellent book on the subject, or search on the Wired archives.

There are a number of different tools for writing internet-drafts. See here: https://tools.ietf.org/tools/

The downside of this is that the lookup is done online, and every use of an individual is tracked per service. This is not something that I am comfortable with.

Yes, I use it often. My Debian installations use Tor for installing updates. Just as an example.

In practice internal only DNS names will always leak to external resolvers in one way or another. Pretending otherwise is very naive.

The problem I have with ^B is that the b is too far away from ctrl. A is much closer, which makes it a much faster one-hand press.

You should probably be more freaked out by your phone. It collects this data by default and sends it to Google or Apple. I think that Google still has an API for querying their database.

Is there a privacy friendly analytics tool that does not set cookies and store data Forever? I don't really care about perfect user analytics, just good enough. Maybe by analysing logs. In the 90's there was s lot of good tools like this, but now everybody has gone cloud. I can't imagine the tools offered today are compatible with GDPR.

Please go ahead and Read RFC4941.

A related project is https://cryptech.is, an open hardware HSM.

You bought a TLD when learning web development? That seems extreme.

Would you say the same thing about e-mail and SMTP?

Does this make you avoid reading very long books?

For a very long time, DNS simply has not been an identified risk for most corporations. In the risk analysis they make, DNS is not on the map at all, even though it may be a single point of complete collapse for them. Thus we see extremely large corporations depending on a single DNS provider, using a registrar that are more interested in profit rather than resilience against attacks, no DNSSEC. Etc etc. This is slowly changing. What is. Not changing fast enough is the ability to run more than one DNS provider, giving you yet another spof.

We should not "give up on BGP". What we should do is to improve security in all layers. This includes BGP, and as you mention DNS. DNSSEC should be mandatory, just as TLS, for any business that take themselves seriously.

Anybody looking forward to the captchas asking us to identify drone targets?

Nothing is going to happen. I have seen this several times now, and support does not lift one finger to give back the account to the original owner. Expect russian spambots to post images in a few weeks time.

Sony.

This reminds me of the Java Ring, that was almost 20 years ago.

Testing over really bad links should be done for a lot of sites out there.

DNS was designed so that you can have multiple operators for your authoritative name servers.

Who would have thought adding a spof to your infrastructure would ever be a problem?

If you want to keep secrets, publishing them in DNS is the wrong place for it.