[Buildroot] [PATCH 1/1] libcurl: fix building against libressl

[Buildroot] [PATCH 1/1] libcurl: fix building against libressl

[Adam Duskett]

LibreSSL 2.7.x breaks libcurl 7.59.0 with the error:
error: static declaration of ?OpenSSL_version_num? follows non-static
declaration

This failure has since been fixed upstream with commit:
https://github.com/curl/curl/commit/7c90c93c0b061da81f69fabdd57125b2783c15fb

Signed-off-by: Adam Duskett <aduskett@gmail.com>
---
 ...-curl-fix-building-against-libressl-2.7.2.patch | 91 ++++++++++++++++++++++
 1 file changed, 91 insertions(+)
 create mode 100644 package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch

diff --git a/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch b/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
new file mode 100644
index 0000000000..e5d6f686e8
--- /dev/null
+++ b/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
@@ -0,0 +1,91 @@
+From 7a67b6561da8e42505e09014a5c97b19e1a93532 Mon Sep 17 00:00:00 2001
+From: Adam Duskett <aduskett@gmail.com>
+Date: Fri, 13 Apr 2018 08:31:37 -0400
+Subject: [PATCH] curl: fix building against libressl 2.7.2
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+LibreSSL 2.7.x breaks libcurl 7.59.0 with the error:
+error: static declaration of ?OpenSSL_version_num? follows non-static
+declaration
+
+This failure has since been fixed upstream with commit:
+https://github.com/curl/curl/commit/7c90c93c0b061da81f69fabdd57125b2783c15fb
+
+Signed-off-by: Adam Duskett <aduskett@gmail.com>
+---
+ lib/vtls/openssl.c | 23 +++++++++++++++++------
+ 1 file changed, 17 insertions(+), 6 deletions(-)
+
+diff --git a/lib/vtls/openssl.c b/lib/vtls/openssl.c
+index 2a6b3cf..09b4ea6 100644
+--- a/lib/vtls/openssl.c
++++ b/lib/vtls/openssl.c
+@@ -104,13 +104,22 @@
+ #endif
+ 
+ #if (OPENSSL_VERSION_NUMBER >= 0x10100000L) && /* OpenSSL 1.1.0+ */ \
+-  !defined(LIBRESSL_VERSION_NUMBER)
++    !(defined(LIBRESSL_VERSION_NUMBER) && \
++      LIBRESSL_VERSION_NUMBER < 0x20700000L)
+ #define SSLEAY_VERSION_NUMBER OPENSSL_VERSION_NUMBER
+ #define HAVE_X509_GET0_EXTENSIONS 1 /* added in 1.1.0 -pre1 */
+ #define HAVE_OPAQUE_EVP_PKEY 1 /* since 1.1.0 -pre3 */
+ #define HAVE_OPAQUE_RSA_DSA_DH 1 /* since 1.1.0 -pre5 */
+ #define CONST_EXTS const
+ #define HAVE_ERR_REMOVE_THREAD_STATE_DEPRECATED 1
++
++/* funny typecast define due to difference in API */
++#ifdef LIBRESSL_VERSION_NUMBER
++#define ARG2_X509_signature_print (X509_ALGOR *)
++#else
++#define ARG2_X509_signature_print
++#endif
++
+ #else
+ /* For OpenSSL before 1.1.0 */
+ #define ASN1_STRING_get0_data(x) ASN1_STRING_data(x)
+@@ -128,7 +137,8 @@ static unsigned long OpenSSL_version_num(void)
+ #endif
+ 
+ #if (OPENSSL_VERSION_NUMBER >= 0x1000200fL) && /* 1.0.2 or later */ \
+-  !defined(LIBRESSL_VERSION_NUMBER)
++    !(defined(LIBRESSL_VERSION_NUMBER) && \
++      LIBRESSL_VERSION_NUMBER < 0x20700000L)
+ #define HAVE_X509_GET0_SIGNATURE 1
+ #endif
+ 
+@@ -147,7 +157,7 @@ static unsigned long OpenSSL_version_num(void)
+  * Whether SSL_CTX_set_keylog_callback is available.
+  * OpenSSL: supported since 1.1.1 https://github.com/openssl/openssl/pull/2287
+  * BoringSSL: supported since d28f59c27bac (committed 2015-11-19)
+- * LibreSSL: unsupported in at least 2.5.1 (explicitly check for it since it
++ * LibreSSL: unsupported in@least 2.7.2 (explicitly check for it since it
+  *           lies and pretends to be OpenSSL 2.0.0).
+  */
+ #if (OPENSSL_VERSION_NUMBER >= 0x10101000L && \
+@@ -259,7 +269,9 @@ static void tap_ssl_key(const SSL *ssl, ssl_tap_state_t *state)
+   if(!session || !keylog_file_fp)
+     return;
+ 
+-#if OPENSSL_VERSION_NUMBER >= 0x10100000L && !defined(LIBRESSL_VERSION_NUMBER)
++#if OPENSSL_VERSION_NUMBER >= 0x10100000L && \
++    !(defined(LIBRESSL_VERSION_NUMBER) && \
++      LIBRESSL_VERSION_NUMBER < 0x20700000L)
+   /* ssl->s3 is not checked in openssl 1.1.0-pre6, but let's assume that
+    * we have a valid SSL context if we have a non-NULL session. */
+   SSL_get_client_random(ssl, client_random, SSL3_RANDOM_SIZE);
+@@ -2082,8 +2094,7 @@ static CURLcode ossl_connect_step1(struct connectdata *conn, int sockindex)
+   case CURL_SSLVERSION_TLSv1_2:
+   case CURL_SSLVERSION_TLSv1_3:
+     /* it will be handled later with the context options */
+-#if (OPENSSL_VERSION_NUMBER >= 0x10100000L) && \
+-    !defined(LIBRESSL_VERSION_NUMBER)
++#if (OPENSSL_VERSION_NUMBER >= 0x10100000L)
+     req_method = TLS_client_method();
+ #else
+     req_method = SSLv23_client_method();
+-- 
+2.14.3
+
-- 
2.14.3

[Buildroot] [PATCH 1/1] libcurl: fix building against libressl

[Thomas Petazzoni]

Hello,

On Fri, 13 Apr 2018 08:39:31 -0400, Adam Duskett wrote:
> LibreSSL 2.7.x breaks libcurl 7.59.0 with the error:
> error: static declaration of ?OpenSSL_version_num? follows non-static
> declaration
> 
> This failure has since been fixed upstream with commit:
> https://github.com/curl/curl/commit/7c90c93c0b061da81f69fabdd57125b2783c15fb
> 
> Signed-off-by: Adam Duskett <aduskett@gmail.com>
> ---
>  ...-curl-fix-building-against-libressl-2.7.2.patch | 91 ++++++++++++++++++++++
>  1 file changed, 91 insertions(+)
>  create mode 100644 package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
> 
> diff --git a/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch b/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
> new file mode 100644
> index 0000000000..e5d6f686e8
> --- /dev/null
> +++ b/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
> @@ -0,0 +1,91 @@
> +From 7a67b6561da8e42505e09014a5c97b19e1a93532 Mon Sep 17 00:00:00 2001
> +From: Adam Duskett <aduskett@gmail.com>
> +Date: Fri, 13 Apr 2018 08:31:37 -0400
> +Subject: [PATCH] curl: fix building against libressl 2.7.2

Since the issue has been fixed upstream, the fix should be a backport
from upstream commit, not a different commit authored by you.

I.e:

$ git clone https://github.com/curl/curl.git
$ cd curl/
$ git checkout curl-7_59_0
$ git cherry-pick 7c90c93c0b061da81f69fabdd57125b2783c15fb
$ git format-patch HEAD^

and then edit the patch to add your Signed-off-by below the one from
the original author, and use that in package/libcurl/.

Could you rework your patch by doing this ? I could have done it
myself, but I preferred to explain the process for doing it properly :)

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [PATCH 1/1] libcurl: fix building against libressl

