- Dillo-dev - lists.mailman3.com

Starting dpis on FreeBSD: blackhole(4) timeouts

by corvid＠lavabit.com

Jorge wrote: > With regard to UDS, it can be scheduled into the repo shortly > after the release; Thereafter users can help us polish it from > there. Do you expect that you will have time to do it yourself? Would it make sense to make a 2.2.1 with just the uds dpi changes and nothing else that isn't rather trivial?

Feb. 7, 2010

valgrind [Re: [Dillo-dev] dillo-2.2-rc1]

by jcid＠dillo.org

Hi Jeremy, On Thu, Feb 04, 2010 at 06:32:29PM +0000, Jeremy Henty wrote: > On Wed, Feb 03, 2010 at 08:07:13AM +0000, corvid wrote: > > Jeremy wrote: > > > > > > Thanks. Everyone is welcome to suggest improvements. > > > > I've been wondering whether it is possible to check dpid and the > > dpis as well. Apparently there's a --trace-children=yes option, but > > it's probably not that simple :) > > I'll look into it. It may not be so complicated - valgrind logs the > PID so it should be easy to group the log entries by process. The > tricky thing is identifying the process - currently I just slurp the > whole output before doing anything, by which time the dpi might have > died. It might be better to process it line-by-line so I can check > the process table right away. That would need a little > re-engineering. Or maybe it would be better to replace the dpis with > wrappers that run valgrind? I'd definitely try with wrappers! -- Cheers Jorge.-

Feb. 7, 2010

Starting dpis on FreeBSD: blackhole(4) timeouts

by jcid＠dillo.org

On Tue, Feb 02, 2010 at 09:13:14PM +0100, Johannes Hofmann wrote: > On Sun, Jan 31, 2010 at 04:44:57PM -0300, Jorge Arellano Cid wrote: > > On Sun, Jan 31, 2010 at 07:02:54PM +0000, corvid wrote: > > > bf wrote: > > > > Because blackhole(4) is a common security measure, and because this > > > > problem did not exist under the previous dpi framework, it must be > > > > considered a regression, even if, in hindsight, it is to be "expected". > > > > > > I finally looked back to refresh my memory on why we switched to inet > > > sockets: Minix. If we do return to Unix sockets eventually, what is the > > > thinking on what we would do for Minix? > > > > At some point in time Minix 3 will have to implement UDS. > > In the meanwhile they can use the version with inet sockets. > > What shall we do about this TCP blackhole issue? > Should we try to switch back to UDS before release? Sorry for the delayed answer Johannes (I was out of the city). IMO, UDS before the release is too risky. It will need lots of testing time. I believe we may choose the solution bf has found to work better as workaround, make a patch with it and release. A few times in the past I rushed a "better" solution into an rc, only to learn not to do it! :) With regard to UDS, it can be scheduled into the repo shortly after the release; Thereafter users can help us polish it from there. -- Cheers Jorge.-

Feb. 7, 2010

How to use the tab or other keyboard keys to set foucs on web page links?

by corvid＠lavabit.com

Yong wrote: > I am using the Dillo on an embedded device for web browsing. Since > this device does not support mouse or touchscreen, > I have to use the keyboard(or some buttons). I found I cannot set the > focus on these links using tab keys( Dillo 2.2-rc1). > > If there any key configuration settings to set the tab key? Not currently. > If not, I want to modify the source code to add this function, Great! > is there any example or related patches for reference? I think the way to make this work would be something like: - borrowing from the dw/findtext.cc iteration code. - checking when style->x_link != -1 or you're currently on an embedded form widget.

Feb. 7, 2010

How to use the tab or other keyboard keys to set foucs on web page links?

by sdliyong＠gmail.com

Hello All, I am using the Dillo on an embedded device for web browsing. Since this device does not support mouse or touchscreen, I have to use the keyboard(or some buttons). I found I cannot set the focus on these links using tab keys( Dillo 2.2-rc1). If there any key configuration settings to set the tab key? If not, I want to modify the source code to add this function, is there any example or related patches for reference? Thanks a lot! Yong

Feb. 7, 2010

dillo-2.2-rc1

by Johannes.Hofmann＠gmx.de

Hello, On Tue, Feb 02, 2010 at 01:11:38PM +0100, Johannes Hofmann wrote: > On Sun, Jan 31, 2010 at 02:34:37AM +0000, corvid wrote: > > As you may have already noticed, we're at RC1 for the next release. > > Johannes has built a tarball: > > > > http://www.dillo.org/download/dillo-2.2-rc1.tar.bz2 > > SHA1: 146216a1541b20a3e042c62c0db8ee42f173ed01 > > > > Please test! > > Ok, for now we know about the TCP blackhole issue reported by bf. I think we need a decision about this soon. I made a short attempt to switch DPIs back to UDS, but couldn't get it working yet. If I find some more time this weekend I will try again. I would propose that we decide on Monday, whether we release our current rc1 as it is and document the issue or go with a possible UDS solution. In both cases I want the release to happen next week. Cheers, Johannes

