Skip to main content

Digital Certificate Encoding types

Privacy Enhanced Mail (PEM) format

.cer / .pem     

- Base-64 encoded ASCII files 
- can be open  in a text editor
- Can contain certificates and private keys

Distinguished Encoding Rules (DER) format

.cer  / .crt / .der

- Binary encoded 
- Hash of the file matches certificate's thumbprint
- Susceptible to corruption due to binary format 
            (single bit change will invalidate cert as the hash won't match)


Public Key Cryptography Standards (PKCS)

Cryptographic Message Syntax Standard   - PKCS#7

.p7b / .p7c 

- Binary encoded format
- Can include whole certification path
- Cannot contain private keys


Personal Information Exchange - PKCS#12

.pfx / .p12
- Passphrase protected
- Can contain private keys
- Can include whole certification path



References:

https://www.sslshopper.com/ssl-converter.html

http://technet.microsoft.com/en-us/library/cc738545(v=ws.10).aspx

This is very low level Windows API stuff:




Comments

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

DNS response and error types

In this post we explore common DNS response codes. We will cover the following responses: NOERROR SERVFAIL NXDOMAIN NODATA REFUSED Throughout article we’ll refer to the following RFCs: RFC 1034 - DOMAIN NAMES - CONCEPTS AND FACILITIES RFC 2308 - Negative Caching of DNS Queries (DNS NCACHE) RFC 2136 - Dynamic Updates in the Domain Name System (DNS UPDATE) RFC 8914 - Extended DNS Errors Response Codes - RCODEs The DNS RCODES are best defined in RFC2316 .  They signify what type of response was sent by the server. “RCODE   Response code - this four bit field is undefined in requests and set in responses.”   The table below shows the summary of the currently defined RCODEs. Mnemonic Val Description NOERROR 0 No error condition.

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 ":"