On Feb 8, 2017, at 3:18 PM, Peter Wu <peter@xxxxxxxxxxxxx> wrote:
> On Wed, Feb 08, 2017 at 10:51:29AM -0800, Guy Harris wrote:
>> On Feb 8, 2017, at 5:40 AM, Peter Wu <peter@xxxxxxxxxxxxx> 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:
https://mta.openssl.org/pipermail/openssl-users/2015-January/000295.html
or that libgcrypt caused on Windows at one point:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3270
I remember some issue such as this coming up somewhere in Wireshark, but it might have been bug 3270.
