July 2016 - Dillo-dev - lists.mailman3.com

cppcheck on Dillo source

by jcid＠dillo.org

Hi, On Sat, Jul 09, 2016 at 03:28:25PM +0100, Nick Warne wrote: > On Sat, 9 Jul 2016 12:35:10 +0100 > Nick Warne <nick at linicks.net> wrote: > > > Hi all, > > > > While waiting for the Tour De France to start on TV, I ran cppcheck on > > Dillo source for something to do - a few errors were picked up! > > > > I have compacted the findings (with two comments from me)and attached > > it as a plain text file. > > > > Keep up the great work guys and thanks! > > > > Nick > > OK, updating cppcheck to 1.74, I ran it again. A new error appears, but > I don't know if it is a false positive, as I still don't really > understand C++ (but do get the logic of function calls vs void etc.: > > Checking ../../slackbuilds/dillo/hg/dillo/src/ui.cc... > [../../slackbuilds/dillo/hg/dillo/src/ui.cc:574]: (error) Return value > of allocation function 'make_filemenu_button' is not stored. > [../../slackbuilds/dillo/hg/dillo/src/ui.cc:588]: (error) Return value > of allocation function 'make_filemenu_button' is not stored. > > Now, the call is: > > make_filemenu_button(); > > to: > > Fl_Widget *UI::make_filemenu_button() > > which returns (btn) > > so is that correct? Where does (btn) go in the calling function - or > what does it do? Patch committed. It wasn't necessary anymore. Most probably it remained from a time when it was used. Now they are stored in local variables so it's safe to make the function void. -- Cheers Jorge.-

July 12, 2016

cppcheck on Dillo source

by jcid＠dillo.org

Hi Nick, On Sat, Jul 09, 2016 at 12:35:10PM +0100, Nick Warne wrote: > Hi all, > > While waiting for the Tour De France to start on TV, I ran cppcheck on > Dillo source for something to do - a few errors were picked up! > > I have compacted the findings (with two comments from me)and attached it > as a plain text file. Thanks for the report. I personally didn't know of cppcheck. We have used several code cleanup tools in the past and we usually honour them as sometimes they catch important flaws. A bunch of patches was just committed. You may peruse them with "hg log -vp" for the details/explanations. > Checking ../../slackbuilds/dillo/hg/dillo/dpi/file.c... > [../../slackbuilds/dillo/hg/dillo/dpi/file.c:356]: (error) syntax error > > if S_ISDIR (finfo->mode) { > Nick-> maybe?: > if (S_ISDIR (finfo->mode)) { Done. > Checking ../../slackbuilds/dillo/hg/dillo/dpid/dpid.c... > [../../slackbuilds/dillo/hg/dillo/dpid/dpid.c:465]: (error) Resource leak: dpidrc_stream > > return -1; > Nick-> maybe?: > return (-1); Done. > Checking ../../slackbuilds/dillo/hg/dillo/dw/hyphenator.cc... > [../../slackbuilds/dillo/hg/dillo/dw/hyphenator.cc:570]: (warning) %u in format > string (no. 1) requires 'unsigned int *' but the argument type is 'int *'. > Checking ../../slackbuilds/dillo/hg/dillo/dw/hyphenator.cc... > [../../slackbuilds/dillo/hg/dillo/dw/hyphenator.cc:570]: (warning) %u in format > string (no. 2) requires 'unsigned int *' but the argument type is 'int *'. It may be a trivial s/%u/%d/, but after reading it a bit I'd prefer Sebastian to double check it. Not committed. > > Checking ../../slackbuilds/dillo/hg/dillo/dw/iterator.cc... > [../../slackbuilds/dillo/hg/dillo/dw/iterator.cc:124]: (error) Memory leak: eit3 Done. AFAICS, this is a false positive. Patched to please cppcheck anyway. > > Checking ../../slackbuilds/dillo/hg/dillo/dw/ooffloatsmgr.cc... > [../../slackbuilds/dillo/hg/dillo/dw/ooffloatsmgr.cc:654]: (error) Possible null pointer dereference: vloat Well, the code should never reach there. Not changed. @Sebastian, BTW, coincidentally I'm using something like: SortedFloatsVector *list; list = isSubRefLeftFloat(ref) ? leftFloats : rightFloats; Float *vloat = list->get (getFloatIndexFromSubRef (ref)); in some patches I have, which also silence cppcheck. But maybe the original construct was meant for adding more options (like absolute positioned floats), but those may end in a third floats array, so I'm not sure. Is it safe to use the above construct, or should I leave it as is? > Checking ../../slackbuilds/dillo/hg/dillo/lout/container.cc... > [../../slackbuilds/dillo/hg/dillo/lout/container.cc:143]: (error) Common realloc mistake: 'array' nulled but not freed upon failure > [../../slackbuilds/dillo/hg/dillo/lout/container.cc:177]: (error) Common realloc mistake: 'array' nulled but not freed upon failure Done. > Checking ../../slackbuilds/dillo/hg/dillo/lout/misc.cc... > [../../slackbuilds/dillo/hg/dillo/lout/misc.cc:172]: (error) Common realloc mistake: 'bits' nulled but not freed upon failure Done. > Truck loads of: > Checking ../../slackbuilds/dillo/hg/dillo/src/md5.c: ARCH_IS_BIG_ENDIAN... > [../../slackbuilds/dillo/hg/dillo/src/md5.c:216]: (error) Uninitialized variable: X > in md5.c Untouched: I'm not md5 savvy. Maybe corvid. -- Cheers Jorge.-

July 12, 2016

Problem related to generated content

by sgeerken＠dillo.org

At least it can be worked around by the user by switching off CSS, so this is not a blocker for a new release. Sebastian On Di, Jul 05, 2016, Sebastian Geerken wrote: > Hi! > > I've come upon an interesting problem. Consider this HTML (stripped > down from a real world example): > > <head> > <style> > .fc:after { > content: ""; > display: block; > clear: both; > } > </style> > </head> > <body> > <div class="fc"> > <div style="float: left">main</div> > </div> > <div style="background:#404040; color:#ffffff">footer</div> > </body> > > Firefox (and probably other browsers) renders black text "main" on > white background above white text "footer" on dark gray background. > Dillo 3.0.5 does the same, for the simple reason that it does not > support floats. Dillo 3.1-dev, however, renders black text "main" and > white text "footer" side by side on dark gray background, because > "main" is within a float. (Which is, of course, difficult to read.) > > The reason why Firefox renders this as it does: the definition within > <style> generates something like a block element before the text > containing "footer", with "clear: both" as CSS attributes; something > like: > > <body> > <div class="fc"> > <div style="float: left">main</div> > </div> > <div style="clear:both"></div> > <div style="background:#404040; color:#ffffff">footer</div> > </body> > > Aside from the fact that dillo has still problems with this ("footer" > is too much to the right; I'll investigate this independently), this > shows that dillo's limited capabilities regarding generated content, > together with floats, causes some unpleasing rendering errors, which > are furthermore laborious to analyse (and thus not so simple to > be ignored). Has someone a feasible idea to deal with this? > > Sebastian > _______________________________________________ > Dillo-dev mailing list > Dillo-dev at dillo.org > http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev

