Earlier quoted context omitted.
The trick to asn.1 is to generate both parser and serializer from the spec. Elliptic curve math on the other hand is ... yeah, you need to know the math and also know the tricks to code that implements it. Both of those have steep learning curve, but it's hardly because it's a mess or it's old.
The problem with ASN.1 is that it is big and complicated, and you only need a fraction of it for cryptography, and it isn't really used for anything outside of pki anymore. It wouldn't be as bad if asn.1 had cought on more as a general purpose serialization format and there were ubiquitous decent libraries for dealing with it. But that didn't happen. Probably partly because there are so many different representations…
DNSSEC disruption affecting .de domains – Resolved
331–340 of 440 posts
Re: DNSSEC disruption affecting .de domains – Resolved
#332Earlier quoted context omitted.
Yeah just ignore the big "not secure" warning in the URL bar
I just checked it. You mean the very small open padlock icon? The era of browsers warning loudly about HTTP was a decade ago, it got reversed due to pushback.
Re: DNSSEC disruption affecting .de domains – Resolved
#333Earlier quoted context omitted.
> The internet's famous "routing around damage" ...is only for Pentagon networks and military stuff. It's not for us normal people. (We get Cloudflare and FAANG bullshit instead.)
This is actually startlingly true. Every FAANG company has their own fiber backbone. Why invest the internet that everyone uses when you can invest in your own private internet and then sell that instead?
Traffic that goes over "the Internet" traverses some mix of your ISP's fiber, fiber belonging to some other ISP they have a deal with, then fiber belong to some ISP they have a deal with, etc.
All those ISPs are being paid to provide service, they can invest in their own networks.
Re: DNSSEC disruption affecting .de domains – Resolved
#334Earlier quoted context omitted.
> Yeah it's only the third largest economy in the world You can both be the 3rd biggest economy in the world and still only be 1/10th of US+China GDPs combined. And only three companies in the Top 100 for Germany: https://companiesmarketcap.com/ Germany is the kingdom of the "mittelstand": many, many, many SMEs. Both GP and you are right: it's the 3rd largest economy in the world and yet it's simply not that big. htt…
How is 1/10th the size of number 1 and 2 COMBINED small? In what world is that a small number? Especially as those two are 1.8 billion people vs 0.08 billion for Germany
Re: DNSSEC disruption affecting .de domains – Resolved
#335Earlier quoted context omitted.
Not sure if serious or /s
Almost certainly /s. "Danke Merkel" ("Thanks Merkel") was once a sincere criticism from conservatives regarding her policies (esp. during 2015 refugee crisis), but it quickly evolved into a sarcastic, deadpan joke used to blame her for literally anything that goes wrong in daily Germany - even years after she left. Interesting phenomenon...
Re: DNSSEC disruption affecting .de domains – Resolved
#336Earlier quoted context omitted.
You're wrong. Both .com and .net are signed (`dig RRSIG com.`), and if they screw up, then all the com/net zones will become inaccessible.
Virtually no zones under .com/.net are signed, which was the only point I was making. It has no adoption here.
Re: DNSSEC disruption affecting .de domains – Resolved
#337Earlier quoted context omitted.
Not sure if serious or /s
Almost certainly /s. "Danke Merkel" ("Thanks Merkel") was once a sincere criticism from conservatives regarding her policies (esp. during 2015 refugee crisis), but it quickly evolved into a sarcastic, deadpan joke used to blame her for literally anything that goes wrong in daily Germany - even years after she left. Interesting phenomenon...
Re: DNSSEC disruption affecting .de domains – Resolved
#338Re: DNSSEC disruption affecting .de domains – Resolved
#339Earlier quoted context omitted.
If there's going to be a single point of failure in front of your website, that single point of failure may as well be the only single point of failure instead of having two single points of failure, and it's probably important that people can't spoof responses.
Nobody had to hack it. A system at DENIC broke, and so Cloudflare turned off DNSSEC validation for all of their users accessing .de. If DNSSEC was actually important for the security model of those users, that would be a huge deal.
Beyond that, DNS has the AD bit. If you need DNSSEC secure data (for example for the TLSA record), then when Cloudflare turns off DNSSEC validation, the AD bit will be clear and things will stop working.
Re: DNSSEC disruption affecting .de domains – Resolved
#340Crazy. I can't remember an incident like this ever happened before and it's still not fixed? .de is probably the most important unrestricted domain after .com from an economical perspective. Millions of businesses are "down".