>There are some issues with a US company exporting anything dealing with
>crypto - you may have heard that our government frowns on such practices
>;-) .
Ah yes-- the US government. Same government that grants all those
software patents, right? :-)
>However, since a diff file doesn't contain any actual algorithms I've been
>TYRING to get the corporate lawyers to look at the situation and advise us
>on whether or not we can push the changes back to OpenSSL. It would make
>me happy to not re-port OpenSSL every time a new release comes out. It is
>a two-day, error prone process.
That's what I'm hoping to avoid, actually. I figure that getting my
changes in would make it easier to stay current, too.
>All of the work I've done is in the Crypto and SSL directories. I haven't
>touched the applications. Many of the changes were just a matter of not
>#including files in the sys/stat directory - the Mac doesn't have them and
>most of the files that include them don't even use them.
Yup-- same here.
>>My biggest criticism of my code is that it's not
>>suitable for a high-performance application, such as a webserver (it uses
>>polling/busy-waiting, rather than doing everything in the notification
>>routine).
>
>My solution was to build a BIO method around our existing network
>functions. That doesn't really help with anything in the apps folder,
>though.
That sounds more elegant than my solution. If you can get yours
released, that'd be a better way to go forward, IMHO.
-Roy
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
