SSLeay is not actually GPL, it's a custom license which allows commercial use:

* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
*    notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
*    notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software
*    must display the following acknowledgement:
*    "This product includes cryptographic software written by
*     Eric Young ([EMAIL PROTECTED])"
* The word 'cryptographic' can be left out if the rouines from the library
*    being used are not cryptographic related :-).
* 4. If you include any Windows specific code (or a derivative thereof) from * the apps directory (application code) you must include an acknowledgement: * "This product includes software written by Tim Hudson ([EMAIL PROTECTED])"


The pilotSSLeay distributions include static libraries (which put all the code in the first segment, leaving little room for your code) and glibs, which are not well documented and I've never been able to compile against (abeit the GCC docs imply that glibs are once again supported).

The "source" version of pilotSSLeay includes the headers and diffs to SSLeay, so if you want to recompile the libraries, you need the SSLeay code. The diffs are against SSLeay 0.8.1, which is no longer available. However, 0.8.1a is available, and the diffs can be applied with some straightforward hand tweaking.


OpenSSL is the continuation of SSLeay -- I don't know if the later versions include bugfixes to the RSA and RC5 code.


I'm currently trying to wrestle pilotSSLeay into a more usable form. I can send you the patched 0.8.1a code.


Can anyone point to directions for compiling against glibs under the current version of GCC (rather than the ancient patched versions referred to in glib documentation)?


--
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Reply via email to