[Arnout Vandecappelle]

On 15-04-18 20:43, Thomas Petazzoni wrote:
> Hello,
> 
> On Fri, 13 Apr 2018 08:39:31 -0400, Adam Duskett wrote:
>> LibreSSL 2.7.x breaks libcurl 7.59.0 with the error:
>> error: static declaration of ?OpenSSL_version_num? follows non-static
>> declaration
>>
>> This failure has since been fixed upstream with commit:
>> https://github.com/curl/curl/commit/7c90c93c0b061da81f69fabdd57125b2783c15fb
>>
>> Signed-off-by: Adam Duskett <aduskett@gmail.com>
>> ---
>>  ...-curl-fix-building-against-libressl-2.7.2.patch | 91 ++++++++++++++++++++++
>>  1 file changed, 91 insertions(+)
>>  create mode 100644 package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
>>
>> diff --git a/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch b/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
>> new file mode 100644
>> index 0000000000..e5d6f686e8
>> --- /dev/null
>> +++ b/package/libcurl/0001-curl-fix-building-against-libressl-2.7.2.patch
>> @@ -0,0 +1,91 @@
>> +From 7a67b6561da8e42505e09014a5c97b19e1a93532 Mon Sep 17 00:00:00 2001
>> +From: Adam Duskett <aduskett@gmail.com>
>> +Date: Fri, 13 Apr 2018 08:31:37 -0400
>> +Subject: [PATCH] curl: fix building against libressl 2.7.2
> 
> Since the issue has been fixed upstream, the fix should be a backport
> from upstream commit, not a different commit authored by you.
> 
> I.e:
> 
> $ git clone https://github.com/curl/curl.git
> $ cd curl/
> $ git checkout curl-7_59_0
> $ git cherry-pick 7c90c93c0b061da81f69fabdd57125b2783c15fb

 Use git cherry-pick -x -s. This will add your Sob right away, and it will
record the upstream commit from which it was taken.

> $ git format-patch HEAD^

 And here, of course, you need to add -N (well, not in this case since it's just
a single patch, but in general).


> and then edit the patch to add your Signed-off-by below the one from
> the original author, and use that in package/libcurl/.
> 
> Could you rework your patch by doing this ? I could have done it
> myself, but I preferred to explain the process for doing it properly :)

 This should be added to the manual...

 Regards,
 Arnout

> 
> Thanks!
> 
> Thomas
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] [PATCH 1/1] libcurl: fix building against libressl

[Thomas Petazzoni]

Hello,

On Tue, 17 Apr 2018 13:41:08 +0200, Arnout Vandecappelle wrote:

> > I.e:
> > 
> > $ git clone https://github.com/curl/curl.git
> > $ cd curl/
> > $ git checkout curl-7_59_0
> > $ git cherry-pick 7c90c93c0b061da81f69fabdd57125b2783c15fb  
> 
>  Use git cherry-pick -x -s. This will add your Sob right away, and it will
> record the upstream commit from which it was taken.

Aah, didn't about -x, definitely useful!

> > $ git format-patch HEAD^  
> 
>  And here, of course, you need to add -N (well, not in this case since it's just
> a single patch, but in general).

Yes, but indeed since it was a single patch, I omitted the -N.

> > Could you rework your patch by doing this ? I could have done it
> > myself, but I preferred to explain the process for doing it properly :)  
> 
>  This should be added to the manual...

True. Honestly, I find our manual badly organized, and I never find
where things should be added. I'm not against writing documentation
(see my e-mail about the changes to the download infrastructure), but I
never find *where* to put those details into our manual.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com