- To generate a private key: openssl genrsa -out ca.key 2048
- To create a self-signed certificate: openssl req -new -key ca.key -x509 -days 365 -out ca.crt
- To create a certificate signing request: openssl req -new -key temp.key -out temp.csr
- To create a certificate from a certificate signing request: openssl x509 -req -in temp.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out temp.crt
- To display a certificate: openssl x509 -text -in temp.crt
- To display the content of a pkcs12 formatted certificate (the displayed private key and certificate are in PEM format, which can be used in the above commands): openssl pkcs12 -in old_uk_escience.p12 -out old.txt
- To convert from pkcs12 format to PEM format: openssl pkcs12 -in cred.p12 -out cert.pem -nodes -clcerts -nokeys, openssl pkcs12 -in cred.p12 -out key.pem -nodes -nocerts
- To create pkcs12 format certificate using PEM format private key and certificate: openssl pkcs12 -in temp.crt -inkey temp.key -out temp.p12 -export
Showing posts with label Cryptography. Show all posts
Showing posts with label Cryptography. Show all posts
Thursday, November 06, 2008
OpenSSL
Recently I used the openssl utility to generate key pairs and certificates. For example,
Self-Decrypting HTML Page
This is something worthy doing. Let's call it self-decrypting HTML page.
It is a publicly accessible, encrypted HTML page, that can be hosted in any website, but can only be decrypted by authorized persons who know the key. JavaScript can be used to perform encryption and decryption locally at the browser. Thus what is transmitted on the net and stays at the public website is the encrypted information, which guarantees the confidentiality of the information. Some symmetric key algorithm is preferred.
A self-decrypting HTML page generator is needed to convert the to-be-protected information to a self-decrypting HTML page.
It is noted that a United States Patent 7003800 has been filed on "Self-decrypting web site pages". It seems it talks about a method pertinent to a web site.
A self-decrypting email utility performs the similar task, which uses RC4 as the cipher. Here is the JavaScript code for RC4.
Compared with another web-based confidential information system, i.e., some information is hosted on a HTTPS server and is protected by some authentication method, self-decrypting HTML page does not require an authentication method, thus no need for user management. All needed to access the confidential information is the URL of the self-decrypting HTML page and the key.
Will Google App Engine be a good platform for this? Will it be possible to use Google AdSense to generate revenue from this application?
It is a publicly accessible, encrypted HTML page, that can be hosted in any website, but can only be decrypted by authorized persons who know the key. JavaScript can be used to perform encryption and decryption locally at the browser. Thus what is transmitted on the net and stays at the public website is the encrypted information, which guarantees the confidentiality of the information. Some symmetric key algorithm is preferred.
A self-decrypting HTML page generator is needed to convert the to-be-protected information to a self-decrypting HTML page.
It is noted that a United States Patent 7003800 has been filed on "Self-decrypting web site pages". It seems it talks about a method pertinent to a web site.
A self-decrypting email utility performs the similar task, which uses RC4 as the cipher. Here is the JavaScript code for RC4.
Compared with another web-based confidential information system, i.e., some information is hosted on a HTTPS server and is protected by some authentication method, self-decrypting HTML page does not require an authentication method, thus no need for user management. All needed to access the confidential information is the URL of the self-decrypting HTML page and the key.
Will Google App Engine be a good platform for this? Will it be possible to use Google AdSense to generate revenue from this application?
Subscribe to:
Posts (Atom)