- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]About proxy authorization && password storing
by Jorge Arellano Cid April 23, 2004

April 23, 2004

On Fri, 23 Apr 2004, Ivan Daniluk wrote: > > [...] > > - renamed a_Http_use_proxy_passwd() to a_Http_set_proxy_passwd(). > > - Made the password not visible when typed. > > - Added a commented entry for "http_proxyuser" in dillorc. > > > > This patch is now in CVS, but is not tested because I don't > > have a proxy at hand! :-) > I've tested - it seems to be ok. Good. > And one correction from Francis Daly: > ------------------------------------------- > > From: "Francis Daly" <francis(a)daoine.org> > > To: "Ivan Daniluk" <Ivan.Daniluk(a)ucl.com.ua> > > > > On Thu, Apr 08, 2004 at 06:49:45PM +0300, Ivan Daniluk wrote: > > Hi there, > > One small thing: > > > + static const char *base64_hex = "ABCDEFGHIJKLMNOPQRSTUVWXYZ" > > > + "abcdefghijklmnopqrstuvwxyz" > > > + "0123456789._"; > > > > RFC 2068 (HTTP/1.1) defers to RFC 2045 (MIME), which uses "+/" as the > > final two elements, instead of "._". > > > > RFC 1945 (HTTP/1.0) defers to RFC 1521 (MIME, obsoleted by 2045) which > > uses the same. Done! > PS. I've sent a letter to Madis, but have got no reply yet. Yes, he's under too much work now (we were working on the SSL plugin and he had to stop because of his duties). Please allow him some time. BTW, we have a new SSL dpi prototype (not for the next release though). More on this later. I'll send a recapitualtion about the FLTK port first... Cheers Jorge.-

1 0

Re: [Dillo-dev]Can't start dpid
by Barry Kauler April 22, 2004

April 22, 2004

Ok, I've joined the dillo-dev list! On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > I should also explain that I have my own distro, Puppy Linux, > > and everything is compiled against uClibc, not glibc. > > (www.goosee.com/puppy) > > Oh, it would be interesting to have Dillo running under uClibc! Dillo has been in Puppy right from the start (which was about one year ago). A few months ago I changed over to uClibc and recompiled everything, including Dillo, and all was well until I upgraded to Dillo v0.8.0. > Check if you can run them crom the CLI: > > cd /usr/local/lib/dillo/dpi/hello > ./hello.filter.dpi I'm doing this as root. When I try this I get: hello.dpi:: starting... and that's it, nothing more, doesn't exit until I ctrl-c. No error message. ...what is it supposed to do? Regards, Barry Kauler

4 11

[Dillo-dev]Re: [Fink-devel] [Dillo] FONTS
by Joe Corneli April 22, 2004

April 22, 2004

