I'm trying to get OpenSSL working on a Mac (yeah, yeah-- I know), but
have run into some problems, and I'm hoping for some advice. And yes,
I've searched the mailing list archives before posting this. :-)
Anyway, the big problem is that the Mac doesn't support sockets. There
is a nice socket emulation/implementation called GUSI which worked with
SSLeay, but it doesn't seem to work with OpenSSL. I'm still poking
around with that, since that would require the least amount of effort to
make this all go.
The next step will be to get away from GUSI, and instead implement
support via the Mac's "native" networking API, OpenTransport
(STREAMS-based). This is where my question(s) come in:
In terms of porting to a system that doesn't support unix-style sockets,
I *think* I really just need to hack on the bss_sock.c, bss_conn.c, and
b_sock.c (and bss_acpt.c if I'm doing server stuff). Oh-- and it looked
like there was some stuff in eos.h that might need tweaking.
Does that seem right to all of you? I took a quick look at the Winsock
port details, and that seems to be where the big differences lie. Yes?
No?
Also, are there endian issues I'll need to worry about? For instance,
this bit from BIO_get_host_ip() in b_sock.c is scarey:
for (i=0; i<4; i++)
ip[i]=he->h_addr_list[0][i];
I figured that endian problems would have been worked out before this,
but maybe not.
Thanks for listening....
-Roy
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
