SWABIZZ
In the Business of Superior WEB Accessed Solutions
SSL Secure Server
Strictly speaking, https is not a separate protocol,
but refers to the combination of a normal HTTP interaction over an
encrypted Secure Sockets Layer (SSL) or Transport Layer Security
(TLS) connection. This ensures reasonable protection from
eavesdroppers and man-in-the-middle attacks.
An https: URL may specify a TCP port; if it does not, the connection
uses port 443 (unsecured HTTP typically uses port 80).
To prepare a web-server for accepting https connections the
administrator must create a public key certificate for the
web-server. These certificates can be created for Unix based servers
with tool(s) such as OpenSSL's ssl-ca [1] or SuSE's gensslcert. This
certificate must be signed by a certificate authority of one form or
another, which certifies that the certificate holder is indeed the
entity it claims to be. Web browsers are generally distributed with
the signing certificates of major certificate authorities, so that
they can verify certificates signed by them.
The system can also be used for client authentication, in order to
restrict access to a Web server to only authorized users. For this,
typically the site administrator creates certificates for each user
which are loaded into their browser. These normally contain the name
and e-mail address of the authorized user, and are automatically
checked by the server on each reconnect to verify the user's
identity, potentially without ever entering a password.
Swabizz hosting supports SSL Secure Server
