Wireshark-dev: Re: [Wireshark-dev] Remove our bundled crypto library (in favor of Libgcrypt)?
From: Guy Harris <[email protected]>
Date: Sat, 11 Feb 2017 12:22:19 -0800
On Feb 8, 2017, at 3:18 PM, Peter Wu <[email protected]> wrote:

> On Wed, Feb 08, 2017 at 10:51:29AM -0800, Guy Harris wrote:
>> On Feb 8, 2017, at 5:40 AM, Peter Wu <[email protected]> wrote:
>>> I did not expect Libgcrypt to consume entropy when it is just doing
>>> decryption.
>> I'm concerned with consuming CPU and wall-clock time - i.e., slowing *shark startup - not entropy.
> Could you clarify this concern? I did not observe an attempt by
> Libgcrypt to obtain entropy at startup

Good!  That means that libgcrypt won't cause this sort of problem that OpenSSL causes:


or that libgcrypt caused on Windows at one point:


I remember some issue such as this coming up somewhere in Wireshark, but it might have been bug 3270.