Re: OpenSSL deprecation warnings under Xcode

From: Kyle J. McKay <mackyle@gmail.com>
Date: Dec 1, 2014, 17:51 UTC
Message-ID: <5DF49984-B22E-4BC2-A4B6-8DC9EECEC8B4@gmail.com>
In-Reply-To: <547BFD42.3040104@web.de>

On Nov 30, 2014, at 21:31, Torsten Bögershausen wrote:

Show 16 quoted lines

> On 12/01/2014 04:02 AM, Michael Blume wrote:
>> I have no idea whether this should concern anyone, but my mac build  
>> of git shows
>>
>>     CC imap-send.o
>> imap-send.c:183:36: warning: 'ERR_error_string' is deprecated: first
>> deprecated in OS X 10.7 [-Wdeprecated-declarations]
>>         fprintf(stderr, "%s: %s\n", func,
>> ERR_error_string(ERR_get_error(), NULL));
>>                                           ^
> []
> Isn't the warning a warning ;-)
> I don't see this warnings because my openssl comes from /opt/local/ 
> include (Mac ports)
> Does anybody know which new functions exist in Mac OS X versions >=  
> 10.7  ?

 From [1]:

Show 5 quoted lines

> In addition to these APIs, a number of open source tools use OpenSSL  
> for secure networking. If you use OpenSSL in your publicly shipping  
> apps, you must provide your own copy of the OpenSSL libraries,  
> preferably as part of your app bundle; the OpenSSL libraries that OS  
> X provides are deprecated.

So using the version from Mac Ports is the right idea to avoid the problem. You can always define NO_OPENSSL. imap-send.c has a --curl option now. (Which presumably automatically becomes the default if you define NO_OPENSSL and not NO_CURL?)

--Kyle

[1] <https://developer.apple.com/library/mac/documentation/security/Conceptual/cryptoservices/SecureNetworkCommunicationAPIs/SecureNetworkCommunicationAPIs.html 
 >