rgoodson at mediacomllc.com
Wed Mar 27 20:09:13 UTC 2013
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
(and it is make clean, not make clear - this removes previously compiled objects from your build directories)
(then change to superuser or other user able to install software on your system)
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.
From: bind-users-bounces+rgoodson=mediacomllc.com at lists.isc.org [bind-users-bounces+rgoodson=mediacomllc.com at lists.isc.org] on behalf of Manson, John [John.Manson at mail.house.gov]
Sent: Wednesday, March 27, 2013 2:56 PM
To: bind-users at 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?
CAO/HIR/NAF Data-Communications | U.S. House of Representatives | Washington, DC 20515
Desk: 202-226-4244 | TCC: 202-226-6430 | john.manson at mail.house.gov<mailto:john.manson at mail.house.gov>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users