Javascript is the language supported within browsers. It is handy for providing instant responsiveness on a web page without involving the web server. There are all too many web pages implemented with Javascript that simply do not function when Javascript is disabled.
http://eloquentjavascript.net/ provides a very nice guide to the language. Javascript is quite different from Java in its underlying philosophy and approach. Much of the information about Javascript is fairly low quality because the author failed to understand the language behind the syntax.
Eloquent Javascript understands the functional roots in the language. It is also nicely written. This is by far the best Javascript guide that I have seen.
Thursday, September 26, 2013
Thursday, September 12, 2013
Certificate Processing
xca is a GUI program that helps with managing certificates and keys. It does a nice job of managing keys and certificates. Whether you are operating your own little certifying authority or obtaining certificates from recognized public authorities, it's helpful to keep copies in the xca database.
Linux server programs specify certificates in their configuration files using pathnames to the actual files. Once you figure out your naming conventions, it is quite easy to export files from xca and copy them to the proper file system locations, replacing expiring certificates with replacements. Restart the service and the new certificate is in operation.
I find dealing with a Microsoft Windows server quite confusing. The menu choices never seem to match what I am doing. One key point: the server wants the key and the certificate to be bundled into one file. This is a PKCS #12 format. .p12 is commonly used for the file extension, but Microsoft prefers .pfx. Once you manage to navigate the menus to where the server wants your .pfx file, you'll be able to install the certificate.
A fine source for certificates is
https://www.startssl.com/
When you setup your account, they will install a certificate in your browser. There is no password to remember and logging in to the site is painless. If you need more than one identity, make sure your browser is configured to let you choose which certificate to present. My main gripe with the site is that the work flows all use a "wizard" approach, but with no capability to backtrack. This avoids complex forms, but can be quite frustrating when you're following the wrong flow and need to abandon your inputs and start over.
Linux server programs specify certificates in their configuration files using pathnames to the actual files. Once you figure out your naming conventions, it is quite easy to export files from xca and copy them to the proper file system locations, replacing expiring certificates with replacements. Restart the service and the new certificate is in operation.
I find dealing with a Microsoft Windows server quite confusing. The menu choices never seem to match what I am doing. One key point: the server wants the key and the certificate to be bundled into one file. This is a PKCS #12 format. .p12 is commonly used for the file extension, but Microsoft prefers .pfx. Once you manage to navigate the menus to where the server wants your .pfx file, you'll be able to install the certificate.
A fine source for certificates is
https://www.startssl.com/
When you setup your account, they will install a certificate in your browser. There is no password to remember and logging in to the site is painless. If you need more than one identity, make sure your browser is configured to let you choose which certificate to present. My main gripe with the site is that the work flows all use a "wizard" approach, but with no capability to backtrack. This avoids complex forms, but can be quite frustrating when you're following the wrong flow and need to abandon your inputs and start over.
Subscribe to:
Comments (Atom)