> We aren't going to do anything - see Bruce's earlier comment. > > For older systems which are in use, apply the standard LFS method: > use it to build an up-to-date one. I hope you created scripts for > what you have so far built, so you will only have to check for > altered deps/build order, and review the individual commands.
Didn't see the earlier comment from Bruce. I think what I'm going to do is fetch glibc-2.17 & 2.18, isolate that one function at fault, __nss_hostname_digits_dots, run a diff, and compare the result with Qualys' very thorough analysis for other changes that might introduce incompatibilities. Then I'll inspect that function in my older versions of glibc and see if it fits--it should, with a little fuzz perhaps. Then I can rerun my build scripts with the patch. I have several older, functional systems I want to keep around, including this 6.6 I'm using now. Their analysis suggests this isn't as severe as Heartbleed or Shellshock, and exim is the fallguy they identify. I'll also update exim. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - Does exactly what it says on the tin -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
