Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20524 - [glibc] gethostbyname() cant resolve names starting/ending with "-"
Attached to Project:
Arch Linux
Opened by Thomas Dy (stoichyu) - Thursday, 19 August 2010, 19:57 GMT
Last edited by Allan McRae (Allan) - Saturday, 11 September 2010, 04:54 GMT
Opened by Thomas Dy (stoichyu) - Thursday, 19 August 2010, 19:57 GMT
Last edited by Allan McRae (Allan) - Saturday, 11 September 2010, 04:54 GMT
|
DetailsDescription:
This bug is the same as https://bugs.launchpad.net/glibc/+bug/144431 The gist of it is that domain names starting or ending with a "-" do not resolve but they are do resolve in Windows and Mac OS X. An example given in the other bug report is "-kol.deviantart.com" Upstream does not seem to want to fix it from what I gathered in the other bug report. The fix was relatively easy, though. I just followed comment #9's instructions and everything seems ok. I have attached a patch file that fixes the problem. Rant: Strangely, in the README file, they admit to allow underscores in domain names which I haven't seen at all. So I don't see why they can't just allow hyphens. |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 11 September 2010, 04:54 GMT
Reason for closing: Upstream
Additional comments about closing: Waiting on upstream decision
Saturday, 11 September 2010, 04:54 GMT
Reason for closing: Upstream
Additional comments about closing: Waiting on upstream decision
glibc-resolv.patch
Drepper's comment will prevent me from applying this patch until there is some upstream agreement:
"Plus, this could have unwanted effects. If somebody makes a mistake when specifying a host name a parameter might be mistaken for it. This might even be exploitable."
Anyway, is getting upstream to fix this the only way this will ever be patched?
Also, it is Arch policy to never apply patches rejected by upstream. See the final point here: http://wiki.archlinux.org/index.php/DeveloperWiki:Patching