July 10, 2016

cppcheck on Dillo source

by nick＠linicks.net

On Sat, 9 Jul 2016 12:35:10 +0100 Nick Warne <nick at linicks.net> wrote: > Hi all, > > While waiting for the Tour De France to start on TV, I ran cppcheck on > Dillo source for something to do - a few errors were picked up! > > I have compacted the findings (with two comments from me)and attached > it as a plain text file. > > Keep up the great work guys and thanks! > > Nick OK, updating cppcheck to 1.74, I ran it again. A new error appears, but I don't know if it is a false positive, as I still don't really understand C++ (but do get the logic of function calls vs void etc.: Checking ../../slackbuilds/dillo/hg/dillo/src/ui.cc... [../../slackbuilds/dillo/hg/dillo/src/ui.cc:574]: (error) Return value of allocation function 'make_filemenu_button' is not stored. [../../slackbuilds/dillo/hg/dillo/src/ui.cc:588]: (error) Return value of allocation function 'make_filemenu_button' is not stored. Now, the call is: make_filemenu_button(); to: Fl_Widget *UI::make_filemenu_button() which returns (btn) so is that correct? Where does (btn) go in the calling function - or what does it do? Nick (trying to learn). -- 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 9, 2016

cppcheck on Dillo source

by nick＠linicks.net

Hi all, While waiting for the Tour De France to start on TV, I ran cppcheck on Dillo source for something to do - a few errors were picked up! I have compacted the findings (with two comments from me)and attached it as a plain text file. Keep up the great work guys and 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 9, 2016

URL field / Loading page images / Refreshing DNS cache

by Johannes.Hofmann＠gmx.de

On Fri, Jul 08, 2016 at 01:23:55PM -0400, Jorge Arellano Cid wrote: > On Fri, Jul 08, 2016 at 05:22:48PM +0200, Johannes Hofmann wrote: > > On Wed, Jul 06, 2016 at 10:28:04AM +0200, Johannes Hofmann wrote: > > > On Tue, Jul 05, 2016 at 04:53:45PM -0400, John Gaffney wrote: > > > > First, a huge thanks to all the Dillo team for their efforts: I just > > > > switched from 3.0.5 to the current snapshot to try out the mbedtls > > > > changes, and I am wowed not only by this, but by all the improvements > > > > in rendering, etc. Great work! > > > > > > > > A few suggestions, all very minor, that might be added to the back of > > > > the development queue: > > > > > > > > In the current snapshot, the navigation bar has changed, and the URL > > > > field does not seem to be taking into account font_factor -- with the > > > > result that the window is smaller than the font height. You can test > > > > this by setting, e.g., font_factor=2.0 in your dillorc (most > > > > dramatically for a tiny panel with small icons). The issue seems to > > > > be with this factor not being taken into account when bh and lh are > > > > set in make_panel() in ui.cc. > > > > > > > > As far as I can see, one can use the context menu to download > > > > individual images on a page, or use the panel to toggle image > > > > loading. But if one wants not to download images in general, but to > > > > download all the images for some one page (e.g., a weather forecast > > > > page), then one has to toggle downloading of images on and then off > > > > again. Maybe a command could be added to KeysCommand_t in keys.hh, > > > > bound by default to something like Ctrl-i in keys.cc, with a > > > > corresponding call to a_Html_load_images() in handle() in ui.cc? > > > > > > > > To make the switch to the current snapshot, I had, sadly, to terminate > > > > an instance of 3.0.5 that had been running continuously for 90 days > > > > without any issues. But to get that much up time it was necessary to > > > > add a little code so that SIGUSR1 would call a_Dns_freeall() and > > > > a_Dns_init(), otherwise (unless I am missing something) Dillo will > > > > persist in using the cached lookup indefinitely and not detect when > > > > the IP address has changed. So maybe some sort of key binding could > > > > be added that would flush the cache when needed? > > > > > > good point. However I'd like to avoid another key-binding and rather > > > do the right thing automatically. > > > I could think of a general DNS entry timeout of a couple of seconds. > > > In many cases DNS responses are cached at OS-level too respecting > > > lifetime values given by the server. > > > > Firefox has an option to configure the DNS cache expiration > > (network.dnsCacheExpiration). > > Attached patch implements a similar feature for Dillo. > > Thanks for the patch Johannes. > > Under the current workload, I guess I'll look at it in a couple of days. > > BTW, different use cases are very interesting. We usually asume our > use case is generic. Dillo has thaught me several times that's not the > case. true > > I for instance, really avoid flushing the DNS cache as it is one of > the slowest parts of my web browsing experience. Sometimes the ISP DNS > server takes more time to answer than the page to load! > > I use another DNS but it's very noticeable, and the sites I usually browse > seldom change their IPs (I've even thought of caching to disk, go figure! ;) > > So I'd like to know what's the use case behind this need. There's surely > something on it (e.g. some site may want to distribute workload between > different servers by changing IP, etc). Searching for "getaddrinfo ttl" gives some interesting information about the topic. The general opinion seems to be that DNS caching should be handled by e.g. nscd(8) as the TTL value is available there and responses can be cached over process restarts of individual apps. That also seems to be the reason why getaddrinfo() doesn't give access to the TTL value (to avoid that all sorts of applications implement their own DNS caching scheme). Nevertheless I think that for the special case of web browsers some DNS caching is helpful. And e.g. Firefox does that too. Having a configuration option for the DNS cache expiration time one can have everything from no caching at all to caching forever. > > One thing I know DNS queries are abused for is for tracking users. > On the old dialup days, the DNS was very quick to answer, so I suspect > something fishy going on when it takes so much time here on broadband... > Cheers, Johannes

July 9, 2016

patches #4634 and #4635

by jcid＠dillo.org

Hi corvid, Some comments: ----------------- Patch #4635: rm IO flags, as they are never used Yes, those linger from a time when shutdown() was used for handling sockets in dillo. Not necessary now since we use read() write() close(). ------------------ Patch #4634: freeing http socket, close FD that's being connected Why did you do this? (i.e. Is there a specific bug?). Beware the FD is closed inside IO.c (OpEnd|OpAbort). If you close it in Http_socket_free(), you are opening race conditions on file descriptors, and coding outside the design. Http_socket_free() is used with the CCC chains, that's why it doesn't close the FD, IO will do it by means of CCC; avoiding race conditions. I haven't tested the code yet, but I'd be amazed if resources don't stop to load at random. For instance, Http_socket_reuse(int Skey) would be activating and reporting success on a socket that's just been closed. Please review all the related patches and be more careful before committing. PD: IIRC I used lsof to check for FD leaks long ago. -- Cheers Jorge.-

July 9, 2016

an experiment using mbed TLS

by eocene＠gmx.com

Martin wrote: > Dillo builds just fine on mucosa, especially after I `brew install mbedtls` > > Problem is that, at start up, it reports > Trusting 0 TLS certificates. > > Any idea how I can install some? It's odd browsing about without https > these days. Did it work with 3.0.5 or the development branch before the recent change? (Wouldn't expect it to.) Johannes reported success on osx, but I don't know what's customary for getting certificates there... I presume https is "working" but forces you to click on dialogs...?

July 8, 2016

an experiment using mbed TLS

by matlads＠gmail.com

Hi dillo-dev, Dillo builds just fine on mucosa, especially after I `brew install mbedtls` Problem is that, at start up, it reports Trusting 0 TLS certificates. Any idea how I can install some? It's odd browsing about without https these days. Cheers, On 4 Jul 2016 20:22, "Nick Warne" <nick at linicks.net> wrote: > On Mon, 4 Jul 2016 17:01:39 +0000 > eocene <eocene at gmx.com> wrote: > > > Nick wrote: > > > > > 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. > > Ummm. You are right. Maybe I was messing around late last night with > the earlier error message - I can't remember now :) > > Sorry for the noise - all builds and works fine. > > 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" > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev at dillo.org > http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev >

