SSL的認(rèn)證原理及使用openssl創(chuàng)建CA自認(rèn)證證書

如何制作自認(rèn)證證書

通用網(wǎng)絡(luò)間的安全傳輸離不開SSL，SSL代表著[公開密鑰加密（PKI）]技術(shù)的應(yīng)用

簡(jiǎn)單來講，使用公開密鑰加密，每單次傳輸過程需要兩個(gè)密鑰完成，即加密密鑰和解秘密鑰

數(shù)據(jù)的提供方，即數(shù)據(jù)傳輸?shù)某霭l(fā)點(diǎn)對(duì)數(shù)據(jù)進(jìn)行加密，之后傳輸，加密使用的密鑰是公開的，稱為公鑰(public key)

數(shù)據(jù)的接收方，對(duì)接收到的數(shù)據(jù)進(jìn)行解密處理，密鑰不公開，稱為私鑰(private key)

SSL中公鑰和私鑰配對(duì)使用，即1個(gè)公鑰對(duì)應(yīng)1個(gè)私鑰（其他模型/算法也可以實(shí)現(xiàn)1對(duì)多，多對(duì)多的密鑰匹配），由數(shù)據(jù)的接收方計(jì)算，并將公鑰通知對(duì)方

所以，實(shí)際應(yīng)用中，完成一次數(shù)據(jù)交互，單方向可讀可寫，則需要兩個(gè)密鑰對(duì)，傳輸方各持一個(gè)公鑰，一個(gè)私鑰

在開始傳輸之前，建立連接過程中，公鑰可以用明文傳輸(SSL的握手協(xié)議)

只要私鑰復(fù)雜到難以破解，傳輸?shù)募瓤梢员３职踩?，又可以保持隨意性，即無需事先交換，利用現(xiàn)有網(wǎng)絡(luò)，即使有監(jiān)聽，只要保證私鑰保密，就可以實(shí)現(xiàn)數(shù)據(jù)的安全傳輸

但是，問題在于，如果在惡意監(jiān)聽過程中，公鑰在傳輸給另一方時(shí)被替換，相當(dāng)于監(jiān)聽者與傳輸?shù)碾p方建立兩個(gè)假安全連接，獲取傳輸?shù)膬?nèi)容。

為解決這個(gè)問題，SSL的解決方案中使用了對(duì)數(shù)據(jù)提供方的認(rèn)證機(jī)制

數(shù)據(jù)的接收方預(yù)先保留一些認(rèn)證機(jī)構(gòu)(CA)的信息，數(shù)據(jù)服務(wù)方需要到認(rèn)證機(jī)構(gòu)對(duì)自己的公鑰作認(rèn)證處理，接收方使用CA的信息和數(shù)據(jù)服務(wù)方的認(rèn)證信息解析驗(yàn)證服務(wù)方公鑰的有效性

CA被視為整個(gè)流程中的源頭，CA可以是權(quán)威的認(rèn)證機(jī)構(gòu)，當(dāng)然也可以自行定制生成，目的僅是保證SSL機(jī)制的順利執(zhí)行

在整個(gè)機(jī)制中，數(shù)據(jù)接收方（客戶端）所需的信息

CA.crt

Server.crt

都可以由openssl命令執(zhí)行生成

openssl genrsa -des3 -out ca.key 1024

openssl req -new -key ca.key -out ca.csr

cp ca.key ca.key.org
openssl rsa -in ca.key.org -out ca.key

openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt

使用相同的方法生成server.key

用ca信息對(duì)其作認(rèn)證處理

openssl x509 -req -days 3650 -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt

附加計(jì)算工具參數(shù)

openssl dHParam -outform PEM -out dh2024.pem 1024

參考文章

http://www.akadia.com/services/ssh_test_certificate.html

Zurück     
How to create a self-signed SSL Certificate ...

...  which can be used for testing purposes or internal usage

Overview

    The following is an extremely simplified view of how SSL is implemented and what part the certificate plays in the entire process.

    Normal web traffic is sent unencrypted over the Internet. That is, anyone with access to the right tools can snoop all of that traffic. Obviously, this can lead to problems, especially where security and privacy is necessary, such as in credit card data and bank transactions. The Secure Socket Layer is used to encrypt the data stream between the web server and the web client (the browser).

    SSL makes use of what is known as asymmetric cryptography, commonly referred to as public key cryptography (PKI). With public key cryptography, two keys are created, one public, one private. Anything encrypted with either key can only be decrypted with its corresponding key. Thus if a message or data stream were encrypted with the server's private key, it can be decrypted only using its corresponding public key, ensuring that the data only could have come from the server.

    If SSL utilizes public key cryptography to encrypt the data stream traveling over the Internet, why is a certificate necessary? The technical answer to that question is that a certificate is not really necessary - the data is secure and cannot easily be decrypted by a third party. However, certificates do serve a crucial role in the communication process. The certificate, signed by a trusted Certificate Authority (CA), ensures that the certificate holder is really who he claims to be. Without a trusted signed certificate, your data may be encrypted, however, the party you are communicating with may not be whom you think. Without certificates, impersonation attacks would be much more common.


