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: > >> Correct, >> There are a plethora of sites that explain this: >> >> 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 s 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. > > 2. CERTIFICATES > A Certificate is a document that your website shows a browser to proclaim its identity. It “certifies” that the website is who it says it is. You said "IOW, the identify of the site can be trusted." I say, the trust is misplaced. > > Where did I say something different? > > Cheers, > > tedd > > _______________ > tedd sperling > tedd@xxxxxxxxxxxx No, you are not difficult, but please read your own statements. Both your statements are the direct opposite of mine.
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
