No idea what’s in master. It should be trivial if you don’t remove the dhcp analyzer completely.
> On Jun 16, 2018, at 6:07 AM, Vlad Grigorescu <v...@es.net> wrote: > > Yep, already working on it. :-) > >> On Sat, Jun 16, 2018 at 6:26 AM, Seth Hall <s...@corelight.com> wrote: >> >> On 15 Jun 2018, at 17:22, Azoff, Justin S wrote: >> >> > The fix is a little trickier, you can't handle both events because the >> > DHCP::Msg type no longer exists and you need to wrap the old event >> > with >> > >> > @ifdef (DHCP::Msg) >> > @endif >> >> Ugh, I didn't consider that. Bro has re-reached the point where >> touching any number of things can set off an avalanche of problems like >> this. >> >> Anyone on this thread up for submitting a patch which makes Bro cope >> with the changes automatically? You can then even mark the old events >> as deprecated. :) >> >> .Seth >> >> -- >> Seth Hall * Corelight, Inc * www.corelight.com >> _______________________________________________ >> bro-dev mailing list >> bro-dev@bro.org >> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev > > _______________________________________________ > bro-dev mailing list > bro-dev@bro.org > http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
_______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev