From robin at corelight.com  Tue Feb  4 04:18:39 2020
From: robin at corelight.com (Robin Sommer)
Date: Tue, 4 Feb 2020 12:18:39 +0000
Subject: [Zeek-Dev] Wrapping up 3.1
Message-ID: <20200204121839.GB75872@corelight.com>

We're planing to wrap up Zeek 3.1 this week with code freeze on Friday
and then a beta version out early next week. The 3.1.0 GitHub project
shows the current state, please make sure we have tickets on there for
everything that's critical to still go in.

Please all take a look at master's NEWS to see if it mentions
everything we should point us. I'm also planing to take that as the
starting point for a blog posting announcing 3.1.

Robin

-- 
Robin Sommer * Corelight, Inc. * robin at corelight.com * www.corelight.com

From dnj0496 at gmail.com  Thu Feb 13 17:54:58 2020
From: dnj0496 at gmail.com (Dk Jack)
Date: Thu, 13 Feb 2020 17:54:58 -0800
Subject: [Zeek-Dev] 2.4.1 to 3.0.1
Message-ID: <CAGATen7cKrKwm+t5rZOAkd5Un6+-QYrtWiP2ReksJ50-=_aVZw@mail.gmail.com>

Hi,
We have a (c++) plugin that we have been using with 2.4.1. We are
trying to move to 3.0.x. Is there any documentation on api changes
(deprecations) that we need to be concerned about? Our plugin is an
analyzer deriving from tcp::TCP_ApplicationAnalyzer. Any guidance is
appreciated. Thanks.

Dk.

From tim at corelight.com  Fri Feb 14 08:51:08 2020
From: tim at corelight.com (Tim Wojtulewicz)
Date: Fri, 14 Feb 2020 09:51:08 -0700
Subject: [Zeek-Dev] 2.4.1 to 3.0.1
In-Reply-To: <CAGATen7cKrKwm+t5rZOAkd5Un6+-QYrtWiP2ReksJ50-=_aVZw@mail.gmail.com>
References: <CAGATen7cKrKwm+t5rZOAkd5Un6+-QYrtWiP2ReksJ50-=_aVZw@mail.gmail.com>
Message-ID: <DFC98057-8BA3-499F-A950-28B3FEDC01CB@corelight.com>

All of the deprecations listed in 3.0.1 will return compiler warnings if you use them in your code, but will still function correctly. The deprecations aren?t actually removed until 3.1, at which point using them will cause failures. That said, if you run into anything with any of the deprecations, let us know and we can help work through them.

Tim

> On Feb 13, 2020, at 6:54 PM, Dk Jack <dnj0496 at gmail.com> wrote:
> 
> Hi,
> We have a (c++) plugin that we have been using with 2.4.1. We are
> trying to move to 3.0.x. Is there any documentation on api changes
> (deprecations) that we need to be concerned about? Our plugin is an
> analyzer deriving from tcp::TCP_ApplicationAnalyzer. Any guidance is
> appreciated. Thanks.
> 
> Dk.
> _______________________________________________
> Zeek-Dev mailing list
> Zeek-Dev at zeek.org
> http://mailman.icsi.berkeley.edu/mailman/listinfo/zeek-dev



From dnj0496 at gmail.com  Fri Feb 14 09:48:11 2020
From: dnj0496 at gmail.com (Dk Jack)
Date: Fri, 14 Feb 2020 09:48:11 -0800
Subject: [Zeek-Dev] 2.4.1 to 3.0.1
In-Reply-To: <DFC98057-8BA3-499F-A950-28B3FEDC01CB@corelight.com>
References: <CAGATen7cKrKwm+t5rZOAkd5Un6+-QYrtWiP2ReksJ50-=_aVZw@mail.gmail.com>
	<DFC98057-8BA3-499F-A950-28B3FEDC01CB@corelight.com>
Message-ID: <33779BE4-B7BB-4F3A-8722-F79AB7B9A297@gmail.com>

Thanks Tim,
Thanks to those compiler warnings, I took care of mpg them. That was ver nice. 

However, I have seen EnableHook being used in some of the newer plugins. My plugin seems to compile fine and rudimentary testing shows it seems to work fine as well. Where can I know more about the APIs purpose and use? Are there any other new APIs that are newer and correct ways of interacting with zeek? 

Thanks again for taking the time for responding to my query. 

Dk. 

> On Feb 14, 2020, at 8:51 AM, Tim Wojtulewicz <tim at corelight.com> wrote:
> 
> All of the deprecations listed in 3.0.1 will return compiler warnings if you use them in your code, but will still function correctly. The deprecations aren?t actually removed until 3.1, at which point using them will cause failures. That said, if you run into anything with any of the deprecations, let us know and we can help work through them.
> 
> Tim
> 
>> On Feb 13, 2020, at 6:54 PM, Dk Jack <dnj0496 at gmail.com> wrote:
>> 
>> Hi,
>> We have a (c++) plugin that we have been using with 2.4.1. We are
>> trying to move to 3.0.x. Is there any documentation on api changes
>> (deprecations) that we need to be concerned about? Our plugin is an
>> analyzer deriving from tcp::TCP_ApplicationAnalyzer. Any guidance is
>> appreciated. Thanks.
>> 
>> Dk.
>> _______________________________________________
>> Zeek-Dev mailing list
>> Zeek-Dev at zeek.org
>> http://mailman.icsi.berkeley.edu/mailman/listinfo/zeek-dev
>