Tedd Sperling wrote: > On Feb 16, 2014, at 1:28 PM, Jasper Kips <jasper@xxxxxxxxxxxxx> wrote: > >> Op 16 feb. 2014, om 18:07 heeft Tedd Sperling <tedd@xxxxxxxxxxxx> het >> volgende geschreven: >> >>> On Feb 16, 2014, at 11:25 AM, Jasper Kips <jasper@xxxxxxxxxxxxx> >>> wrote: >>> >>>> http://wpengine.com/support/how-does-all-this-work-https-ssl-certificates-ca-public-and-private-keys-csrs/ >>> >>> I am not trying to be difficult, but the link you provided supports >>> everything I said -- namely: >>> >>> 1. HTTPS just means “HTTP with SSL.” Just as “http://”; means “this >>> is a website,” seeing “https://”; means “this is a website, and it’s >>> using SSL to encrypt data and authenticate the website. >> Yes and it NEEDS the certificate, which you kind of deny >> You: "I also claim that a SSL Certificate has absolutely nothing to >> do with actual HTTPS communication between the Browser and the >> Server. For example, I can use HTTPS communication by simply placing >> a script in a HTTPS directory or using a .htaccess directing such -- >> all without a SSL Certificate." >> >> And the certificate is needed, to establish the SSL, and hence then >> encrypted, connection. > > I am only questioning one doesn't need a SSL Certificate from a third > party to use HTTPS communication -- is that wrong? No, that is correct. You do need the certificate, but you may issue one yourself. > What is being implied by you is that a SSL Certificate exist > regardless if one purchases one from a third party or not -- is that > true? Yes. -- Per Jessen, Zürich (5.8°C) http://www.dns24.ch/ - your free DNS server, made in Switzerland. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
