- Dillo-dev - lists.mailman3.com

an experiment using mbed TLS

by eocene＠gmx.com

Nick wrote: > A bit premature here. I quickly ran ./configure before work and > configure worked OK. But tonight, run make, my linker bombed out with: > > /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld: > cannot find > -libmbedtls /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld: > cannot find > -libmbedx509 /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld: > cannot find -libmbedcrypto > > Strange, as ldconfig -v reveals: > > /usr/local/lib: > libmbedcrypto.so.0 -> libmbedcrypto.so.2.3.0 > libmbedtls.so.10 -> libmbedtls.so.2.3.0 > libmbedx509.so.0 -> libmbedx509.so.2.3.0 > > Anyway, an hour of investing, it turns out the linker flags are > incorrect - changing in configure fixed it up: > > if test "x$ssl_ok" = "xyes"; then > LIBSSL_LIBS="-libmbedtls -libmbedx509 -libmbedcrypto" > > Should be -lmbedtls, -lmbedx509 and -lmbedcrypto > > All really does build fine now :) > > mbedtls seems to work well - seems a tad quicker too. I don't know where you got the "-libmbedtls -libmbedx509 -libmbedcrypto" from. Mine has "-lmbedtls -lmbedx509 -lmbedcrypto", and it says "-lmbedtls -lmbedx509 -lmbedcrypto when I double-check on hg.dillo.org.

July 4, 2016

an experiment using mbed TLS

by nick＠linicks.net

On Mon, 4 Jul 2016 06:08:58 +0100 Nick Warne <nick at linicks.net> wrote: > On Sun, 3 Jul 2016 21:09:40 +0000 > eocene <eocene at gmx.com> wrote: > > > I wrote: > > > I wrote: > > > > Nick wrote: > > > > > OK, what do I need to do to build this after an hour of head > > > > > scratching: > > > Making the attached changes makes it succeed, although I've only > > > gotten just that far at the moment and haven't looked into whether > > > it's an error on their part or what... > > > > Their bug: https://github.com/ARMmbed/mbedtls/issues/522 > > Good catch - all builds fine now - thanks, A bit premature here. I quickly ran ./configure before work and configure worked OK. But tonight, run make, my linker bombed out with: /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld: cannot find -libmbedtls /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld: cannot find -libmbedx509 /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld: cannot find -libmbedcrypto Strange, as ldconfig -v reveals: /usr/local/lib: libmbedcrypto.so.0 -> libmbedcrypto.so.2.3.0 libmbedtls.so.10 -> libmbedtls.so.2.3.0 libmbedx509.so.0 -> libmbedx509.so.2.3.0 Anyway, an hour of investing, it turns out the linker flags are incorrect - changing in configure fixed it up: if test "x$ssl_ok" = "xyes"; then LIBSSL_LIBS="-libmbedtls -libmbedx509 -libmbedcrypto" Should be -lmbedtls, -lmbedx509 and -lmbedcrypto All really does build fine now :) mbedtls seems to work well - seems a tad quicker too. Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

July 4, 2016

an experiment using mbed TLS

by nick＠linicks.net

On Sun, 3 Jul 2016 21:09:40 +0000 eocene <eocene at gmx.com> wrote: > I wrote: > > I wrote: > > > Nick wrote: > > > > OK, what do I need to do to build this after an hour of head > > > > scratching: > > Making the attached changes makes it succeed, although I've only > > gotten just that far at the moment and haven't looked into whether > > it's an error on their part or what... > > Their bug: https://github.com/ARMmbed/mbedtls/issues/522 Good catch - all builds fine now - thanks, Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

July 4, 2016

an experiment using mbed TLS

by eocene＠gmx.com

