Re: Securing socket programming
Re: Securing socket programming
- Subject: Re: Securing socket programming
- From: Becky Willrich <email@hidden>
- Date: Mon, 8 Aug 2005 13:21:43 -0700
Certainly if you need portability to another platform, OpenSSL is the
way to go, but if you're content with Mac-only code, you should look
at CFNetwork. CFNetwork provides a top-level API which spares you
from much of the details of setting up and using SSL; you specify the
host and port you wish to connect to, and the SSL protocol you wish
to use, and then just read from the resulting stream. And if your
interest is to perform HTTPS requests, you should look at
CFHTTPStream, which will handle HTTPS URLs just fine.
Hope that helps,
REW
On Aug 8, 2005, at 8:01 AM, Mark Thomas wrote:
Hi,
I'm needing to move some code over to SSL, and I can see there is
either
SecureTransport or OpenSSL which I can use.
So far I think the OpenSSL might give me a better choice because of
1) More portable to move code to other platforms ?
2) Sample code so far seems little less complicated, but that might be
because I still don't really understand this so far, and the
SecureTransport
sample isn't very straight forward as has heaps of options in it.
Does anybody have an recommendations or pitfalls which I might come
across, as I need this code to work from 10.2.0 onwards.
My present understand on this SSL mechanism is that you open a basic
socket on the secure serve socket e.g. 443 for http, and then you
have to
kick off the SSL api's ?
Thanks in advance
Mark.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden