Re: Remove our bundled crypto library (in favor of Libgcrypt)?

[Guy Harris <guy () alum mit edu>]

On Feb 11, 2017, at 1:57 PM, Bálint Réczey <balint () balintreczey hu> wrote:

> +1 for going without a new layer of indirections.
> Making libgcrypt mandatory is easy and every level of indirection make
> understanding the code harder which is a source of bugs.

+1

Enough places in Wireshark use it, and there will probably be, over time, 1) more encryption in protocols and 2) more 
calls for Wireshark to do decryption whenever possible, so I consider it worthy of deeming an essential support library 
for packet analysis.

If you want a small tool to run on devices, put a *capture* tool there and do the *analysis* on something big enough to 
do the job.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe