John,
You do not need to run the configure script again if you're compiling from the same directory you have compiled from previously. Just edit the specified file(s), then run make clean (and it is make clean, not make clear - this removes previously compiled objects from your build directories) make (then change to superuser or other user able to install software on your system) make install If you do not stop and start BIND, you will have the same vulnerable binary running on your system that you had before the install. You'll need to stop named and start the updated binary for the source code changes you compiled to take effect on your system. -Rich ________________________________ From: bind-users-bounces+rgoodson=mediacomllc....@lists.isc.org [bind-users-bounces+rgoodson=mediacomllc....@lists.isc.org] on behalf of Manson, John [john.man...@mail.house.gov] Sent: Wednesday, March 27, 2013 2:56 PM To: bind-users@lists.isc.org Subject: FW: CVE-2013-2266 Question In the work around section of this notice, it talks about ‘make clear’ and editing a file statement. No problem with that. Does ‘make clear’ affect the running named or is it best to stop named and start it afterward? Do I also need to run configure again or just make? Will dig and rndc be updated as well? Thanks John Manson CAO/HIR/NAF Data-Communications | U.S. House of Representatives | Washington, DC 20515 Desk: 202-226-4244 | TCC: 202-226-6430 | john.man...@mail.house.gov<mailto:john.man...@mail.house.gov>
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
