October release comes with 1 major feature and various bug fixes:

• Spider now captures TLS secrets live and deciphers TLS encrypted communications: HTTPS, MQTTS, secured DB connections...

I am thrilled to announce a major milestone for Spider: TLS encrypted communication deciphering is now available! 🚀

This release represents a significant leap forward in achieving comprehensive observability for all your communications.

I dreamed of making this possible, and here it is—after a lot of intricate engineering, it's finally a reality! 😀

All 43 microservices and UIs have been upgraded to Node 20 and Alpine 3.20, with latest security fixes. 💪

Since the introduction of new Whisperers agents in Go, these Gossipers have proven reliable, extremely stable and no known bugs is left pending.
They even offer a simpler setup with standalone executables.

Nodes.js Whisperers are thereby officially deprecated, and TLS deciphering has only been implemented in Gossipers.

For years, Spider has been able to parse a second time TCP sessions

• For which Packets, TCP sessions and Parsing log was saved in Elasticsearch
• For which some Packets have been missing when parsing

I've decided to remove this feature as:

• Most often Packets and Tcp sessions are not saved anymore
• Streaming parsing quality is now excellent
• It was one useless service flying around in the cluster

This parsing step has then been removed from the deployed cluster, the configuration and documentation!

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:

• Gossiper Go agent to replace Whisperer Node.js agents

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:

• Whisperer creation form
• TCP payload UX improvements & decoder plugins
• Timezone management

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:

• User may define its default timezone
• And Whisperers may each be associated to their own timezone

Selecting a Whisperer now automatically switch Spider UI to its own timezone! 💪