TCP session parsing storage has evolved for the second time.
The first time was to be able to have TCP sessions with thousands of HTTP communications inside: I had to remove the list of items from the parsing block.
This time was to be able to have parallel parsing of TLS and HTTP (or another) protocol without risking concurrency update.
July release comes with 1 major feature and some bug fixes:
To reduce Whisperers resource usage, and to be able to introduce new features afterward, I wanted to migrate Whisperers from
Node.js to a native language.
Trendy languages for this kind of work are Go and Rust.
Go being more used in Kubernetes ecosystem, and having a nice ecosystem, I decided to go for Go 馃槈!
May release comes with 3 major features and many UX improvements:
With Spider being deployed in the US, and soon, in Australia, Spider needed a way to display communications times in the timezone of the capture rather than the user's one.
It is now possible:
Selecting a Whisperer now automatically switch Spider UI to its own timezone! 馃挭
While adding TCP content decode plugin, I took the occasion to close some roadmap tickets on TCP details panel!
Spider introduces a new plugin slot to decode TCP payloads directly in the UI!
No need to download the payload in Wireshark anymore. You may directly decode any protocol, even your own, in Spider UI.
Initializing Whisperers was requiring to go in many tab at first:
Status tabINTERFACE or UPLOAD in Capture tabTo make things simpler, I added a short Create Whisperer Form to set the main
settings of the Whisperer to create in a single space.
April release comes with 2 major features:
Ever wanted to keep some Whisperer data longer than others?
Spider introduces Data Storage Policies to achieve this 馃槏!