• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Including libcrypto.0.9.7.dylib for backwards compatibility
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Including libcrypto.0.9.7.dylib for backwards compatibility


  • Subject: Re: Including libcrypto.0.9.7.dylib for backwards compatibility
  • From: Daniel Jalkut <email@hidden>
  • Date: Sat, 05 Nov 2005 03:00:37 -0500

I had to do something like this a while back. I had trouble getting the dynamic libraries included in the application's Frameworks folder to take precedence over the system-installed ones. Since the application I was working on needed libcrypto and libssl unconditionally, I just compiled them in directly as static libraries. This required building the libraries myself, but it worked well in the end, and provided a completely self-contained solution.

Daniel

On Nov 5, 2005, at 2:41 AM, Nick Ptacek wrote:

I'm currently working on a project utilizing the AES encryption calls
included in <openssl/aes.h>.  I'm compiling the project in Xcode 2.1
on OS X 10.4.3, and it runs just fine on OS X 10.3 and higher.
However, I would like to include compatibility for OS X 10.2 and
higher, which is not possible (as far as I have been able to
determine), due to the fact that libcrypto on OS X 10.2 does not
include access to the AES calls.  I've found various references to
projects that have included a copy of libcrypto.0.9.7.dylib in the
built application, but I'm not quite sure how to go about including
the file in my program distribution.  If anyone could shed any light
on this, it would be greatly appreciated.

I realize that I could switch to another encryption format (such as
blowfish or des), which would function on older distributions of
libcrypto, however if it is easier to just include a copy of the newer
version of libcrypto with my application, I would like to do so.

Thanks for any tips or insights on how to accomplish this task!

- Nicholas Ptacek
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
sweater.com


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Including libcrypto.0.9.7.dylib for backwards compatibility (From: Nick Ptacek <email@hidden>)

  • Prev by Date: Including libcrypto.0.9.7.dylib for backwards compatibility
  • Next by Date: NSPropertyDescription userInfo
  • Previous by thread: Including libcrypto.0.9.7.dylib for backwards compatibility
  • Next by thread: NSPropertyDescription userInfo
  • Index(es):
    • Date
    • Thread