3 ms·
> Ends up in test environment for, what, a month.. nothing using getaddrinfo from glibc is being used to test this environment or anyone noticed that it was bro
by bpt3 9mo ago
> Ends up in test environment for, what, a month.. nothing using getaddrinfo from glibc is being used to test this environment or anyone noticed that it was broken
This is the part that is shocking to me. How is getaddrinfo not called in any unit or system tests?
- SAI_Peregrinus 9mo agoProbably Alpine containers, so musl's version instead of glibc's.
- zinekeller 9mo agoAs black3r mentioned (https://news.ycombinator.com/item?id=46686096 https://news.ycombinator.com/item?id=46686096), it is likely rearranged by systemd, therefore only non-systemd glibc distributions are affected. I would hazard a guess that their test environment have both the systemd variant and the Unbound variants (Unbound technically does not arrange them, but instead reconstructs it according to RFC "CNAME restart" logic because it is a recursive resolver in itself), but not just plain directly-piped resolv.conf (Presumably because who would run that in this day and age. This is sadly just a half-joke, because only a few people would fall on this category.)
- WGH_ 9mo ago> it is likely rearranged by systemd, therefore only non-systemd glibc distributions are affected. systemd doesn't imply installed and running systemd-resolved though. I believe it's usually not enabled by default.
- zinekeller 9mo ago> I believe it's usually not enabled by default. Just verify modern OSes now, they definitely do mediate via systemd-resolver (including in server OSes).