I wrote: > I wrote: > > Nick wrote: > > > OK, what do I need to do to build this after an hour of head scratching: > > > > > > checking mbedtls/ssl.h usability... no > > > checking mbedtls/ssl.h presence... yes > > > configure: WARNING: mbedtls/ssl.h: present but cannot be compiled > > > configure: WARNING: mbedtls/ssl.h: check for missing prerequisite > > > headers? configure: WARNING: mbedtls/ssl.h: see the Autoconf > > > documentation configure: WARNING: mbedtls/ssl.h: section "Present > > > But Cannot Be Compiled" configure: WARNING: mbedtls/ssl.h: proceeding > > > with the compiler's result checking for mbedtls/ssl.h... no > > > configure: WARNING: *** mbed TLS 2 not found. Disabling SSL/HTTPS/TLS > > > support. *** > > > > IIRC, Jeremy was the closest we had to an autoconf expert, but he hasn't > > been around. > > > > Is anything interesting in the mbedtls region of the config.log file? > > > > I don't remember ever seeing quite that sort of set of warnings out > > of autoconf before. > > I was able to reproduce the problem by uninstalling mbed tls and then > pointing to it during configuration with CPPFLAGS to the include dir > and LDFLAGS to the lib dir. > > Making the attached changes makes it succeed, although I've only > gotten just that far at the moment and haven't looked into whether > it's an error on their part or what... Their bug: https://github.com/ARMmbed/mbedtls/issues/522

July 3, 2016

an experiment using mbed TLS

by eocene＠gmx.com

I wrote: > Nick wrote: > > OK, what do I need to do to build this after an hour of head scratching: > > > > checking mbedtls/ssl.h usability... no > > checking mbedtls/ssl.h presence... yes > > configure: WARNING: mbedtls/ssl.h: present but cannot be compiled > > configure: WARNING: mbedtls/ssl.h: check for missing prerequisite > > headers? configure: WARNING: mbedtls/ssl.h: see the Autoconf > > documentation configure: WARNING: mbedtls/ssl.h: section "Present > > But Cannot Be Compiled" configure: WARNING: mbedtls/ssl.h: proceeding > > with the compiler's result checking for mbedtls/ssl.h... no > > configure: WARNING: *** mbed TLS 2 not found. Disabling SSL/HTTPS/TLS > > support. *** > > IIRC, Jeremy was the closest we had to an autoconf expert, but he hasn't > been around. > > Is anything interesting in the mbedtls region of the config.log file? > > I don't remember ever seeing quite that sort of set of warnings out > of autoconf before. I was able to reproduce the problem by uninstalling mbed tls and then pointing to it during configuration with CPPFLAGS to the include dir and LDFLAGS to the lib dir. Making the attached changes makes it succeed, although I've only gotten just that far at the moment and haven't looked into whether it's an error on their part or what...

July 3, 2016

an experiment using mbed TLS

by eocene＠gmx.com

Nick wrote: > OK, what do I need to do to build this after an hour of head scratching: > > checking mbedtls/ssl.h usability... no > checking mbedtls/ssl.h presence... yes > configure: WARNING: mbedtls/ssl.h: present but cannot be compiled > configure: WARNING: mbedtls/ssl.h: check for missing prerequisite > headers? configure: WARNING: mbedtls/ssl.h: see the Autoconf > documentation configure: WARNING: mbedtls/ssl.h: section "Present > But Cannot Be Compiled" configure: WARNING: mbedtls/ssl.h: proceeding > with the compiler's result checking for mbedtls/ssl.h... no > configure: WARNING: *** mbed TLS 2 not found. Disabling SSL/HTTPS/TLS > support. *** IIRC, Jeremy was the closest we had to an autoconf expert, but he hasn't been around. Is anything interesting in the mbedtls region of the config.log file? I don't remember ever seeing quite that sort of set of warnings out of autoconf before.

July 3, 2016

an experiment using mbed TLS

by nick＠linicks.net