Step 1: Generate a Private Key

    The openssl toolkit is used to generate an RSA Private Key and CSR (Certificate Signing Request). It can also be used to generate self-signed certificates which can be used for testing purposes or internal usage.

    The first step is to create your RSA Private Key. This key is a 1024 bit RSA key which is encrypted using Triple-DES and stored in a PEM format so that it is readable as ASCII text.

    openssl genrsa -des3 -out server.key 1024  
Generating RSA private key, 1024 bit long modulus  
.........................................................++++++  
........++++++  
    e is 65537 (0x10001)  
Enter PEM pass phrase:  
Verifying password - Enter PEM pass phrase:  


Step 2: Generate a CSR (Certificate Signing Request)

    Once the private key is generated a Certificate Signing Request can be generated. The CSR is then used in one of two ways. Ideally, the CSR will be sent to a Certificate Authority, such as Thawte or Verisign who will verify the identity of the requestor and issue a signed certificate. The second option is to self-sign the CSR, which will be demonstrated in the next section.

    During the generation of the CSR, you will be prompted for several pieces of information. These are the X.509 attributes of the certificate. One of the prompts will be for "Common Name (e.g., YOUR name)". It is important that this field be filled in with the fully qualified domain name of the server to be protected by SSL. If the website to be protected will be https://public.akadia.com, then enter public.akadia.com at this prompt. The command to generate the CSR is as follows:

    openssl req -new -key server.key -out server.csr

    Country Name (2 letter code) [GB]:CH
    State or Province Name (full name) [Berkshire]:Bern
    Locality Name (eg, city) [Newbury]:Oberdiessbach
    Organization Name (eg, company) [My Company Ltd]:Akadia AG
    Organizational Unit Name (eg, section) []:Information Technology
    Common Name (eg, your name or your server's hostname) []:public.akadia.com
    Email Address []:martin dot zahn at akadia dot ch
    Please enter the following 'extra' attributes
    to be sent with your certificate request
    A challenge password []:
    An optional company name []:


Step 3: Remove Passphrase from Key

    One unfortunate side-effect of the pass-phrased private key is that Apache will ask for the pass-phrase each time the web server is started. Obviously this is not necessarily convenient as someone will not always be around to type in the pass-phrase, such as after a reboot or crash. mod_ssl includes the ability to use an external program in place of the built-in pass-phrase dialog, however, this is not necessarily the most secure option either. It is possible to remove the Triple-DES encryption from the key, thereby no longer needing to type in a pass-phrase. If the private key is no longer encrypted, it is critical that this file only be readable by the root user! If your system is ever compromised and a third party obtains your unencrypted private key, the corresponding certificate will need to be revoked. With that being said, use the following command to remove the pass-phrase from the key:

    cp server.key server.key.org
    openssl rsa -in server.key.org -out server.key

The newly created server.key file has no more passphrase in it.

    -rw-r--r-- 1 root root 745 Jun 29 12:19 server.csr
    -rw-r--r-- 1 root root 891 Jun 29 13:22 server.key
    -rw-r--r-- 1 root root 963 Jun 29 13:22 server.key.org


Step 4: Generating a Self-Signed Certificate

    At this point you will need to generate a self-signed certificate because you either don't plan on having your certificate signed by a CA, or you wish to test your new SSL implementation while the CA is signing your certificate. This temporary certificate will generate an error in the client browser to the effect that the signing certificate authority is unknown and not trusted.

    To generate a temporary certificate which is good for 365 days, issue the following command:

    openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
    Signature ok
    subject=/C=CH/ST=Bern/L=Oberdiessbach/O=Akadia AG/OU=Information
    Technology/CN=public.akadia.com/Email=martin dot zahn at akadia dot ch
    Getting Private key
    

    通過CA文件認(rèn)證服務(wù)器文件

    openssl x509 -req -days 3650 -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt


    dh文件生成
    openssl dHParam -outform PEM -out dh2024.pem 1024