I will provide a broken example of the source to anyone who wants it. The
example
code has no real function it is just used to illustrate the problem. Contact
me at
[EMAIL PROTECTED]

--ian

> I have tried using static libraries and it works fine. But to distribute
> the utility with
> EXPORT functions I need to make it a shared object so a third party vendor
> (shopping
> cart) can use the utilities in their application software.
> I plan to make the "interface" public but I have to remove the underlying
> message protocol
> code. I work for a payment services company and I am not allowed to
> release that
> information.
> Sorry I am not "replying" in between the lines. I am using this mail list
> through
> http://marc.theaimsgroup.com/?l=openssl-users
> and I can't seem to reply using it...only read. If you have a better
> discussion site please
> let me know.
> 
> --ian
> 
> >What if you build it into a static lib? Just wondering. Are you planning
> to make your interface code public domain? 
> ------------------------------------------
> 
> Sorry for the "double" I forgot to attach the working/broken example
> 
> 
> OS           : solaris 2.6
> openSSL      : 0.9.5a  and 0.9.6
> gcc 2.95.2
> ld (gnu binutils 2.10 and solaris native ld )
> 
> I am trying to use OpenSSL libraries to create a combined cryptographic
> shared object
> utility. A shared object is built using custom interface software calling
> OpenSSL
> functions for use in third party applications needing crytographic
> capabilities. 
> The shared object exports only the custom interface to comply with US
> crytographic
> export regulations.
> 
> Custom object files and the OpenSSL object files are linked to produce a
> shared
> object file which can be dynamically called by a third party application. 
> On solaris 2.6 :
> OpenSSL 0.9.5a/0.9.6 compile and test correctly.
> The combined shared object is correctly compiled and produces no compile
> time errors when
> linked into an executable application. The application will then not run
> and solaris 2.6 states  
> "pfpro: Exec format error. Binary file is not executable."
> A subsequent 'file' command states the executable is a valid ELF 32-bit
> MSB executable.
> 
> I have compiled the EXACT same code and makefile on solaris 2.7 and linux
> Red Hat 6.x 
> and it works correctly. ONLY solaris 2.6 with the shared object linking
> fails to produce
> a valid binary. Linking the 'pfpro' binary with the static version of the
> combined
> library (custom interface + OpenSSL) produces a working executable on
> solaris 2.6.
> 
> I have tried various things to determine the problem.
> 
> 1) I have used gcc and gnu linker. no dice
> 
> 2) gcc and solaris linker. no dice
> 
> 3) compiled the combined shared object and moved it to solaris 2.7 to link
> with executable 
>    and it works. So it seems the shared object is getting produced
> correctly on sol 2.6 
>    its the linking with the executable that fails.
>    
> 4) I have compiled the shared object and the binary on sol. 2.7 and moved
> them
>    to a sol 2.6 box and everything works.
> 
> 5) compiled the code on a solaris 2.5.1 box and everything works.
> 
> 6) I have compiled OpenSSL 9.5a/9.6 on solaris 2.7 and moved them to link
> in on solaris
>    2.6 and it fails to produce a valid executable.
> 
> 7) finally I have produced the combined shared object with RSA 1.0 SSLC.
> The executable
>   works correctly. Only the OpenSSL on solaris 2.6 fails.
> 
> ALL results point to the inability of solaris 2.6 to link in the combined
> OpenSSL and
> custom interface shared object to produce a working binary executable.
> solaris 2.6 will run an executable created on sol 2.7 but it will not
> properly produce
> the executable itself.
> 
> so.....any help would be greatly appreciated. I can use the RSA 1.0
> libraries, but I am
> a huge proponent of open source and I would prefer to use OpenSSL.
> 
> I hope I have fully explained the problem and my efforts. I have included
> a "working"
> version of this problem "ready" to compile.
> 
> If you need any further clarification please contact me at
> [EMAIL PROTECTED]
> 
> Thank you in advance for your time and efforts.
> 
> Sincerly,
> Ian Cain
> 
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to