mastodon 4.6.9MacPorts Developer, PPL/A, Works at Red Hat on Cryptography
searchable
So apparently #DEnic has messed up #DNSSEC records for .de, and essentially all resolutions of .de domains now randomly fail. For example, Google DNS just gave me "RRSIG with malformed signature found for 76b2e6birnkv6aekmcbtnl5i4qkbji6a.de/nsec3 (keytag=33834)" in a failure response. With caching, this is probably going to take a while.
I'm still not convinced DNSSEC is a net positive technology. The impact crater when somebody messes it up is just way too large.
CAPS_WORD is best Caps Lock. I have this configured on all my keyboards, and it's why I'm really looking closely at which manufacturers actually provide source code for #QMK and which ones are violating the license.
@ErikUden Yep, nothing you can do from your end.
If you're already running a local resolver, you can configure that to ignore DNSSEC for .de, e.g., for unbound:
server:
domain-insecure: "de"
but that isn't something you can tell non-tech people.
My team is looking for a US-based person to work making #PQC #SmartCards work with open source software. Says Raleigh, but remote will be considered when nobody can be found locally, which is likely:
#Crypto #cryptography #GetFediHired #FediHire
Note: don't complain to me if company decides to cancel the position in three days for reasons I don't understand.
