I've upgraded wireshark 3.4 -> 3.6 and the protocol for sharkd has changed.
I am doing cat contrib/info.json | socat UNIX-CONNECT:/tmp/sharkd.sock - which returns
{"jsonrpc":"2.0","id":0,"error":`{"code":-32600,"message":"Invalid JSON(2)"}}`
I can't find how it is invalid.
for the following info.json:
{
"jsonrpc": "2.0"
, "id": 1
, "method":"info"
}
I've got a similar issue with the following json
{
"method":"load"
, "jsonrpc": "2.0"
, "id" : 1
, "params" : {
"file": "/home/teto/tcp/client_2_cleaned.pcapng"
}
}
NB: the doc at https://wiki.wireshark.org/Development/sharkd seems out of date