Thanks. I'm somewhat amazed that the Dillo people didn't catch that. >> My ~/.dillo/.dillorc Note that the file should be named ~/.dillo/dillorc (leave the second dot). I do think it would be nice to support a .dillorc too, for people who, like me, automatically type the `.'.

2 1

Re: [Dillo-dev]About proxy authorization && password storing
by Jorge Arellano Cid April 21, 2004

April 21, 2004

On Fri, 2 Apr 2004, Ivan Daniluk wrote: > Hi Jorge. Hi! > > > Maybe, we should open popup dialogue and ask user for > > > login/password? > > > > The login may be specified in dillorc, and the password asked > > in a popup dialog (whenever there's a login in dillorc :). > > > > This adds the burden of entering the password, but keeps things > > a bit more private. > I've implement this burden :), but stuck in a problem and need advice > and/or suggestion from you. > First, look to the attached current patch for stable dillo 0.8.0 > release. Oh, I haven't yet. Anyway, here's the answer. > Main problem for me is the way to stopping the query, waiting > until password will be entered or canceled, and resuming it. > When we call a_Interface_proxy_passwd_dialog(), the dialog window pops > up, and query goes forward, without being formed with proxy password. > So, I see two ways: > 1) to stop the query forming(in Http_get() function) and wait, while > proxy_passwd_dialog_window will be destroyed. > 2) to abort the query, and recall it when password will be entered. > > I'm a newbie in gtk programming, and can't figure out how to graceful > open dialog window and wait until it'll be closed. If it's possible, > than imho it's the best way. > About second choice.. There are complexity for me in a_Http_ccc stuff. > Sure, I'll win this problem, but it will take more time. And really > want to hear your thoughts about it. Use the third alternative! :-) AFAIS the simplest way to to it is to ask for the proxy password when dillo starts, that is, before any query is made, probably after the splash screen is displayed. That way, things would reach the same simplicity as in the first patch! > One more question around it. > Password dialog window is activating in case if there is option > "http_proxyuser" in config, but not when http query gets "Cache Access > Denied" error. > Is this way ok? AFAIU, yes. The proxy login/password pair is one thing, and HTTP's simple authentication mechanism (section 11) is another. It may happen that you reach a realm/password protected page through a login/password authenticated proxy. Now, if after this patch, you want to keep on working on basic authentication, be sure to contact Madis (AFAIR he once worked on it), and I can make the CCC bindings to stop/resume/forward the querying process. > And, the last note on patch. It's about following lines in IO/http.c: > + if ( strchr(prefs.http_proxyuser, ':') ) > + { > + DEBUG_MSG(5, "Storing proxy password in dillorc is insecure!\n"); > + ask_proxy_passwd = FALSE; > + HTTP_Proxy_Auth_base64 = a_Misc_encode_base64(prefs.http_proxyuser); > + } > It allows user to store in config file not only proxy user name, but > pair "user:password" as well. I've done it's mainly for convenience, > but of cource we can remove it from patch. Hmmm, this is one I'm not yet sure of. On one hand, it is very handy not to have to enter the password every time, and on the other, stealing the proxy's password becomes quite simple (for instance, a bathroom break and it's gone! ;). [minutes thinking...] It's not a thing I'd recommend. Now, as Dillo project is explicitly concerned about security, it can't do otherwise. Perhaps you may leave that portion of code commented out, so the responsibility is left to the one that decides to enable it. I'd like to hear comments about this. Specially from sysadmins. > Your suggestion for me are welcome. Thanks. Cheers Jorge.-

2 2

[Dillo-dev]fonts
by Joe Corneli April 20, 2004

April 20, 2004

My ~/.dillo/.dillorc contains # Fontname for variable width rendering (most of the text). # - some fonts may slow down rendering, some others not! # - try to tune a fontname/font_factor combination. # Ex. {helvetica, lucida, times, "new century schoolbook", utopia, ...} vw_fontname=utopia # Fontname for fixed width rendering (mainly <pre> quoted text) fw_fontname=courier # All fontsizes are scaled by this value (default is 1.0) font_factor=3.0 The font that is actually used appears to be the same as the default. Can you please suggest how to debug this or how to actually change the font? I'm running OS X, using Dillo 0.8.0 from Fink. Joe

2 1

[Dillo-dev]Who posted BUG#544?
by Jorge Arellano Cid April 20, 2004

April 20, 2004

Hi, I wonder who posted this report: BUG# 544 Impact: feature fault At : run time Type : other Comments: I love the html bug detector but I can't copy the data from it! This greatly reduces it's strength... my students are using dillo almost everyday now in a web dev class.. HTReproduce: get a buggy html site/ click on ck html / try to copy the errors WorkedBy: nobody Obviously doing Copy&Paste from the error window solves the problem. It's be very interesting for us to know where and how is dillo used in a web dev class. Cheers Jorge.-

1 0

[Dillo-dev]BAD HTML and Good Webmasters
by Jorge Arellano Cid April 20, 2004

April 20, 2004

Hi there, These days have brought several good surprises with regard to HTML and good webmasters. For instace, from the sites that appear in our splash screen: The Register: switched to XML! (no BUGS) Slashdot : they're fixing the HTML (some old detected bugs don't show anymore) Monster news: In the process of fixing. Dillo's site: Fixed! (Yes, the new parser catched hidden bugs) also, sourceforge.net and newsforge.com look better with the new parser (not a merit of the sites, but a good new anyway). To finish this report, and with a view to exemplify what you should expect from a good webmaster, I'd like to forward a couple of emails I had with the webmaster of www.fluxagent.org: ---------- Forwarded message ---------- Date: Thu, 15 Apr 2004 21:50:12 +0200 From: Markus Kroetzsch <Markus.Kroetzsch(a)inf.tu-dresden.de> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Re: www.fluxagent.org and Dillo Dear Jorge, thank you for your answer. Setting the area > tag fixes the problem, even on my old Dillo 0.7.2. The webpages will be updated shortly to reflect this insight. When viewing the uncorrected page sources with Mozilla, the missing ">" actually shows up automagically, which might be the reason why nobody noticed so far (the pages are auto-generated by a script, so there is just one place where ">" is missing...). Best regards Markus > Hi, > > Sometime ago someone filled the following bug record with > regard to www.fluxagent.org: > > BUG#478 > Impact : soft error > At : run time > Type : misbehaviour > Comments: Images used for navigation within a table (each equiped > with some polygon-area mouse-<map>) do not always (but sometimes) > actually work as links. Maybe related to bug 317? > - PS: Great project! - > HTReproduce: Go to www.fluxagent.org (valid html4.01). Check the > navbar: only the first link works, no matter which sub-page is > viewed. > WorkedBy : nobody > > I tried to get the webmaster's email address from: > > http://www.fluxagent.org/emails.htm > > but it didn't show for Matthias Fichtner, so I write to you. > > > The problem is that for some reason I don't yet know of, SGML > allows for omitting the '>' closing tag character for the <area> > element. > > If you check the page with W3C, it validates, but if you do > with the WDG validator, then it shows: > > http://www.htmlhelp.org/cgi-bin/validate.cgi? > url=http%3A%2F%2Fwww.fluxagent.org&warnings=yes > > The easiest solution is to add the missing '>' for each <area> tag. > > > Hope this helps > Jorge.- > http://www.dillo.org ------- End of Forwarded message -------- Cheers Jorge.-

1 0

[Dillo-dev]Bookmarks, Tabs
by Tom Barnes-Lawrence April 18, 2004

April 18, 2004

Hi all, I've got 2 questions to ask: 1)- I was on the list back in January, and amongst other things, I mentioned that I'd consider it a huge improvement if the bookmarks DPI were made to allow for a nested hierarchy of sections. Jorge and Thorben pointed out that it wasn't a priority at the time, and that I should write it myself if I wanted it. Unfortunately, I too had things to be doing back then, but about a month ago, I set about doing some work on such a thing. -It is written in Perl, rather than C; it seemed a good choice due to all the text manipulation, etc. This might be considered a problem if Dillo is being used on platforms where Perl isn't (readily) available, but AFAICT the Windows version of Dillo is a purely 3rd party thing that isn't directly supported by the project, and Perl for Windows does *exist*... I don't know if there'd be any other issues with this decision though. -I moved much of the Dillo-DPI specific stuff into a separate file, hoping to make it a Perl Module, but I know nothing about how that works (and I can't get the Camel book ATM because I'm broke) and couldn't understand the relevant man page, so I don't think it turned out how modules are supposed to. I mention this because it could maybe end up useable by any other Perl-based DPIs that get written. -It currently uses the "ngbm" DPI name (for "Next Generation BookMarks"), and uses ngbm.txt for the bookmarks file, to avoid breaking the existing bookmarks program. That's because it's not ready yet. -It *does* implement the nested sections stuff I wanted that the current bm dpi doesn't, with a file format that's backwards compatible with the current one- so you can get it to read your existing bm.txt file. -BUT I only worked on it for about a day, and much of that was spent trying to figure out how it was supposed to communicate, so it still doesn't have much of the important functionality, such as actually adding or modifying any bookmarks or sections. Also, as I was hacking away a lot to try to get it to work at all, there's a lot of commented-out debug stuff, and much of the notes and comments are probably wrong now (I don't think I fixed them whilst I was changing the code and the design). I didn't want to go quietly working away at it for ages and then find that actually someone else was quietly working away at the same thing, for example (also the DPI handling stuff got incredibly frustrating, which put me off doing any more for a while). Unfortunately, I kept forgetting to do *anything else* about it because I had other things to think about :P SO: Would this be of any interest to the project in whatever way? I figure I could (a) post the existing code, get a bit of feedback and then do some more work on it, or (b) give the code to the project and let someone else take it over from me. (or (c) I could just keep it to myself...) 2)-Since my high-res monitor blew up in December, I installed Frank's tabs+ frames patch, and I find it helps enormously- I don't think I could manage without it now. Unfortunately, AFAICT Frank has either left the project or gone on holiday or something (though I can't find any explanation anywhere), and the latest version on his site (which I'm using) only works with an old CVS version from November, so I'm still having to put up with the bugs that have been fixed in 0.8. Gah! I saw after 0.8 was released, someone on the list said he'd try to take on the tabs/frames patch in some way, but I didn't hear anything more about it. Is there *any* news on this whatsoever? I'd really like to be able to upgrade. Thanks in advance, Tom Barnes-Lawrence -- Signature? I have no need of signatures

2 1

[Dillo-dev]HTML Policy and New parser improvements
by Jorge Arellano Cid April 16, 2004

April 16, 2004

Hi there, Most of us are familiarized with the aforism about our HTML parsing policy stated in the [Project Notes]: "Our policy with HTML is not to try to render badly written HTML, ideally send a warning message, and not to crash!" Here goes the rationale behind it. I wrote it sometime ago as an email answer, and here I quote an improved version: <q> About our parsing policy ------------------------ These days I have thought a lot about this subject. In fact an important part of the work of a project maintainer is indeed to make a stance on the difficult decisions; those that are not white or black, but a trade off. With regard to our parsing policy, imagine a triangle with the following vertices: * Standards (W3C) * Web site authors * Users Each vertex represents the exact position of its naming group. The inside area, the whole space of stances anyone could take. Each group has its own interests, sometimes opposed and sometimes very near. The position of a web browser can be visualized as a point within the area of that triangle determined by its development team. Dillo should have to be in the vertex of the W3C, but that would make it almost useless because of the horrible state of the HTML in the Web (aka. "Tag Soup"). For that reason we make some exceptions so that dillo can render a larger set of the web, by correcting some HTML faults, but we keep close to the W3C vertex. An standards compatible browser, as Mozilla, should be close to the W3C, but I understand it would never manage to be a canditate to replace IE if it did (a trade off). Actually it locates alongside the authors-users side AFAIU. As our main objective is the democratization of the access to the internet's information, and that has direct relation with the use of standards, we follow the path of respecting and promoting them. The idea of adding an HTML quality meter to the interface, in the form of a face icon and the number of detected errors, surges as a good idea to improve dillo as a QA tool for content authors. I've also thought of adding a "combat mode rendering" button. That is a way of parsing the worst sites into a basic an simple rendering. That way, users would be one click away from being able to "see" pages with awful HTML. These two ideas would help dillo to keep close to the correct vertex of the triangle, while also becoming a tool to help web authors to provide more standards compliant content. </q> After the new parser was introduced (0.8.0), Dillo featured much better HTML error detection, but it rendered malformed HTML a bit worst. It was a good trade off from the "standards" vertex of the above mentioned triangle, but I also knew that it was not going to be that much amusing for the "users" vertex. These days I've been working on improving the parser and bug-meter by introducing information about the inline, block and flow content models of HTML. After having that information in place, it was easy to produce better and more accurate bug detection and also to improve the rendering more towards what it used to be. So that's the good news: the new CVS contains code with an improved parser that hopefully will be a glad surprise for our users. From the Changelog: * Added container|inline model information to the HTML element table, and made the bug-meter and the parser aware of it. This both improves bug detection and rendering. * Fixed newly detected HTML bugs in bookmarks dpi and file.c. * Fixed opening files with a ':' character in its name (again). * Added binaryconst.h (allows for binary constants in C). * Fixed The ladder effect with lists (BUG#534). So go ahead and try it! Cheers Jorge.-

2 1

[Dillo-dev]what's the use of "EndTag" component of struct TagInfo?
by Lei Jin April 15, 2004

April 15, 2004

Its value can be "O" "F" "R", so what do they mean? AND Why use them? --------------------------------- Do You Yahoo!? 惠普TT游戏剧，玩游戏，中大奖！

2 1