Just a few corrections to some recent mails regarding SSL:


Q: Where does SSL belong, in the browser or the stack ?

A: It belongs in the stack. SSL is an acronym for "Secure Socket
Layer", i.e. it is an extension to the existing socket API
(usually bsdsocket.library on the Amiga) to support data
encryption and authentication. In the OSI reference model
it fits partially into the "transport" and "session" layers,
below the application layer, i.e. outside of application code.
The SSL protocol is in no way specific to web browsing. It has
nothing to do with HTTP or any other web browser functions.
SSL can be used for telnet, ftp, email etc. in the same way as
for web browsing, and standards exist for all that, so it makes
sense to share the code in a common place. The only reason why
some PC browsers traditionally included SSL in the browser is
because Windows and its built-in stack did not support it
already when the browsers were released.


Q: Does having SSL externally from the web browser cause any
difficulties in the browser or limit the browser in any way,
e.g. regarding certificate management ?

A: No. Specifically regarding MiamiSSL: it supports certificate
verification and management in the same way as other SSL
implementations. (That's only logical, considering that it uses
the same code.) Voyager just does not support the certificate
hooks of MiamiSSL in its current version. Certificate
verifications and updates would be easy to implement though,
and the example source code for MiamiSSL demonstrates how to
do that.


Q: Is IBrowseSSL/VoyagerSSL in any way "better" or more
advanced than MiamiSSL ?

A: No, Chris, it is not. Please stop spreading nonsense.
ALL Amiga SSL implementations are currently based on
SSLeay 0.6.x (SSL v2), i.e. they use identical code and a
full set of protocols, as many as are permissible by law.
For both MiamiSSL and VoyagerSSL new versions are planned
for the near future, based on more recent versions of
OpenSSL, with support for SSL v3 and TLS. Besides, users
within the US or Canada *have* to use MiamiSSL or
IBrowseSSL. The use of VoyagerSSL is illegal there.

-- 
Holger Kruse   [EMAIL PROTECTED]
               http://www.nordicglobal.com
               NO COMMERCIAL SOLICITATION !


____________________________________________________________
Genesis Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"

Reply via email to