News for hackers. Stuff that matters.
Re:Glibc getaddrinfo stack-based buffer overflow by arielb1 on Tuesday February 16, 2016 @10:51AM (#11110622)
That's what you get when you have thousands of lines of code with variable names like `thisanssizp`. glibc should die in a fire.
Re:Glibc getaddrinfo stack-based buffer overflow by the_why_of_y on Tuesday February 16, 2016 @03:10PM (#11112774)
The DNS code in resolv/ is not formatted according to GNU coding style - you can tell by the sane placement of braces.

It's a fork of an ancient version of BIND.

  Starting with version 2.2, the resolver in the GNU C Library comes
  from BIND 8. 
https://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/READ...
Re:Glibc getaddrinfo stack-based buffer overflow by frign on Wednesday February 17, 2016 @03:01AM (#11116128)
Exactly. The mess glibc is is giving C a bad name. Look at the musl libc for how it should be done.