Re: RFC: a loadable plugin framework for external capture backends

[Robin Jarry via tcpdump-workers <tcpdump-workers () lists tcpdump org>]

> --- Begin Message ---
>
>
> From: "Robin Jarry" <rjarry () redhat com>
>
> Date: Mon, 05 Oct 2026 10:47:11 +0200
>
> Michael Richardson, Oct 05, 2026 at 08:28:
> > If it's effectively enabled by default, then it's an attack surface 
> > that maintainers have to pay attention to :-)
> > That's the point here.
>
> Of course, and I am not waiving that risk. We need to be extra careful 
> to minimize that attack surface.
>
> > One interesting possibility if current libpcap *is* just a plugin 
> > itself (as I think Bill Fenner suggested) and the plugin ABI *is* 
> > _libpcap2_ (or another name), then this offers a new way of doing 
> > pcap-write vs pcapng-write, and also allows the usb and other things 
> > to also be split out.
> >
> > Maybe there is a small number of helper functions that would remain in 
> > a libpcap. (and maybe that's a .a file only, because it's ~five small 
> > functions)
>
> If we can get a consensus, we could propose the initial plugin loading 
> system along with an example built-in backend (e.g. D-Bus) migrated to 
> use it.
>
> --
> Robin
>
> # Many suitcases look alike.
>
>
> --- End Message ---
_______________________________________________
tcpdump-workers mailing list -- tcpdump-workers () lists tcpdump org
To unsubscribe send an email to tcpdump-workers-leave () lists tcpdump org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s