Sake Blok wrote:
> May I have your votes please? ;-)
>
> 1) Don't include the code at all
There are enough weak key identifiers out there without burdening
Wireshark with a CPU intensive test for a one off problem. The next time
someone finds a weakness it is bound to be a different problem needing
different discovery.
I don't want to have anyone in our networks using a version of Wireshark
with the ability to crack keys. It will panic the security people and
they will ban Wireshark totally. Wireshark it too useful to let that happen.
--
There's no point in being grown up if you can't be childish sometimes.
-- Dr. Who
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
https://wireshark.org/mailman/listinfo/wireshark-dev
