Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] dillo
Date: Thu, 9 Jan 2020 21:50:25 +0100	[thread overview]
Message-ID: <20200109215025.377ae5b8@gmx.net> (raw)
In-Reply-To: <372b903d-cd05-28bd-b1ba-7ac3314ee165@cam.ac.uk>

Hello Jonathan

added CC buildroot at buildroot.org

On Thu, 9 Jan 2020 17:09:12 +0000, Jonathan Kimmitt <jrrk2@cam.ac.uk> wrote:

> Dear Peter,
>
> Are you a maintainer for the dillo port to buildroot? If so I have some
> patches for you

Yes, somehow...

>
> concerning SSL compatibility, relative to the 2019.11 release. No doubt
> they need reworking to be upstream worthy.

Thanks for the patches, some remarks:

- 0003-SSL_library_init.patch

> SSL_library_init is now a #define, causing this check to fail ...
>
> --- a/configure.ac	2020-01-09 14:57:27.823065488 +0000
> +++ b/configure.ac	2020-01-09 14:59:35.735065000 +0000
> @@ -276,7 +276,7 @@
>
>    if test "x$ssl_ok" = "xyes"; then
>      old_libs="$LIBS"
> -    AC_CHECK_LIB(ssl, SSL_library_init, ssl_ok=yes, ssl_ok=no, -lcrypto)
> +    AC_CHECK_LIB(ssl, OPENSSL_init_ssl, ssl_ok=yes, ssl_ok=no, -lcrypto)
>      LIBS="$old_libs"
>    fi

Which openssl provider/library did you use, openssl (BR2_PACKAGE_LIBOPENSSL=y) or
libressl (BR2_PACKAGE_LIBRESSL=y)?

Will test/check your patch (but needs some time, I am no daily dillo user ;-) )...


- 0004-certificate.patch

> --- a/dpi/https.c	2015-06-30 15:06:08.000000000 +0100
> +++ b/dpi/https.c	2020-01-09 15:28:25.843058400 +0000
> @@ -475,9 +475,12 @@
>           break;
>        case X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT:
>           /*Either self signed and untrusted*/
> +#if 0
>           /*Extract CN from certificate name information*/
>           if ((cn = strstr(remote_cert->name, "/CN=")) == NULL) {
> -            strcpy(buf, "(no CN given)");
> +#endif
> +           strcpy(buf, "(no CN given)");
> +#if 0
>           } else {
>              char *cn_end;
>
> @@ -489,6 +492,7 @@
>              strncpy(buf, cn, (size_t) (cn_end - cn));
>              buf[cn_end - cn] = '\0';
>           }
> +#endif
>           msg = dStrconcat("The remote certificate is self-signed and "
>                            "untrusted.\nFor address: ", buf, NULL);
>           d_cmd = a_Dpip_build_cmd(

This one looks like upstream commit 'Support OpenSSL 1.1.0' ([1]) and
according to the mercurial info should be contained in the 3.0.5
release (in case I read the mercurial info right), but seems not to
be contained in the dillo-3.0.5.tar.bz2 sources...

Regards,
Peter

[1] https://hg.dillo.org/dillo/rev/b171b8610400

>
> Regards,
>
> Jonathan Kimmitt
>
>
>

       reply	other threads:[~2020-01-09 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <372b903d-cd05-28bd-b1ba-7ac3314ee165@cam.ac.uk>
2020-01-09 20:50 ` Peter Seiderer [this message]
2020-01-09 21:29   ` [Buildroot] dillo Peter Seiderer
     [not found]     ` <b192f7f2-e7c8-45c3-0fd5-a9c2db78a92d@cam.ac.uk>
2020-01-10 19:53       ` Peter Seiderer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200109215025.377ae5b8@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox