Working on phasing the use of protobufs out of Kismet.
There's nothing wrong with them, per se, but it's becoming increasingly difficult to use them outside of a fully constrained environment - it might be fine if your code lives in a docker/k8s instance, but it's pretty miserable on any generic uncontrolled distro.
Between the google base code, protobufs-c, python protobufs, etc, it's not worth the pain.
Upside: protobufs is also one of the more obnoxious dependencies, so getting rid of it should definitely be worth the effort.
It'll probably take a while to get the new code written, still.
=> More informations about this toot | View the thread | More toots from kismetwireless@infosec.exchange
text/geminiThis content has been proxied by September (ba2dc).