ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] performing cpu/time intensive computation in a protocol diss

From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Thu, 7 Aug 2008 15:12:24 +0200
On Thu, Aug 07, 2008 at 01:30:25PM +0200, Sake Blok wrote:
> > You could leave the code in there, and have an 'identify weak keys' menu 
> > option.
> > 
> > But at present I'm changing my vote to 1) Don't include the code at all.
> 
> All considering, I vote for 1) as well.

I still strongly prefer 2) (optionally identify)

 ciao
     Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.