Wireshark-bugs: [Wireshark-bugs] [Bug 11422] New: Some SHA2 Algorithm Ids not showing in certifi
Date: Wed, 05 Aug 2015 18:57:48 +0000
Bug ID 11422
Summary Some SHA2 Algorithm Ids not showing in certificates
Product Wireshark
Version Git
Hardware All
OS All
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter slimshady007@inbox.lv

Created attachment 13778 [details]
Patch diff

Build Information:
Version 1.99.9 (v1.99.9rc0-77-g2221153 from master)

Compiled (64-bit) with GTK+ 3.14.13, with Cairo 1.14.2, with Pango 1.36.8, with
libpcap, with POSIX capabilities (Linux), without libnl, with libz 1.2.8, with
GLib 2.44.1, without SMI, with c-ares 1.10.0, with Lua 5.2, with GnuTLS 3.3.8,
with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with PortAudio <= V18,
without
AirPcap.

Running on Linux 3.19.0-25-generic, with locale en_US.UTF-8, with libpcap
version 1.6.2, with libz 1.2.8, with GnuTLS 3.3.8, with Gcrypt 1.6.2.
        Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz

Built using gcc 4.9.2.
--
Algorithm Ids for sha384- sha512- and sha224WithRSAEncryption do not show as
such (e.g. just iso.2.840.113549.1.1.13 for sha512) in certificate dissection
with SSL. Please see attachments '-before' for existing behavior, '-after' for
fixed behavior provided by patch, and the relevant patch.

Explanation of changes reflected in patch
1) Moved 'sha256WithRSAEncryption' out of asn1/cmp/packet-cmp-template.c as
Certificate Management Protocol probably isn't the place for PCKS1 OIDs.
2) Added sha384, sha512, and sha224  OIDs to asn1/pkcs1/packet-pkcs1-template.c
alongside sha/sha1 (see also next change, '3') (also, this is the destination
for the sha256 move from '1').
3) Changed 'shaWithRSAEncryption' to 'sha1WithRSAEncryption' as it's both more
descriptive and the correct term from various RFCs (3279, 5480, & 5912).
4) Ran 'make' in asn1/cmp and asn1/pkcs1 to generate for /epan/dissectors

If pkcs1 really isn't the place for these OIDs then put them where they do.

Thanks,
Tim


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