If you generally had "search example.com" in you resolv.conf, and were in the habit of having "web01.dev" in places, behaviour may have changed if you were happen to be on a machine that had the "search" line missing (or something else).
So if you generally had "search example.com" in you resolv.conf, and were in the habit of having "web01.dev" in places, behaviour may have changed if you were suddenly on a machine that had the "search" line missing (or something else).
> Then use a wildcard so none of leaks into cert transparency logs
You now also have to build infrastructure to distribute the wildcard from (presumably) central place where you generate it to all the different places where it is desired.
And hope the wildcard's private key does not leak from one of myriad of places it now lives.
So if "example.com" is control by Corporate IT, and they don't want 'random' folks fiddling with it, then you can create a "dnsauth.example.com" and point the dns-1 challenge record from "…foo.example.com" to "foo.dnsauth.example.com" (or a completely different domain, like "…example.net").
There are DNS servers written strictly focused on this use case:
Which could (maybe) be fine if they could be permanently turned off (and not reset-to-on on every startup). Heck, even if it was a dealership-only change it would be something.
See recent driving 4 answers video on the silliness of some of these features:
An alert that causes you to look down every time to enter an intersection/roundabout when you most need to be looking up? Warnings when you put on sunglasses?
"Probably not, but then my job is to celebrate and defend the wonders of British democracy. And look at this: the fact that you're interviewing me, on the Today program, because all the other parties are not standing [up candidates] says more about them than it does about me."
I have a manual 2003 Golf TDI (purchased in 2003; has a tape deck!) that's slowly rusting, and I'm not looking forward to when I have to replace it.
I don't have a garage/drive way, and so have to park on the street, which makes me leans towards another short [1] vehicle: currently thinking about VW Golf, Mazda 3, Mazda CX-30, Kia Niro.
From what I've seen from almost all cars, lots more screens and lots fewer buttons.
I have gotten flack for giving ULA+NPTv6 as a possible solution to an IPv6 multi-homing issue because the RFC that describes it was 'only' "Experimental":
> “People are already doing it, so we might as well rubber-stamp it even if it’s not great” introduces problems of its own: people will perceive that rubber-stamping as validating it, and now they’ll use it even more, where perhaps if you held back, they wouldn’t.
The GOST cipher, which is Russia's AES equivalent, is also in an RFC:
The GOST document is categorized in the same way as the one currently being debated/discussed: Informational. It also has "N" under the "Recommended" column (like ML-KEM-only will have):
Further the draft that this is all about does not make a recommendation for its use. The currently IETF-recommended TLS algorithms are: X25519MLKEM768, x448, x25519, secp384r1, secp256r1.
As noted by someone on the IETF list [1] there are already ML-KEM-only implementations in various libraries, so if we want interoperability then it's best to have a standard document. No one is forcing anyone to use this algorithm, and it's not even 'officially' recommended (per above).
While there are 365 days in a (non-leap) year, live trading days are fewer:
> Trump averaged 85 trades per market day, an analysis of the report shows. Just 10 days accounted for about a quarter of all trades executed in 2025. Many of those came during heightened volatility on Wall Street after Trump had already announced policy changes.
> But to just state that "Life is so much better in 2026 than in 1926 for Americans" is obviously a pretty nebulous statement.
Given that there was no antibiotics in 1926, no chemotherapy or radiation therapy for cancer, no public pensions (so good luck getting old), hardly any indoor plumbing (even by 1940 it was about half), I think life is much better now that one hundred years ago.
What were infant mortality rates in 1926? Maternal mortality? Average life span? How many years did people live after retirement?
Can you list the ways in which you think life was better in 1926?
And to say life is better now is not to say it's perfect or to deny that improvements can still be made.
> I can't speak for 1926, but compared to 1980s or 1960s, this is so patently not true. The US population is much sicker and more obese, as one example.
If you're a woman, would you rather live in the 1960s or 2020s? If you were black or any other minority, in the 1960s or 2020s? If you're gay, would you rather live in the 1960/80s or in the 2020s?
Average US life expectancy was in about 70 in the 1960s, and mid-70s in the 1980s, and approaching 80 until COVID hit. Cancer survivorships has improved (not only because better screen and treatment, but also because of less cigarette smoking). The infant mortality rate now is a fifth of what it was in the 1960s.
Of course for all these numbers non-US developed countries are much better.
Generally, to say that life is better now is not to say it's perfect or to deny that improvements can still be made.
> People are not starving, but at the cost of eating "manufactured" foods that will make them sick in 20 - 40 yrs.
Groceries have gone from being 14% of household spending in the 1960s to being less 6% (takeout from 4% to 6%). In 1900 food was 40%:
Pure, non-hybrid implementations of ML-KEM (FIPS 203, previously "Kyber") are already in the major crypto libraries. So given code is being written, there can either be an IETF document available to ensure interoperability or not: the IETF would prefer interop it seems.
The list of IETF-recommended TLS algorithms can be found under the (sortable) "Recommended" column of officially registered TLS parameters:
That won't prevent me from getting a ticket saying "the network is down".