So I was up early this morning and counting packets didn’t help. I was thinking of what we do here at Mu and how testing requirements have dramatically changed over the last few years. This blog is an ode (well it doesn’t rhyme) to the most awesomest testing product created by the Mu team.
Archive for February 2010
Announcing xtractr – unleash the power of packets
At Mu, we deal with pcaps every day. We love Wireshark. We decode packets, work with protocols, auto generate test cases (functional to fuzz) from pcaps by analyzing the contents and just have incredible amounts of fun solving major problems for our customers. Yet when it comes to replicating field issues, most of our customers struggle with large pcaps and try to get a bird’s eye view of what’s in it to pinpoint the conversation or packet that triggered a bug. This takes hours if not days. With Mu Studio, it’s super easy to load a multi-protocol transaction and use it as the basis for testing – from functional to fuzz. But how do you find the suspicious transaction or conversation from the large pcap before you can test?
