This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 11 and 12
Revision 11 as of 2008-04-12 17:50:13
Size: 2598
Editor: localhost
Comment: converted to 1.6 markup
Revision 12 as of 2008-04-14 12:02:50
Size: 2961
Editor: proxy2-nsn
Comment: Added link to CMP trace file with content-type "pkixcmp-poll"
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
Line 23: Line 24:
 * [[attachment:SampleCaptures/cmp_in_http_with_pkixcmp-poll_content_type.pcap.gz]] CMP version 2 encapsulated in HTTP. The CMP messages are of the deprecated but used content-type "pkixcmp-poll", so they are using the TCP transport style. In two of the four CMP messages, the content type is not explicitly set, thus they cannot be dissected correctly.
Line 29: Line 32:
Line 35: Line 39:

Certificate Management Protocol (CMP)

CMP is a protocol for managing Public Key Infrastructures (PKI) based on X.509v3 certificates. Protocol messages are defined for certificate creation and management. It is used by commercial PKI products as Entrust Security Manager, Unicert, Insta Certifier and Cryptlib. An OpenSSL client side implementation is work in progess.



Protocol dependencies

  • TCP: CMP can use TCP or HTTP as its transport protocol. The well known TCP port for CMP traffic is 829.

  • While there is no implementation known supporting it, transporting CMP over email (SMTP, POP etc.) or file transfer (["FTP") is also mentioned in CMPtrans (see below).

Example traffic

TODO: Add example traffic here (as plain text or Wireshark screenshot).



Preference Settings


Example capture file

Display Filter

A complete list of CMP display filter fields can be found in the display filter reference

  • Show only the CMP based traffic:

Capture Filter

You cannot directly filter CMP while capturing. However, if you know the TCP port used (see above), you can filter on that one.

  • Capture only the CMP traffic over the default port (829):
     tcp port 829 

  • RFC 4210 Internet X.509 Public Key Infrastructure Certificate Management Protocols. This version obsoletes RFC 2510. According to the new RFC, the CMP transport protocol issues are handled in the separate CMPtrans document.

  • Last IETF CMPtrans draft This draft for CMPtrans is expired, hence there is no obligatory transport protocols spec available. There are obvious mistakes in it which may cause confusion. Implementations more or less adhere to it.

  • RFC 4211 Certificate Request Message Format is more or less bound to CMP. This Version obsoletes RFC 2511 and is used by RFC 4210

CMP (last edited 2013-02-16 10:47:51 by LTejas)