Wireshark-bugs: [Wireshark-bugs] [Bug 11371] DTLS decryption failing on Ubuntu buildbot
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 16 Jul 2015 20:21:06 +0000

Comment # 1 on bug 11371 from 
The last passing build was using commit c8c8eefb47ad, so one of the following
triggers a DTLS failure (which is not reproducible here):

commit 85f8a99f354850d5fbf774b04e9721195614d7d8
Author: Peter Wu <peter@lekensteyn.nl>
Date:   Thu Jul 9 16:36:49 2015 +0200

    ssl-utils: fix failing decryption for some RSA keys

    Reported at
    https://ask.wireshark.org/questions/43788/struggling-to-decrypt-ssl

    "u" requirement is documented at
   
https://www.gnupg.org/documentation/manuals/gcrypt/RSA-key-parameters.html#RSA-key-parameters

    Add regression test (key is generated manually with p and q swapped and
    qInv recalculated).

    Change-Id: I5505ddcdb54bb47d7a58867b8c3e53fcc0f66dde
    Reviewed-on: https://code.wireshark.org/review/9573
    Tested-by: Peter Wu <peter@lekensteyn.nl>
    Reviewed-by: Peter Wu <peter@lekensteyn.nl>

commit 79be8312da5f572664e8a56d6e98d92dc34fdc95
Author: Peter Wu <peter@lekensteyn.nl>
Date:   Thu Jul 9 15:48:09 2015 +0200

    ssl-utils: remove unused, broken libgcrypt code

    Remove unused SSL_FAST code. That approach cannot work in modern
    libgcrypt anyway since the symbols were renamed and private to
    libgcrypt. The RSA decryption routine is not even a hot path, it is only
    called for decrypting the encrypted pre-master secret.

    While at it, expand the SSL_PRIVATE_KEY macro and remove its definition.

    Change-Id: Ied556d18501ea6cbac5fb27218364b3479ad62ce
    Reviewed-on: https://code.wireshark.org/review/9572
    Reviewed-by: Martin Kaiser <wireshark@kaiser.cx>
    Reviewed-by: Peter Wu <peter@lekensteyn.nl>

The only reason I can think of is a bug in the libgcrypt library that is in use
by the Ubuntu libgcrypt 1.5.3 package. I'll try to reproduce it on such a
machine.

You are receiving this mail because:
  • You are watching all bug changes.