Explore >> Select a destination
|
You are here 
|
agiletribe.wordpress.com | ||
| | | | |
swiftrocks.com
|
|
| | | | | You do not need to understand the theory of certificates and profiles in order to create a fully working iOS app, but you might be interested in knowing how this process works to make future debugging sessions easier. | |
| | | | |
eamonnsullivan.co.uk
|
|
| | | | | One huge and welcome change in the last decade or so for Web development is that secure connections are ubiquitous. Free certificates are available and most hosting providers make it very easy to obtain, use and renew the certificates automatically. This site, for example, runs on Amazon Web Services and enabling https took not much more effort than ticking a few checkboxes.Browsers, like Chrome, Firefox and Safari, have also played their part, by gently steering users toward secure connections, warning about sending sensitive information over plain text and switching to https automatically, when available. | |
| | | | |
dadrian.io
|
|
| | | | | This post is about HTTPS (X.509) certificates used on the web1. It has two parts: Certificates explained without cryptography Certificates explained with cryptography The explanation with cryptography depends on the explanation without cryptography, so you'll want to either read both, or only read Part 1. Certificates and certification authorities, explained without cryptography Websites use certificates to prove that they're the "real" website2, and not an imposter. The certificate is used to bootstrap ... | |
| | | | |
zaries.wordpress.com
|
|
| | | There are thousands of articles and entries in stackexchange but none of them worked for me out of the box. So after hours of battling with this issue here is my short recipe. Create the Root Key: openssl genrsa -out rootCA.key 2048 Self-sign this root certificate: openssl req -x509 -new -nodes -key rootCA.key -sha256 -days... | ||
