- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]About proxy authorization && password storing

by Ivan Daniluk

Hi! You wrote at Tue 06 Apr 2004 17:06: > 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! Yes, this simplify all that mess =) I've done as you suggested. > 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. Ok! Great. I'll contact him. > > > 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. Ok, I just commented it out. Here attached pre2 :) patch. What about hiding symbols, when entering password? (i.e, replacing visible characters by asterisk symbol). Maybe we just have to add additional parameter in a_Interface_make_dialog(..), like "gboolean entry_hidden" or smth? Or implement a new dialog_window type specially for login/password asking? It will be useful for basic authentication stuff. Regards! -- Ivan Daniluk, software developer, Ukrainian Computer Labs, Kiev, Ukraine mailto:Ivan.Daniluk@ucl.com.ua

April 8, 2004

[Dillo-dev]Theme for Dillo 0.8.0

by Gregg

Hi all, I made a button theme for 0.8.0 - Cobalt. Enjoy! -- Gregg

April 8, 2004

Re: [Dillo-dev]GTK 1.2 and Dillo's future

by Philip Blundell

On Wed, 2004-04-07 at 14:46, John wrote: > But I have to ask, why not just keep using GTK 1.2? GTK 1.2 is mature, and lite. Perhaps it will start an effort to keep GTK 1.x alive? As far as I'm concerned, the disadvantages of sticking with 1.2 are: - lack of support for client-side antialiased fonts, multiple displays, internationalisation, and other modern toolkit features - abandoned upstream; nobody is even fixing bugs in 1.2 at this point. - used by increasingly few other programs, which creates a headache for system integrators. For example, every other program in the distributions that I work with is using GTK 2 now. I would love to be able to ship a recent Dillo, but this would mean installing libgtk1.2 and libglib1.2 (plus probably a pile of server-side fonts for it to use) and I can't spare that amount of flash. p.

April 8, 2004

[Dillo-dev]A button theme for Dillo 0.8.0

by Geek

While I was stuck with no internet, I made a theme for Dillo I call "cobalt". Enjoy! -- Gregg t3h g33k http://geek.scorpiorising.ca

April 8, 2004

[Dillo-dev]GTK 1.2 and Dillo's future

by John

As a major fan of lite-weight apps I am very unhappy that so many of my favorite applications are being ported to GTK2. I've been following the Dillo Dev list and I know that there is an effort to port Dillo over to FLTK which may be a good alternative to GTK2. But I have to ask, why not just keep using GTK 1.2? GTK 1.2 is mature, and lite. Perhaps it will start an effort to keep GTK 1.x alive? John

April 7, 2004

Re: [Dillo-dev]why use "ccc chain" instead of calling the function directly?

by Jorge Arellano Cid

On Wed, 7 Apr 2004, [gb2312] Lei Jin wrote: > Thank you for your detail explanation. ACK. First of all, there's no need to CC me, I read dillo-dev! > I am still confused. Would you provide an example such as the > situation of the two threads doing network job(what happens > when using threads and mutexes and when using CCC chain)? Maybe > it will help to understand. When using threads and mutexes (pthreads), thread scheduling is done by a third thread or by the kernel (depends upon the implementation), and it is preemptive. Now, the address space may be shared, so the need for mutexes arise, and because of both reasons, performance is degraded. Using a pseudo-thread (CCC thread), doesn't require scheduling by an external process or by the kernel. All is done in the same process, but there's no preemption. (If you ever have heard that unthreaded servers are faster than threaded counterparts, you'll find the same reasons behind.) Now, since CCC-threads are not preemtive, Dillo also makes use of pthreads when it needs this ability (for instance for DNS resolving). As all the CCC-threads run in the same process, it's easy to sync with pthreads with a polling wait and an event. Cheers Jorge.-

April 7, 2004

[Dillo-dev]Re: New dillo user (contributor?)

by January Weiner

> least a rudimentary man page should be in each programs distribution. Is > there any document available on Dillos shortcuts and configuration, or > should I download the sources right away? Ok, ok, my fault, I got it. j. -- ------------ January Weiner 3 ---------------------+--------------- Division of Bioinformatics, University of Muenster | Schlo�platz 4 (+49)(251)21634 | D48149 M�nster http://www.uni-muenster.de/Biologie.Botanik/ebb/ | Germany

April 7, 2004

[Dillo-dev]New dillo user (contributor?)

by January Weiner

Hello, first of all, let me thank you for this great piece of software. It's fast, it's simple, it keeps up good Unix traditions -- small, efficient programs which do one job. I have used dillo a couple of years ago, but it was a little too brittle and not mature enough for me, especially due to the lack of tables (or was it CSS?) -- anyway, it is very nice now[*]. A thing that's really lacking (at least for me) -- is a.. man page. I'm an unbelievably traditional when it comes to man pages, mostly because of the apropos database[#]. Further, an introductory readme page for users (with shortcuts etc., and not necessarily compilator options) would also be a nice thing to have, I think. How about that -- if you do not have anything principally against man pages / readme's for newbie's, I'll write it, and promise to keep up with Dillo's releases for the next 12 months. I do not have much time, but at least a rudimentary man page should be in each programs distribution. Is there any document available on Dillos shortcuts and configuration, or should I download the sources right away? Regards, January P.S. A nice detail: when running dillo for the first time, make it copy the dillorc into ~/.dillo/. This is the first place a literate Unix user will look for a configuration when he or she notices that Dillo created ~/.dillo/. Tested on three individuals :-) [*] the only thing I really miss is the support for ISO-8859-2. [#] besides, it took me a couple of minutes to figure out that "s <keyword>" is not a thing you should type in the address widget, but an abbreviation for "ctrl-s keyword", esp. because ctrl-s is such a widespread shortcut for "save". -- ------------ Dr January Weiner 3 ------------------+--------------- Division of Bioinformatics, University of Muenster | Schlo�platz 4 (+49)(251)21634 | D48149 M�nster http://www.uni-muenster.de/Biologie.Botanik/ebb/ | Germany

April 7, 2004

Re: [Dillo-dev]Disable toolbars

by Jorge Arellano Cid

On Sun, 4 Apr 2004, Florian Angehrn wrote: > if i don't want both toolbars, what do i have to change in the sourcecode? > > many thanks for your great product (and an answer :)! Hmmm, you should be able to find this by yourself, but... Go to Interface_browser_window_customize() and set Interface_toggle_panel() to do what you want. Cheers Jorge.-

April 7, 2004

Re: [Dillo-dev]Can't start dpid

by Jorge Arellano Cid

On Sat, 3 Apr 2004, Barry Kauler wrote: > Hi, I'm not on the list, so hope this can be submitted! > Kindly also reply a copy to bk(a)goosee.com > > I have been following Dillo for sometime, as a user, and recently > upgraded to v0.8.0. > > Problem is, when I click on a ftp url, the message: > > "Error: can't start dpid daemon" > > So, I tried to start dpid directly on the commandline: > > # dpid > # dpid.c:352: register_all: fatal error: > -can't find the directory for dpis > > So, is there something missing here? -- what is dpis? > Appreciate any advice on this! <q> ------------ Dpi programs ------------ These are installed by "make install". If you don't have root access, copy "dillo" and "dpid" to some directory in your path and install the dpis by running "./install-dpi-local" from the top directory (they will be installed under ~/.dillo). </q> (Extracted from the README file! ;-) Cheers Jorge.- PS: Now that you've tried manually, it'd be wise to assert there's no running dpid process when you retry: ps aux | grep dpi [kill dpid processes if present]

April 7, 2004