加密扩展
在线手册:中文  英文

OpenSSL


加密扩展
在线手册:中文  英文

用户评论:

michelerosica at gmail dot com (2012-05-29 18:30:24)

<?php
/*-----------------------------------------------------------*
 * AES: openSSL (PHP) implementation                         *
 *-----------------------------------------------------------*/
 
 # init
 
$keySizeInBits 128;
 
$keySize = ($keySizeInBits 8);

 
# get method 
 
$method getMethod($keySize"ofb");

 
# get the cipher key
 
$salt openssl_random_pseudo_bytes(8);
 
$key pbkdf2("Secret Passphrase"$salt1000$keySize);

/*-----------------------------------------------------------*
 * ENCRYPT: AES 128 bit, OFB                                 *
 *-----------------------------------------------------------*/
 # get iv
 
$iv openssl_random_pseudo_bytes(16);
 
$iv64 base64_encode($iv);

 
# do encryption
 
$raw false// true returns raw bytes, false returns base64
 
$ciphertext openssl_encrypt("plaintext"$method$key$raw$iv);

/*-----------------------------------------------------------*
 * DECRYPT: AES 128 bit, OFB                                 *
 *-----------------------------------------------------------*/
 # get the IV
 
$iv base64_decode($iv64);

 
# do decryption
 
$plain openssl_decrypt($ciphertext$method$key$raw$iv);
?>

Anonymous (2009-10-07 17:28:26)

OpenSSL creates asynchronous key pairs, however I wanted to have the private key something that was human-memorizable. With the standard keys generated, this is not possible. How I achieved it was to use two types of encryption.
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.
Of course, this will only be as good as your human-memorizable key is and can potentially reduce the security of your script if you choose something simple or don't use salts.

bdh dot hall at gmail dot com (2009-05-29 15:18:09)

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 (2008-08-31 10:27:03)

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.

易百教程