It would be a matter of getting this updated to work with the latest
wireshark. There's various changes to the SSL libs (opaque structures
and the like) that need a bit of a rework to get going, and there's the
wireshark API itself has changed since the way back.
Ideally the goal would be to get this incorporated into mainline because
this looks like a great tool for interoperability to get wireshark's DPI
capabilities from outside wireshark.
Unless you know of something similar, I think a good route forward is to
get sharktools working again. And my ultimate goal is to get Perl CPAN
Net::Sharktools working with the latest and greatest.
On 01/12/2018 05:55 PM, Roland Knall wrote:
What would you need to be worked on? The whole set or are you looking for a new maintainer?
Am 12.01.2018 um 23:45 schrieb Mark Murawski <[email protected]>:
Anyone interested in this if I posted a bounty?
On 01/09/2018 03:12 PM, Mark Murawski wrote:
Trying to post this for the third time. I adjusted the url that was maybe causing my post to get (silently) dropped.
Is there anyone who knows of an updated sharktooks that works with the latest wireshark (2.2+) ?
h t t p s github dot com /armenb/sharktools
I've contacted the author and haven't heard anything back yet. Is there someone who may be willing to help update sharktools to work with modern wireshark?
I've done a tiny little bit of porting work so far on it, but I still have a ways to go and I'm not familiar with the history/refactors that wireshark has gone through to really do a proper port. I'm getting a bit lost in the details.
Sent via: Wireshark-dev mailing list <[email protected]>
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-devmailto:[email protected]?subject=unsubscribe