Re:Glibc getaddrinfo stack-based buffer overflow
by rspeer on Tuesday February 16, 2016 @03:19PM
(#11112843)
Well, now, a lot of people are making containers, which are static linking turned up to 11.
I bet this bug will live on forever in people's Docker stacks.
Re:Glibc getaddrinfo stack-based buffer overflow
by peterwwillis on Tuesday February 16, 2016 @06:30PM
(#11113951)
The past four years of modern development practices have run screaming from the concept. Learning why the systems used to work they way they did was, like, super hard, so they reinvented the wheel and are running into the same problems that caused us to make shared libraries/COW/etc in the first place.
Re:Glibc getaddrinfo stack-based buffer overflow
by XorNot on Wednesday February 17, 2016 @03:20AM
(#11116205)
You've pretty fundamentally misunderstood them if you think immutable practices in anyway damage the ability to deploy fixes. Years of shared library hell is what causes things like this to go unfixed.
Re:Glibc getaddrinfo stack-based buffer overflow
by peterwwillis on Wednesday February 17, 2016 @06:25PM
(#11122406)
Immutability in software development & deployment is, for the vast majority of use cases, completely unnecessary. The only reason people talk about it now is everyone has a fetish over using simple software rather than designing software that works well.
And 'immutable practices' don't damage anything - they simply make things take longer, duplicate effort, make inefficient use of resources, and make everything generally more inflexible. The only benefit seems to be high level abstraction at the cost of everything else.
Re:Glibc getaddrinfo stack-based buffer overflow
by strictfp on Tuesday February 16, 2016 @03:40PM
(#11112968)
Nope, the pendulum is at it's other extreme. Go is going all in on static builds, docker containers freeze ALL THE THINGS \@/ and "immutable" package managers like Nix which in effect is like static linking without the speed benefits.
Re:Glibc getaddrinfo stack-based buffer overflow
by mentat on Tuesday February 16, 2016 @01:10PM
(#11111843)
That isn't it, see siblings here. You have to restart all processes that load glibc and interact with the affected services.
Re:Glibc getaddrinfo stack-based buffer overflow
by w8rbt on Tuesday February 16, 2016 @02:52PM
(#11112650)
Debian does this automatically and alerts the user what services are being restarted.
Re:Glibc getaddrinfo stack-based buffer overflow
by drummer32 on Tuesday February 16, 2016 @06:38PM
(#11113994)
It doesnt't. There's the needsrestart package that does this though.
Re:Glibc getaddrinfo stack-based buffer overflow
by muppetman on Tuesday February 16, 2016 @06:13PM
(#11113882)
I updated this morning and nothing got restarted. Shouldn't pretty much every network service I have gotten a restart? sshd, postfix, apache, icecast2, dovecot
None of them restarted. So I restarted them all myself...
Re:Glibc getaddrinfo stack-based buffer overflow
by yxhuvud on Tuesday February 16, 2016 @03:36PM
(#11112950)
Does libc even support static linking?
Re:Glibc getaddrinfo stack-based buffer overflow
by steveklabnik on Tuesday February 16, 2016 @03:40PM
(#11112970)
glibc is generally not statically linked. MUSL libc generaly is.
You _can_ statically link glibc, but then you lose some stuff. https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked...
This question had me feeling kind of old. Does nobody learn what shared libraries are anymore?