OpenSSL

简介
安装／配置
预定义常量
密钥/证书参数
证书验证
OpenSSL 函数
- openssl_cipher_iv_length — 获取密码iv长度
- openssl_cms_decrypt — Decrypt a CMS message
- openssl_cms_encrypt — Encrypt a CMS message
- openssl_cms_read — Export the CMS file to an array of PEM certificates
- openssl_cms_sign — Sign a file
- openssl_cms_verify — Verify a CMS signature
- openssl_csr_export_to_file — 将CSR导出到文件
- openssl_csr_export — 将CSR作为字符串导出
- openssl_csr_get_public_key — 返回CSR的公钥
- openssl_csr_get_subject — 返回CSR的主题
- openssl_csr_new — 生成一个 CSR
- openssl_csr_sign — 用另一个证书签署 CSR (或者本身) 并且生成一个证书
- openssl_decrypt — 解密数据
- openssl_dh_compute_key — 计算远程DH密钥(公钥)和本地DH密钥的共享密钥
- openssl_digest — 计算摘要
- openssl_encrypt — 加密数据
- openssl_error_string — 返回 openSSL 错误消息
- openssl_free_key — 释放密钥资源
- openssl_get_cert_locations — 检索可用的证书位置
- openssl_get_cipher_methods — 获取可用的加密算法
- openssl_get_curve_names — 获得ECC的可用曲线名称列表
- openssl_get_md_methods — 获取可用的摘要算法
- openssl_get_privatekey — 别名 openssl_pkey_get_private
- openssl_get_publickey — 别名 openssl_pkey_get_public
- openssl_open — 打开密封的数据
- openssl_pbkdf2 — 生成一个 PKCS5 v2 PBKDF2 字符串
- openssl_pkcs12_export_to_file — 输出一个 PKCS#12 兼容的证书存储文件
- openssl_pkcs12_export — 将 PKCS#12 兼容证书存储文件导出到变量
- openssl_pkcs12_read — 将 PKCS#12 证书存储区解析到数组中
- openssl_pkcs7_decrypt — 解密一个 S/MIME 加密的消息
- openssl_pkcs7_encrypt — 加密一个 S/MIME 消息
- openssl_pkcs7_read — 将 PKCS7 文件导出为 PEM 格式证书的数组
- openssl_pkcs7_sign — 对一个 S/MIME 消息进行签名
- openssl_pkcs7_verify — 校验一个已签名的 S/MIME 消息的签名
- openssl_pkey_derive — Computes shared secret for public value of remote and local DH or ECDH key
- openssl_pkey_export_to_file — 将密钥导出到文件中
- openssl_pkey_export — 将一个密钥的可输出表示转换为字符串
- openssl_pkey_free — 释放一个私钥
- openssl_pkey_get_details — 返回包含密钥详情的数组
- openssl_pkey_get_private — 获取私钥
- openssl_pkey_get_public — 从证书中解析公钥，以供使用。
- openssl_pkey_new — 生成一个新的私钥
- openssl_private_decrypt — 使用私钥解密数据
- openssl_private_encrypt — 使用私钥加密数据
- openssl_public_decrypt — 使用公钥解密数据
- openssl_public_encrypt — 使用公钥加密数据
- openssl_random_pseudo_bytes — 生成一个伪随机字节串
- openssl_seal — 密封 (加密) 数据
- openssl_sign — Generate signature
- openssl_spki_export_challenge — 导出与签名公钥和挑战相关的挑战字符串
- openssl_spki_export — 通过签名公钥和挑战导出一个可用的PEM格式的公钥
- openssl_spki_new — 生成一个新的签名公钥和挑战
- openssl_spki_verify — 验证签名公钥和挑战。
- openssl_verify — 验证签名
- openssl_x509_check_private_key — 检查私钥是否对应于证书
- openssl_x509_checkpurpose — 验证是否可以为特定目的使用证书
- openssl_x509_export_to_file — 导出证书至文件
- openssl_x509_export — 以字符串格式导出证书
- openssl_x509_fingerprint — 计算一个给定的x.509证书的指纹或摘要
- openssl_x509_free — 释放证书资源
- openssl_x509_parse — 解析一个X509证书并作为一个数组返回信息
- openssl_x509_read — 解析一个x.509证书并返回一个资源标识符
- openssl_x509_verify — Verifies digital signature of x509 certificate against a public key
OpenSSLCertificate — OpenSSLCertificate 类
OpenSSLCertificateSigningRequest — OpenSSLCertificateSigningRequest 类
OpenSSLAsymmetricKey — OpenSSLAsymmetricKey 类

User Contributed Notes

james at NOSPAM dot gmail dot com 13-Jul-2016 10:01


In regards to the comment above:



"After generating a key pair with OpenSSL, the public key can be stored in plain text format. I then encrypted the private key itself using regular mcrypt with the human-memorizable key of my choice and converted it to ACSII using base64_encode. Then to get the private key back, I just decrypted it with mcrypt. This way I could store the encrypted private key on the server without worrying about having things stored unencrypted. "