July 8, 2016

URL field / Loading page images / Refreshing DNS cache

by jgaffney＠lawrenceville.org

Jorge Arellano Cid <jcid at dillo.org> writes: [...] >> As far as I can see, one can use the context menu to download >> individual images on a page, or use the panel to toggle image >> loading. But if one wants not to download images in general, but to >> download all the images for some one page (e.g., a weather forecast >> page), then one has to toggle downloading of images on and then off >> again. Maybe a command could be added to KeysCommand_t in keys.hh, >> bound by default to something like Ctrl-i in keys.cc, with a >> corresponding call to a_Html_load_images() in handle() in ui.cc? > > This is interesting. > >> To make the switch to the current snapshot, I had, sadly, to terminate >> an instance of 3.0.5 that had been running continuously for 90 days >> without any issues. > > Wow, it's good to know it can last that long. > > What you describe here is very interesting, in a way I've > come to suspect most users don't have the slightest clue. > > I mean, everyone of us (as dillo users) have *different* use cases. > There's no way we can guess what other people are doing outside of > our awareness realm. > > Now, you're not only a casual user, but one that uses dillo *a lot*, > and appreciate it as an everyday tool. > > That being stated, we are very interested in knowing your use case, > and all the details of it. There's potentially a lot we can learn from it, > and also improve yours/and-the-generic user experience as a result of > this learning. > > So please elaborate on why you like to have it running for that long time, > what do you do with it, how you do it, what problem does it solve that other > tools don't, why is it your choice. What you'd wish it had. I had been using Firefox (and still do, for trusted sites that require javascript), but looked around for another browser when the option to turn off javascript was removed from the preferences dialog -- when javascript is so often the vulnerability behind exploits, I didn't want a browser hoisting in javascript from all over the Internet at its own discretion. (It is still possible to turn javascript off in Firefox if one starts from a script that invokes a prefs.js with a legacy `user_pref("javascript.enabled", false);', or from the internal about:config page, but:) Dillo was one of the few browsers without javascript, and when I checked it out, I found that I agreed very much with Dillo's stated philosophy. And it has been my principal browser ever since. In fact, along with an xterm and Emacs, it's one of the three apps always running on my machine. Things I like about Dillo: Dillo doesn't even include javascript. (I cringe a bit when there is talk on the list about the possibility of including it -- if it is included at some point, I hope that there will be a #define to exclude that code at compile time.) Dillo is small and fast, which is nice not only for general browsing, but when invoking it through, e.g., Emacs to open a link. Dillo let's me configure things the way I like, and when it doesn't do something I want, the code base is accessible enough that I can modify it to do so. (I had in fact already implemented the suggestions I made, but didn't share any patches because, even beyond being an amateur, my hacks tend to be on the ugly side -- the loading of images per page, for example, required adding #include "html.hh" to ui.cc, indicating that I am certainly violating some logic of organization and encapsulation.) Dillo isn't phoning home or doing anything else behind my back, and it let's me easily block ad and other such sites in domainrc. Dillo doesn't try to do all sorts of exotic things, or invoke external apps to do them, with all of the potential security risks. With other browsers, you have to do a lot of work to try to prevent this sort of automagical behavior, and even if it's possible, you aren't left feeling at all confident about having prevented it. Like you, I like that Dillo caches DNS lookups, but of course IP addresses change from time to time for legitimate reasons, so there does need to be a way to flush the cache. Johannes's patch is a good one, but I also still like the idea of using the cache until I need it to refresh. Of course, one could simply start a new instance of Dillo, but I also like that it caches pages in a way that allows me to open a link to a previously visited page off-line, without trying to reconnect and reload it. And -- possibly a unique personal idiosyncrasy -- I like to see links I have visited displayed as visited. Other than that, there really isn't any reason not to be firing up a fresh instance of Dillo whenever it is needed. And probably a lot of other virtues in Dillo that just aren't coming to mind right now. > Some things may be possible, others not, a few may be solved in different > ways, etc. Just learning about those key tasks, or improving a single one, > would be a big gain for all of us. > > Your feedback as a dillo power-user is not only welcomed, it's asked for! > > >> Thanks again for all your hard work! > > Ack! > > > @all: if you're a dillo power-user, let us know about it!

July 8, 2016