Wireshark-commits: [Wireshark-commits] rev 52320: /trunk/epan/dissectors/ /trunk/epan/dissectors/:
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: alagoutte@xxxxxxxxxxxxx
Date: Tue, 01 Oct 2013 19:35:34 GMT
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=52320

User: alagoutte
Date: 2013/10/01 07:35 PM

Log:
 Enable RC2 support with libgcrypt
 
 The name "RC2" is not used by libgcrypt, instead it uses
 "RFC2268_<keysize>". RFC2268_40 and RFC2268_128 are both documented,
 though only RFC2268_40 is implemented right now.
 
 As documented in RFC2246 (TLS 1.0), section 6.3.1 Export key generation
 example, exportable ciphers (in this case, the
 TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 cipher) only use 40 bits of the
 key_block, but the real key (final_{client,server}_write_key) used for
 the actual algorithm (RC2) is still 16 bytes (128 bits). Therefore
 RFC2268_128 is the correct name to use.
 
 As libgcrypt 1.5.3 does not support the 128-bit keys, I have submitted a
 patch for libgcrypt to support the larger 128-bit rc2 keys has been
 submitted to gcrypt-devel@xxxxxxxxx (it sits in their mail queue as I am
 not subscribed).

Directory: /trunk/epan/dissectors/
  Changes    Path                  Action
  +2 -2      packet-ssl-utils.c    Modified