The OpenSSL API
- From: Harold Weissman <HaroldW22@xxxxxxxxxxx>
- Date: Thu, 16 Aug 2007 10:27:55 -0000
Can anybody in this forum explain why the API exposed by OpenSSL
is so complicated? I am thinking from the point of view of an application
A that wishes to exchange data securely with some remote application B
using SSL. I would naively thought that an API with four calls would be
enough: One for establishing the secure channel, another for sending
data, another for receiving data, and one for terminating the secure
channel.
In my view, the application developer only wants to use security
afforded by the protocol, without having to know anything much (or at
all) about the protocol itself - after all, when doing sockets
programming, one does not have know much about TCP/IP, right? However,
the OpenSSL API forces application developers to do many of the protocol
chores by hand, so to speak.
Since the designers of the OpenSSL are clearly not stupid, I must
be missing something important here. What is it?
.
- Follow-Ups:
- Re: The OpenSSL API
- From: phil-news-nospam
- Re: The OpenSSL API
- From: slebetman@xxxxxxxxx
- Re: The OpenSSL API
- From: David Schwartz
- Re: The OpenSSL API
- Prev by Date: Re: Wireless config
- Next by Date: Considering a Transition from Windows to Linux
- Previous by thread: how do i stop LCP errors with my modem-router?
- Next by thread: Re: The OpenSSL API
- Index(es):
Relevant Pages
|