This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 8 and 10 (spanning 2 versions)
Revision 8 as of 2007-11-02 18:15:13
Size: 2292
Editor: h113-n225
Comment:
Revision 10 as of 2008-02-22 19:28:45
Size: 2578
Editor: GuyHarris
Comment: Fix typo.
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
CMP is a protocol for managing Public Key Infrastrictures (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'' and ''Unicert'' 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.
Line 10: Line 10:
 * 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).
Line 29: Line 30:
You cannot directly filter CMP protocol while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one. You cannot directly filter CMP while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one.
Line 35: Line 36:
 * [http://www.ietf.org/rfc/rfc4210.txt RFC 4210] ''Internet X.509 Public Key Infrastructure Certificate Management Protocols''. This version obsolets [http://www.ietf.org/rfc/rfc2510.txt RFC 2510]. New RFC says that the CMP transport protocol issues are handled in a separate document CMPtrans ( [http://tools.ietf.org/html/draft-ietf-pkix-cmp-transport-protocols-05 Last IETF draft of CMPtrans] ).  * [http://www.ietf.org/rfc/rfc4210.txt RFC 4210] ''Internet X.509 Public Key Infrastructure Certificate Management Protocols''. This version obsoletes [http://www.ietf.org/rfc/rfc2510.txt RFC 2510]. According to the new RFC, the CMP transport protocol issues are handled in the separate CMPtrans document.
 *
[http://tools.ietf.org/html/draft-ietf-pkix-cmp-transport-protocols-05 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.
Line 37: Line 39:
== Discussion ==
I edited this page in part about RFC4210 and I'm not sure that CMPtrans last version is "Last IETF draft of CMPtrans" because i'm not in this theme deeply. Sorry, my english is bad.

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.

History

TODO:

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).

Wireshark

TODO:

Preference Settings

TODO:.

Example capture file

  • attachment:SampleCaptures/cmp-trace.pcap.gz CMP certificate requests
  • attachment:SampleCaptures/cmp-in-http-with-errors-in-cmp-protocol.pcap.gz CMP version 2 encapsulated in HTTP on port 4711. Full "Initialization Request" and rejected "Key Update Request". There are some errors in the CMP packages.

Display Filter

A complete list of CMP display filter fields can be found in the [http://www.wireshark.org/docs/dfref/c/cmp.html display filter reference]

  • Show only the CMP based traffic:
     cmp 

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 

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