On Sun, 3 Jul 2016 19:03:42 +0100 Nick Warne <nick at linicks.net> wrote: > On Sun, 3 Jul 2016 16:37:56 +0000 > eocene <eocene at gmx.com> wrote: > > > Jorge wrote: > > > On Mon, Jun 20, 2016 at 10:10:54AM +0200, Johannes Hofmann > > > wrote: > > > > On Sun, Jun 19, 2016 at 08:48:28PM +0000, eocene wrote: > > > > > > > > > > I wanted to see what it would take to use mbed tls with dillo. > > > > > > > > > > I put a copy of the diff at > > > > > http://www.dillo.org/test/mbedtls.diff and I mention it here > > > > > in case someone should want that one day. > > > > > > > > Excellent. I like mbedtls (formerly known as PolarSSL). The code > > > > looks much saner to me than openssl. > > > > > > If you both agree it's a better lib than OpenSSL, +1. > > > > All right, then. *commits* > > > > If you need mbed TLS 2.x: https://tls.mbed.org/download > > Ha ha.... that got me. I updated Dillo, and found SSL sites don't > work. So I clicked on the above link... doesn't work as it is SSL :) OK, what do I need to do to build this after an hour of head scratching: checking mbedtls/ssl.h usability... no checking mbedtls/ssl.h presence... yes configure: WARNING: mbedtls/ssl.h: present but cannot be compiled configure: WARNING: mbedtls/ssl.h: check for missing prerequisite headers? configure: WARNING: mbedtls/ssl.h: see the Autoconf documentation configure: WARNING: mbedtls/ssl.h: section "Present But Cannot Be Compiled" configure: WARNING: mbedtls/ssl.h: proceeding with the compiler's result checking for mbedtls/ssl.h... no configure: WARNING: *** mbed TLS 2 not found. Disabling SSL/HTTPS/TLS support. *** Thanks, Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

July 3, 2016

an experiment using mbed TLS

by nick＠linicks.net

On Sun, 3 Jul 2016 16:37:56 +0000 eocene <eocene at gmx.com> wrote: > Jorge wrote: > > On Mon, Jun 20, 2016 at 10:10:54AM +0200, Johannes Hofmann wrote: > > > On Sun, Jun 19, 2016 at 08:48:28PM +0000, eocene wrote: > > > > > > > > I wanted to see what it would take to use mbed tls with dillo. > > > > > > > > I put a copy of the diff at > > > > http://www.dillo.org/test/mbedtls.diff and I mention it here in > > > > case someone should want that one day. > > > > > > Excellent. I like mbedtls (formerly known as PolarSSL). The code > > > looks much saner to me than openssl. > > > > If you both agree it's a better lib than OpenSSL, +1. > > All right, then. *commits* > > If you need mbed TLS 2.x: https://tls.mbed.org/download Ha ha.... that got me. I updated Dillo, and found SSL sites don't work. So I clicked on the above link... doesn't work as it is SSL :) Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

July 3, 2016

an experiment using mbed TLS

by eocene＠gmx.com

Jorge wrote: > On Mon, Jun 20, 2016 at 10:10:54AM +0200, Johannes Hofmann wrote: > > On Sun, Jun 19, 2016 at 08:48:28PM +0000, eocene wrote: > > > > > > I wanted to see what it would take to use mbed tls with dillo. > > > > > > I put a copy of the diff at http://www.dillo.org/test/mbedtls.diff > > > and I mention it here in case someone should want that one day. > > > > Excellent. I like mbedtls (formerly known as PolarSSL). The code > > looks much saner to me than openssl. > > If you both agree it's a better lib than OpenSSL, +1. All right, then. *commits* If you need mbed TLS 2.x: https://tls.mbed.org/download If you watch the MSGs, you'll see I've turned off the certificate chain printing and instead show a more concise summary at shutdown of which root certificates were used to verify communication with which servers. And at startup it'll tell you how many such certificates you are trusting. By default, I had 174, but I've trimmed them down on this computer to...twenty at the moment because I never need the ones from certificate authorities in China, Turkey, Hungary, etc.

July 3, 2016

valgrind errors

by sgeerken＠dillo.org

On Mi, Jun 22, 2016, eocene wrote: > Another one is containerAllocationState not getting initialized in > OOFPositionedMgr. Fixed, too. Sebastian

June 26, 2016