Feb. 6, 2010

Editable User-Agent

by corvid＠lavabit.com

Alexander wrote: > I would like to make a small proposal for another useful option in > dillorc: A customizable User-Agent string. > > I think this might be useful for some users that want to mime another > browser in order to avoid vulnerabilities due to zero day security > problems or that want to test their website with several browsers and > User-Agent strings. I think I'm currently in favor of a configurable User-Agent header for privacy. - It might be good for dillo to start sending an Accept header. I send one because I use a Firefox user agent string, and sometimes servers don't send content if one isn't doing a good enough job of pretending to be Firefox. (I've never seen the Accept header convince a server that I dont want application/xhtml+xml or multipart/mixed, though, unfortunately). - Possibly we could print a MSG when we see User-Agent in the Vary header (it tells us when a response was in some way determined by that header). I would probably like that, but perhaps others would find it irritating.

Feb. 5, 2010

Editable User-Agent

by Hole.destructor＠gmx.de

Dear Dillo Developers, I would like to make a small proposal for another useful option in dillorc: A customizable User-Agent string. I think this might be useful for some users that want to mime another browser in order to avoid vulnerabilities due to zero day security problems or that want to test their website with several browsers and User-Agent strings. Enclosed please find a small patch that adds a new option to dillorc which defines the User-Agent string via http_user_agent="Mozilla/5.0" Kind regards, Alexander Voigt

Feb. 4, 2010

valgrind [Re: [Dillo-dev] dillo-2.2-rc1]

by onepoint＠starurchin.org

On Wed, Feb 03, 2010 at 08:07:13AM +0000, corvid wrote: > Jeremy wrote: > > > > Thanks. Everyone is welcome to suggest improvements. > > I've been wondering whether it is possible to check dpid and the > dpis as well. Apparently there's a --trace-children=yes option, but > it's probably not that simple :) I'll look into it. It may not be so complicated - valgrind logs the PID so it should be easy to group the log entries by process. The tricky thing is identifying the process - currently I just slurp the whole output before doing anything, by which time the dpi might have died. It might be better to process it line-by-line so I can check the process table right away. That would need a little re-engineering. Or maybe it would be better to replace the dpis with wrappers that run valgrind? Hmm, dillo is somewhat unusual in that it forks children that are intended to keep running after the parent dies. I don't know whether valgrind will handle that usefully. This needs some research. Meanwhile, you've got to love this extract from "man valgrind" regarding the "--child-silent-after-fork" option: This can make the output less confusing (although more misleading) Meaningful and correct: pick one! :-) Regards, Jeremy Henty

Feb. 4, 2010

Starting dpis on FreeBSD: blackhole(4) timeouts

by bf2006a＠yahoo.com

--- On Sun, 1/31/10, Jorge Arellano Cid <jcid(a)dillo.org> wrote: ... > > > > > > Simple solution: try something like this > script to > > > start dillo: > > > > > > #!/bin/sh > > > ST="`ps -ef|grep "[0-9] dpid"|wc -l`" Since ps(1) on *BSD differs from POSIX, I used instead: ps -ax -ocomm | grep -ce "dpid" > > > if [ "$ST" = "1" ]; then > > > echo "Dpid is running OK!" > > > dillo > > > else > > > echo "Dpid is NOT running" > > > dpid & > > > dillo > > > fi > > ... > You can increase dpid's time to live: > > dpid/main.c:208 > - int dpid_idle_timeout = 60 * 60; /* > default, in seconds */ > + int dpid_idle_timeout = 60 * 60 * 24; /* > default, in seconds */ > > > Or simply let it linger forever: > > dpid/main.c:207 > - int i, n = 0, open_max; > + int i, n = 0, linger = 1, open_max; > dpid/main.c:295 > - if > (server_is_running("downloads")) > + if (linger || > server_is_running("downloads")) > > > Please test both and send your feedback. Once > we have a usable > workaround, we may think of a good patch (e.g. a dillorc > option). I have used tested both methods, and both seem to prevent the timeouts (or at least the great majority of them, in the case of the patch that just increases the ttl), when used with something like the script above. Such a script is not quite as convenient as simply starting dillo, but probably offers an adequate workaround for the initial part of this problem, for the moment. > Last but not the least, IMHO, > using verbs like "plagued" and > expressions like "or sit on my hands" doesn't help in > dillo-dev. Perhaps something is lost in translation, or we're just proving that what one person considers colorful or descriptive is considered to be too strongly worded by another. In any event, my language was not meant to be an attack upon anyone, and no one should construe it as such. On the whole, the new version looks good. Congratulations and thanks to those who put time and energy into improving dillo since the last release. b.

Feb. 4, 2010