On Thu, Feb 28, 2019 at 11:35 +0100, Jan Grashöfer wrote:
> The question here would be whether LL-analyzers have to be linked
> dynamically.
Well, the point of the plugin API is being able to add new
functionality externally through an independently compiled shared
library. Excluding link-layer
On Wed, Feb 27, 2019 at 16:07 +0100, Jan Grashöfer wrote:
> At first glance it looks like IP-layer multiplexing is done in
> NetSessions::{NextPacket, DoNextPacket} and the Transport-layer is tackled
> in Manager::BuildInitialAnalyzerTree in context of initializing a
> connection.
Well,
On 26/02/2019 02:36, Robin Sommer wrote:
> I see three pieces here overall that I think can be tackled
> independently:
>
> (1) Link-layer: Currently hardcoded in Packet::ProcessLayer2()
>
> (2) IP-Layer: Currently hardcoded in NetSessions::NextPacket()
>
> (3) Transport-layer: Currently
Hi everyone,
I am researcher in KIT where I’m also doing my PhD. I had the chance to meet
some of you in the last (well first) Bro Europe workshop.
My research work is focused on the cyber-physical security of communication
networks of substations based on IEC 61850. Thus, I was wondering if I
