December 2011 - Dillo-dev - lists.mailman3.com

dillo-3.0.2 released

by corvid＠lavabit.com

It's official! http://www.dillo.org/download/dillo-3.0.2.tar.bz2 http://www.dillo.org/download/dillo-3.0.2.tar.bz2.asc And, for good measure, the sha1sum is still... 1d1258ee7d18c8ca0eabaf100f2f611c6be03f87 as it was for the rc. Thanks everyone!

Dec. 5, 2011

IPv6 and HTTPS (Re: release candidate for dillo-3.0.2)

by Johannes.Hofmann＠gmx.de

On Sun, Dec 04, 2011 at 11:05:15AM -0500, Benjamin Johnson wrote: > Johannes wrote: > > >I doubt it's worth making the current experimental HTTPS plugin > >IPv6 ready. > >We will need a more robust HTTPS solution at some point. > > Cheers, > >Johannes > > Why not just reuse the existing HTTP code? > > *cough* > > http://dillo-win32.sourceforge.net/patches/07-dfcntl.diff > http://dillo-win32.sourceforge.net/patches/08-dsock.diff > http://dillo-win32.sourceforge.net/patches/17-https.diff > > Just add some warning dialogs and you've got everything the plugin > offers, plus greater efficiency, code reuse, IPv6, etc. > > (Not to mention, it's thoroughly tested and quite stable on Linux, > BSD, that other OS with 99% market share, etc. I use it myself > every day.) > > Anyway, all my code's still there if you're interested. Thanks for the offer. Currently the patches don't seem to apply cleanly and they also mix in WIN32 compatibility code. So integration work is needed and also an in depth review of the certificate handling. Cheers, Johannes

Dec. 4, 2011

IPv6 and HTTPS (Re: release candidate for dillo-3.0.2)

by obeythepenguin＠gmail.com

Johannes wrote: > I doubt it's worth making the current experimental HTTPS plugin > IPv6 ready. > We will need a more robust HTTPS solution at some point. > Cheers, > Johannes Why not just reuse the existing HTTP code? *cough* http://dillo-win32.sourceforge.net/patches/07-dfcntl.diff http://dillo-win32.sourceforge.net/patches/08-dsock.diff http://dillo-win32.sourceforge.net/patches/17-https.diff Just add some warning dialogs and you've got everything the plugin offers, plus greater efficiency, code reuse, IPv6, etc. (Not to mention, it's thoroughly tested and quite stable on Linux, BSD, that other OS with 99% market share, etc. I use it myself every day.) Anyway, all my code's still there if you're interested. Cheers, ~Benjamin

Dec. 4, 2011

IPv6 and HTTPS (Re: release candidate for dillo-3.0.2)

by jcid＠dillo.org

On Sat, Dec 03, 2011 at 10:41:50PM +0100, Johannes Hofmann wrote: > On Sat, Dec 03, 2011 at 09:23:41PM +0000, corvid wrote: > > Axel wrote: > > > IPv6 and HTTPS seem both to work independently, but HTTPS over IPv6 > > > does not work. An example host would be the IPv6-only reachable server > > > at https://jumper.deuxchevaux.org/. (Submitted to the bug database as > > > bug #1023.) > > > > > > The same host with just HTTP (http://jumper.deuxchevaux.org/) works > > > fine as well as does a randomly chosen (IPv4 :-) HTTPS website. > > > > > > OTOH with 3.0.1 it looks very similar and doesn't work either with > > > IPv6 + HTTPS, so I think it's "just" a bug in Dillo, but not a > > > regression in 3.0.2. :-) > > > > Is anyone in a sufficiently IPv6-ed environment that they can dig into > > this at some point? > > I doubt it's worth making the current experimental HTTPS plugin > IPv6 ready. > We will need a more robust HTTPS solution at some point. Ditto. -- Cheers Jorge.-

Dec. 4, 2011

IPv6 and HTTPS (Re: release candidate for dillo-3.0.2)

by Johannes.Hofmann＠gmx.de

On Sat, Dec 03, 2011 at 09:23:41PM +0000, corvid wrote: > Axel wrote: > > IPv6 and HTTPS seem both to work independently, but HTTPS over IPv6 > > does not work. An example host would be the IPv6-only reachable server > > at https://jumper.deuxchevaux.org/. (Submitted to the bug database as > > bug #1023.) > > > > The same host with just HTTP (http://jumper.deuxchevaux.org/) works > > fine as well as does a randomly chosen (IPv4 :-) HTTPS website. > > > > OTOH with 3.0.1 it looks very similar and doesn't work either with > > IPv6 + HTTPS, so I think it's "just" a bug in Dillo, but not a > > regression in 3.0.2. :-) > > Is anyone in a sufficiently IPv6-ed environment that they can dig into > this at some point? I doubt it's worth making the current experimental HTTPS plugin IPv6 ready. We will need a more robust HTTPS solution at some point. Cheers, Johannes

Dec. 3, 2011

IPv6 and HTTPS (Re: release candidate for dillo-3.0.2)

by corvid＠lavabit.com

Axel wrote: > IPv6 and HTTPS seem both to work independently, but HTTPS over IPv6 > does not work. An example host would be the IPv6-only reachable server > at https://jumper.deuxchevaux.org/. (Submitted to the bug database as > bug #1023.) > > The same host with just HTTP (http://jumper.deuxchevaux.org/) works > fine as well as does a randomly chosen (IPv4 :-) HTTPS website. > > OTOH with 3.0.1 it looks very similar and doesn't work either with > IPv6 + HTTPS, so I think it's "just" a bug in Dillo, but not a > regression in 3.0.2. :-) Is anyone in a sufficiently IPv6-ed environment that they can dig into this at some point? > Otherwise 3.0.2 RC1 looks fine for me. :-) Thanks :)

Dec. 3, 2011

Dillo temporary directory

by obeythepenguin＠gmail.com

Jorge wrote: > On Sat, Dec 03, 2011 at 09:11:48AM +0100, Georg Potthast wrote: > > I observe that Dillo changes the current directory to "\tmp" when > > running. Why does it do that and what files shall be written into > > this directory? > No files, Dillo tries to work from an unmounted directory. > -- Cheers > Jorge.- But *why* does Dillo work from an unmounted directory? What advantage does this provide, especially if Dillo does not write any files there? (As a side note, /tmp _is_ mounted on many systems, like OpenBSD.) Cheers, ~Benjamin

Dec. 3, 2011

release candidate for dillo-3.0.2

by jcid＠dillo.org

On Fri, Dec 02, 2011 at 09:46:22PM +0000, corvid wrote: > Jorge wrote: > > AFAIR, libpng detection was an issue (not only for us), and it > > took a long time to come with something that worked across all > > the different platforms we were testing. > > What we can glean from good old CVS is: > > > In December 2004, the test changed from > which libpng12-config || which libpng-config || which libpng10-config > to a bunch of separate whiches because > "Fixed a libpng detection problem (e.g., on CYGWIN). BUG#651". > Of course, BUG#651 is long gone, but presumably the problem was the "||". > > > In January 2004, we go from > PNG_CONFIG="`which libpng-config || which libpng12-config`" > to > PNG_CONFIG=`which libpng12-config || which libpng-config || which libpng10-config` > (along with general restructuring) > Then if we follow that to the archive, > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-January/001683.html > the libpng talk is of Slackware 3.9, which came out in May, 1999. > A quoted msg from Jorgen doesn't appear to be in the archive. > > Looking at http://slackware.cs.utah.edu/pub/slackware/slackware-3.9/slakware/MANIFEST.… > Slackware 3.9 used libpng-1.0.3, and did not have a png-config of any > sort that I can see. > > Looking at the CHANGES file with my copy of libpng shows that png-config > showed up during the 1.2.x series. > > Earlier in January, > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-January/001615.html > says that libpng 1.2.5 needed to be added to the Slackware 3.9 system to > make dillo happy. > > Overall, the messages give every appearance of saying that dillo should > start with trying the libpng-config system but then still work on > systems that predate libpng-config. > > Looking at the change made, yeah, I guess that pre-libpng-config system > mustn't have had libpng stuff in the right places to get by with CPPFLAGS > as they were, hence added code that, if there was no libpng-config at all > and there was png.h, then add in 'LIBPNG_LIBS="-lpng -lm"' ourselves. > > libpng configuration checking was introduced in March 2003. > This leads back to > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-March/000390.html > where nothing brought up seems to have bearing on the matter at hand here. > > > Nothing reveals itself in the extant archaeological record suggesting > that the various libpng-configs themselves were an issue. Sorry if my meaning/wording wasn't clear. I meant, "it took some effort to sort the detection code so it finally was able to compile automatically accross all the different platforms we were testing" (some had libpng-config, some not, some had both installed at the same time IIRC). -- Cheers Jorge.-

Dec. 3, 2011

Dillo-dev Digest, Vol 76, Issue 1

by jcid＠dillo.org

On Sat, Dec 03, 2011 at 09:11:48AM +0100, Georg Potthast wrote: > I observe that Dillo changes the current directory to "\tmp" when > running. Why does it do that and what files shall be written into > this directory? No files, Dillo tries to work from an unmounted directory. -- Cheers Jorge.-

Dec. 3, 2011

release candidate for dillo-3.0.2

by jcid＠dillo.org

On Thu, Dec 01, 2011 at 03:18:53AM +0000, corvid wrote: > > I just put up an rc at > http://www.dillo.org/download/dillo-3.0.2-rc1.tar.bz2 > > $ sha1sum dillo-3.0.2-rc1.tar.bz2 > 1d1258ee7d18c8ca0eabaf100f2f611c6be03f87 dillo-3.0.2-rc1.tar.bz2 > > Please test :) I've being using it for a few days and it compiles and works very well on amd64 (x86_64 GNU/Linux). -- Cheers Jorge.-

Dec. 3, 2011