PHP Serial Extension is a Development software developed by Cosmin Buhu. After our trial and test, the software is proved to be official, secure and free. Here is the official description for PHP Serial Extension: BS Editor: This is a loadable extension for running on Windows implementing serial port handling and communications. Once installed in PHP environment you can programm PHP applications to control serial device hosted on server from remote location; these devices can be anything from video, cameras pan/tilt, ham radios, media players, home automation boxes, GSM modems/ (send/receive SMS), only your and needs are the limits.

For checking the status of a client certificate using OCSP, you can use this script: 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. 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.

Optional: If you have Arduino-uno and an IR receiver: - See the dir Arduino. Optional: Serial communications php-Arduino in windows: - Download and install 'PHP Serial extension' free from (with some limits). Note: If you have some different IR HW, modify irp_rxtxArduino.php to. 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.

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. John Deere 6x4 Gator Technical Manual. 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. 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.