To anyone reading this that might not be all that familiar with public key cryptography; I haven't the slightest idea what this person is talking about, but I can tell you its an absolutely horrible idea.  He might have ended up with something that "looked like a private key" insofar as it was a base64 encoded string, but he did not have a private key.  The parameters that make up a public/private key pair are EXTREMELY specific and in the case of RSA rely on very large co-primes plus an even larger moduli.  Its not just a base64 encoded string; and just for the record... base64 encoding is not encryption. 



One of two things happened; the more likely is the whatever program he needed the certificate for realized there was something wrong with the private key, and ignored it, reverting to either a default key, or null encryption or something.  The worse outcome would be if it interpreted whatever was there as legitimate; and encrypted data as if it were a a proper certificate; encrypting this way would likely provide close to zero security and I'm not even sure you could decrypt the data once encrypted.  Its not worth giving much thought.  



Just please; don't do this.



You can read about pki certificate structures and attribute frameworks by pasting "T-REC-X.509-201210-I" into your favorite interwebs search widget and following the result to the International Telecommunications Union webpage, or you can refer to the numerous RFCs; 6818, 5820 being good places to start. The Internet Engineering Task Force archives all RFCs, but there are other sources as well.  "IETF RFC" should be enough to get you there.



...sorry, the "spam buster" was giving me all kinds of issues.

bdh dot hall at gmail dot com 29-May-2009 03:18


I was having a heck of a time finding help on making asynchronous encryption/decryption using private key/public key systems working, and I had to have it for creating a credit card module that uses recurring billing.



You'd be a fool to use normal, 'synchronous' or two-way encryption for this, so the whole mcrypt library won't help.



But, it turns out OpenSSL is extremely easy to use...yet it is so sparsely documented that it seems it would be incredibly hard.



So I share my day of hacking with you - I hope you find it helpful!



<?php



if (isset($_SERVER['HTTPS']) )

{

    echo "SECURE: This page is being accessed through a secure connection.<br><br>";

}

else

{

    echo "UNSECURE: This page is being access through an unsecure connection.<br><br>";

}



// Create the keypair

$res=openssl_pkey_new();



// Get private key

openssl_pkey_export($res, $privatekey);



// Get public key

$publickey=openssl_pkey_get_details($res);

$publickey=$publickey["key"];



echo "Private Key:<BR>$privatekey<br><br>Public Key:<BR>$publickey<BR><BR>";



$cleartext = '1234 5678 9012 3456';



echo "Clear text:<br>$cleartext<BR><BR>";



openssl_public_encrypt($cleartext, $crypttext, $publickey);



echo "Crypt text:<br>$crypttext<BR><BR>";



openssl_private_decrypt($crypttext, $decrypted, $privatekey);



echo "Decrypted text:<BR>$decrypted<br><br>";

?>



Many thanks to other contributors in the docs for making this less painful.



Note that you will want to use these sorts of functions to generate a key ONCE - save your privatekey offline for decryption, and put your public key in your scripts/configuration file. If your data is compromised you don't care about the encrypted stuff or the public key, it's only the private key and cleartext that really matter.



Good luck!

koen dot thomeer at pubmed dot be 31-Aug-2008 10:27


For checking the status of a client certificate using OCSP, you can use this script:



<?php

// User variables:

$dir = '/path/to/temp/'; // Directory where apache has access to (chmod 777).

$RootCA = '/path/to/Root.cer'; // Points to the Root CA in PEM format.

$OCSPUrl = 'http://ocsp.url'; //Points to the OCSP URL

// Script:

$a = rand(1000,99999); // Needed if you expect more page clicks in one second!

file_put_contents($dir.$a.'cert_i.pem', $_SERVER['SSL_CLIENT_CERT_CHAIN_0']); // Issuer certificate.

file_put_contents($dir.$a.'cert_c.pem', $_SERVER['SSL_CLIENT_CERT']); // Client (authentication) certificate.

$output = shell_exec('openssl ocsp -CAfile '.$RootCA.' -issuer '.$dir.$a.'cert_i.pem -cert '.$dir.$a.'cert_c.pem -url '.$OCSPUrl);

$output2 = preg_split('/[\r\n]/', $output);

$output3 = preg_split('/: /', $output2[0]);

$ocsp = $output3[1];

echo "OCSP status: ".$ocsp; // will be "good", "revoked", or "unknown"

unlink($dir.$a.'cert_i.pem');

unlink($dir.$a.'cert_c.pem');

?>



It can be ameliorated, but it's just a beginning!



Normally, you can extract the ocsp url from the client certificate. Also, an OCSP request contains only the hash of the issuer name, the hash of the issuer's key, and the serial number of the client certificate. All three can be extracted directly from the client certificate.