Skip to main content

SCEP certificate enrollment - packet analysis


1. CA cert request:

 Enrolling device requests and installs CA cert.

 SCEP Opertion: GetCACert

 HTTP Header:

 GET /CertSrv/mscep/mscep.dll/pkiclient.exe?operation=GetCACert&message=SCEPLab HTTP/1.0
Host: 10.0.0.6



2. SCEP server returns the CA cert:

 In the case of GET operation with a type of GetCACert, the MIME content type returned will 
depend on whether or not an RA is in use. If there is no RA, only the CA certificate is sent back in the response, and the response has the content type tagged as application/x-x509-ca-cert.
If there is an RA, as it is the case in this lab, the RA certificates are sent back together with the CA certificates. The content type is application/x-x509-ca-ra-cert.
HTTP Header:

HTTP/1.1 200 OK
Content-Length: 4170
Content-Type: application/x-x509-ca-ra-cert
Server: Microsoft-IIS/8.0
Date: Mon, 29 Apr 2013 09:15:51 GMT
Connection: close


3. Device requests an identity certificate:

 SCEP Operation: PKIOperation

 HTTP Header (message string has been truncated):

 GET /CertSrv/mscep/mscep.dll/pkiclient.exe?operation=PKIOperation&message=MIITnyeD%0%3D%3D%0A HTTP/1.0
Host: 10.0.0.6


4. SCEP server returns identity cert:

 For each GET operation, the CA/RA server will return a MIME object via HTTP. For a GET operation with PKIOperation as its type, the response is tagged as having a Content Type of application/x-pki-message. The body of this message is a BER encoded binary PKI message.

 HTTP Header:

 HTTP/1.1 200 OK
Content-Length: 2067
Content-Type: application/x-pki-message
Server: Microsoft-IIS/8.0
Date: Mon, 29 Apr 2013 10:46:51 GMT
Connection: close


SCEP Reference: http://www.cisco.com/warp/public/cc/pd/sqsw/tech/scep_wp.htm
Labels:

Comments

Post a Comment

Popular posts from this blog

x.509 Certificates - Critical vs non-critical extensions

Extensions are used to associate additional information with the user or the key.  Each certificate extension has three attributes - extnID, critical, extnValue extnID - Extension ID - an OID that specifies the format and definitions of the extension critical - Critical flag - Boolean value extnValue - Extension value  Criticality flag specifies whether the information in an extension is important. If an application doesn't recognize the extension marked as critical, the certificate cannot be accepted. If an extension is not marked as critical (critical value False) it can be ignored by an application. In Windows, critical extensions are marked with a yellow exclamation mark,  View certificate extensions using OpenSSL: # openssl x509 -inform pem -in cert.pem -text -noout (output abbreviated)         X509v3 extensions:             X509v3 Key Usage: critical                 Digital Signature, Key Encipherment             X509v3 Subject Key Identifier
Post a Comment
Read more

Count number of lines - 'findstr'

How do I count number of lines in a command output? findstr /r/n "^" | find /c ":" Above commands will display number of lines output by whatever command (well, nearly whatever) you specify in the front.  For example:  C:\>ping localhost | findstr /r/n "^" | find /c ":" FINDSTR: // ignored 12 This comes handy if you want to find out how many OUs you have in Active Directory: dsquery ou  -limit 0 | findstr /r/n "^" | find /c ":" How many user accounts there are: dsquery user -limit 0 | findstr /r/n "^" | find /c ":" Computers: dsquery computer -limit | findstr /r/n "^" | find /c ":"
Post a Comment
Read more

Cisco ASA Certificate Revocation Checking

ASA supports status verification using CRLs and OCSP. CRL can be retrieved using HTTP, LDAP or SCEP. Revocation checking using CRL: Over HTTP: ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-crl)# protocol http By default ASA will use address listed in CDP extension of the certificate that is being validated.  To override default behaviour we need to add the following in the CRL configuration context. ciscoasa(config-ca-crl)# policy static ciscoasa(config-ca-crl)# url 1 http://cdpurl.kp.local/crl.crl Over LDAP: Certificate I'm using for this lab, doesn't have LDAP address in its CDP extension. Therefore I'm using "policy static"  to specify LDAP URL where CRL can be retrieved.  ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-trustpoint)# crl configure ciscoasa
Post a Comment
Read more