>ulf> Is it really necessary to have 320k + 50k files in a printable
>ulf> encoding in the Mac directory??
>
>Macintosh files that are not purely text files may be formated in such
>a way that doesn't translate easily to and especially from a stream.
>At the same time, you probably want to avoid t
>Roy! I've
>changed your MacSockets a little bit so that synopsis resembles more
>Unix.
Okay! I'll take a look and try to stay in-synch.
-Roy
__
OpenSSL Project http://www.openssl.org
Developmen
>I have seen that some of the files include macsocket.h. Where can I get
>the version that the author intended?
I'm the author, and I can send you them if you wish. I take it they're
not in the current snapshot tree?
-Roy
__
Another quick question--
I'm coding a simple example for my Mac port of OpenSSL. The sample
fetches an URL from an "https" server (exciting and original, no?).
Anyway, what is a reasonable URL to have the demo code pointed at?
-Roy
Okay, as a first step toward getting my Mac changes into OpenSSL, here
are the diffs I've made wrt to clean 0.9.4 install.
Next, I'm packaging up some notes and code for Mac people who are
interested in using OpenSSL. Is there an FTP drop box I can place these?
It'll be a little large for em
A while ago I asked a question about contributing back some changes to
OpenSSL for porting it to the Macintosh.
I'm ready to do that now, but I'm not sure what format is preferred. I
think it's probably a diff dump, but I'm not sure what options to include
when I generate the diff dump (I'll
Okay, the background is that I've ported OpenSSL to the Macintosh (yeah,
yeah-- I know). Even stranger yet, I'm using it as a library for a code
resource which is loaded by another application to do an 'https' query of
a server (if it means anything to anyone reading this, I'm working on an
X
>> >> I suppose I ought to start thinking about submitting diffs back to the
>> >> project, huh?
>> >
>> >Yes, please do so via openssl-dev list. But please
>> >consider the following: (a) code needs to be somehow
>> >stable since probably no other developer has a Mac
>
>I do:-) But my CodeWarrior
>> I suppose I ought to start thinking about submitting diffs back to the
>> project, huh?
>
>Yes, please do so via openssl-dev list. But please
>consider the following: (a) code needs to be somehow
>stable since probably no other developer has a Mac
>and can test it (b) the original code should b
>Speaking about OpenSSL for Macintosh. In March a guy wrote to
>openssl-dev:
>
>> From: CJ Holmes
>> Subject: OpenSSL on the MacOS
>> Date: Wed, 3 Mar 1999 23:56:36 -0500
>>
>> I had just finished porting SSLeay 0.9.0 to MacOS 8.x when I learned (quite
>> by accident) that it had become OpenSS
You said:
>Roy,
>I ported SSLeay to an embedded system whose OS didn't have
>unix-style sockets, what I ended up doing was writing "wrapper"
>functions ("socket", "bind" etc) which had the same names as the
>unix calls but internally used the embedded systems API to actually
>do anything.
T
You said:
>Is there API documentation available for OpenSSL? The fragments at
>www.openssl.org/docs/ are somewhat minimalistic, alas.
I'll say.
I haven't found much anything either. It seems the source is the best
reference-- and it's huge.
Please let me know if you find anything
-Roy
>All endianness problems should be handled by ntoh... and
>hton... macros/functions. I have never checked whether everything is
>really done right, but if handled correctly, things like that don't
>cause problems.
Is OpenSSL running on any big-endian machines? (Uh oh-- I always get
that wrong.
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 sock
14 matches
Mail list logo
