April 2015 - Dillo-dev - lists.mailman3.com

Dillo CPU-hog lock on slashdot
by jcid＠dillo.org July 31, 2015

July 31, 2015

Hi there, Trying to read about this laptop on slashdot dillo locks with 100% CPU and increasing memory footprint. :-P [1] http://hardware.slashdot.org/story/15/01/20/1655242/librem-a-laptop-custom-… -- Cheers Jorge.-

2 2

SSL in the browser
by eocene＠gmx.com May 9, 2015

May 9, 2015

James wrote: > Every certificate that doesn't have something at the root of its chain, as it should. I'm on osx and there is no /etc/ssl/certs, so I had no roots until I started loading them. Where does OSX keep them? I'd looked on the web a bit in the past in case there was any simple consensus out there on the matter of where to check, but didn't find anything. I'll see where curl checks. Whatever they do is probably a good idea.

2 4

Crash with ascii text scribbled across a data structure.
by james.from.wellington＠gmail.com April 22, 2015

April 22, 2015

>From time to time, I get a most peculiar SEGV. Here's an example on fairly clean source up to c761c66 on a mac: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 0x00000001000064b7 in Fl_Widget::position (this=0x118148910, X=2003792928, Y=1869881479) at Fl_Widget.H:321 321 void position(int X,int Y) {resize(X,Y,w_,h_);} (gdb) bt #0 0x00000001000064b7 in Fl_Widget::position (this=0x118148910, X=2003792928, Y=1869881479) at Fl_Widget.H:321 #1 0x000000010008521a in dw::fltk::FltkViewport::updateCanvasWidgets (this=0x101208a10, dx=0, dy=-25) at fltkviewport.cc:502 #2 0x0000000100086492 in dw::fltk::FltkViewport::scrollTo (this=0x101208a10, x=0, y=347) at fltkviewport.cc:398 #3 0x0000000100084c10 in dw::fltk::FltkViewport::scroll (this=0x101208a10, dx=0, dy=-25) at fltkviewport.cc:413 #4 0x0000000100084c4a in dw::fltk::FltkViewport::vscrollbarChanged (this=0x101208a10) at fltkviewport.cc:156 #5 0x0000000100084c65 in dw::fltk::FltkViewport::vscrollbarCallback (vscrollbar=0x101208c90, viewportPtr=0x101208a10) at fltkviewport.cc:161 #6 0x0000000100100b13 in Fl_Widget::do_callback (this=0x101208c90, o=0x101208c90, arg=0x101208a10) at Fl_Widget.cxx:328 #7 0x000000010001a8ef in Fl_Widget::do_callback (this=0x101208c90) at Fl_Widget.H:840 #8 0x00000001001005c1 in Fl_Valuator::handle_drag (this=0x101208c90, v=347) at Fl_Valuator.cxx:95 #9 0x00000001000ec3bc in Fl_Scrollbar::handle (this=0x101208c90, event=19) at Fl_Scrollbar.cxx:142 #10 0x00000001000857d7 in dw::fltk::FltkViewport::handle (this=0x101208a10, event=19) at fltkviewport.cc:304 #11 0x00000001000ceb39 in send (o=0x101208a18, event=19) at Fl_Group.cxx:98 #12 0x00000001000cf338 in Fl_Group::handle (this=0x10053d760, event=19) at Fl_Group.cxx:254 #13 0x0000000100007aa2 in UI::handle (this=0x10053d760, event=19) at ui.cc:788 #14 0x00000001000ceb39 in send (o=0x10053d760, event=19) at Fl_Group.cxx:98 #15 0x00000001000cf338 in Fl_Group::handle (this=0x10053d6b0, event=19) at Fl_Group.cxx:254 #16 0x00000001000ceb39 in send (o=0x10053d6b0, event=19) at Fl_Group.cxx:98 #17 0x00000001000cf338 in Fl_Group::handle (this=0x10053cf60, event=19) at Fl_Group.cxx:254 #18 0x00000001000b7b94 in Fl_Window::handle (this=0x10053cf60, ev=19) at Fl.cxx:1643 #19 0x00000001000b67e0 in send (event=19, to=0x10053cf60, window=0x10053cf60) at Fl.cxx:1136 #20 0x00000001000b8ad1 in Fl::handle_ (e=19, window=0x10053cf60) at Fl.cxx:1444 #21 0x00000001000b8b7a in Fl::handle (e=19, window=0x10053cf60) at Fl.cxx:1216 #22 0x00000001000ab1b3 in cocoaMouseWheelHandler (theEvent=0x1181582b0) at Fl_cocoa.mm:943 #23 0x00000001000ab1e8 in -[FLView scrollWheel:] (self=0x101505a50, _cmd=0x7fff8965ff98, theEvent=0x1181582b0) at Fl_cocoa.mm:2250 #24 0x00007fff890580c7 in -[NSWindow sendEvent:] () #25 0x00007fff88f8cafa in -[NSApplication sendEvent:] () #26 0x00000001000aed74 in +[FLApplication sendEvent:] (self=0x1001b36d0, _cmd=0x7fff896552c0, theEvent=0x1181582b0) at Fl_cocoa.mm:1609 #27 0x00000001000ae989 in do_queued_events (time=1e+20) at Fl_cocoa.mm:749 #28 0x00000001000ae9bf in fl_wait (time=1e+20) at Fl_cocoa.mm:773 #29 0x00000001000aea86 in fl_mac_flush_and_wait (time_to_wait=1e+20) at Fl_cocoa.mm:792 #30 0x00000001000b9081 in Fl::wait (time_to_wait=1e+20) at Fl.cxx:528 #31 0x00000001000b910b in Fl::run () at Fl.cxx:589 #32 0x00000001000052a7 in main (argc=1, argv=0x7fff5fbff280) at dillo.cc:589 (gdb) print (char *)this $6 = 0x118148910 "lore ipsum the text out of the editor window in the email.\n\nMore lorem ibsum.\n\nRegards,\nJames." 0x118148910 is correctly allocated to dw::flak::ui::FltkLabelButtonResource, according to Apple's debugging malloc. I can't find, in the debugging malloc, the allocation for storing the text in the text-box. The worst cases are that someone is scribbling malloc control structures, or someone is scribbling addresses in a dillo data structure. I've seen something essentially the same where the scribble contained a URL. I'm contemplating relinking with electric fence. Regards, James.

1 0

Secure: yes, Though Features Missing; and Bugs
by miroslav.rovis1＠zg.ht.hr April 12, 2015

April 12, 2015

( I already wrote this entire message, and only then noticed eocene didn't send this to dillo-dev but only to me. But I now have to, All written. Can't correct that now. ) On Fri, Apr 03, 2015 at 08:14:36PM +0000, eocene wrote: > miroslav.rovis1 wrote: > > ukrainian at uabox ~ $ Domain: Default accept. > > By the way, if you're interested in making your browsing more secure, > you could modify your domainrc file not to have 'accept' as its default > rule. Let me first reply to this message. I really wish to start viewing dillo more comfortably first, so this will wait. But, since I started about it here, let me explain. Look here, how my dillo brings pages to me currently: https://forums.gentoo.org/viewtopic-t-1004014.html#7724054 and currently, download and open the mkv files... (So people reading later, open the, hopefully, webm files. That's how it was, talking to you in the future.) Those mkv files will, hopefully, soon be replaced with the HTML5 compliant webm files. So if opened those, that's how it shows currently. I was only able to use dillo after reverting my 1024x768 capable old monitor, to 800x600, in another display in X (:1.0 in, say, ffmpeg command line), else, I would have gone blind from effort to read. And I still have difficulty reading some of the pages. ##################################################################### The Homepage is particularly too hard to read for, I guess at least a non-insignificant though small percentage (no, not less than a small percentage number, it's not insignificant!) of visitors. The background must be very light. As soon as it is too dark, the font is not easily readable. ##################################################################### I'm not at poor-accessibility eyesight yet, I don't have problems with most of pages. I really don't. Pls. take notice of this claim of mine and value the outlined paragraph with respect to that claim! I hope this will help dillo homepage become more readable. So, first I really need the fonts, and will follow your kind advice, eocene, on the fonts, as soon as I find more free time. domainrc is great thing to try to sort too, but the other issue is urgent. Pls allow more time for me to reply to your other mail (I got two mails of kind advice from eocene. Can't go online (the SourceForge archive) to see if my bad provider and bad regime filtered some emails out from dillo-dev. Busy elsewhere. -- Miroslav Rovis Zagreb, Croatia http://www.CroatiaFidelis.hr

2 4

Documentation fixes: autolinking
by onepoint＠starurchin.org April 4, 2015

April 4, 2015

Three small patches that fix autolinking errors in the documentation. The first two escape the autolinking syntax in a few places where it was not intended to be a link. The third fixes a few places where a link was intended but the autolink syntax was not quite right. http://starurchin.org/dillo/patch/doxygen-escape-hash-characters.html http://starurchin.org/dillo/patch/doxygen-escape-double-colons.html http://starurchin.org/dillo/patch/doxygen-fix-simple-name-refs.html Comments are welcome. If these are OK I can push them myself as I have write permission. (It's actually easier for me to do it myself because Mercurial Queues does not notice when the remote repository has a patch that is identical to a patch in its queue and generates spurious errors.) Regards, Jeremy Henty

3 5

patch: provide a redirection-blocked page
by eocene＠gmx.com April 4, 2015

April 4, 2015

I was in the mood to make the use of domainrc more pleasant. Having to check the terminal for redirection-denied MSGs is no fun, and sometimes I imagine that I'm the only person who uses it due to its...limited friendliness. Patch attached.

1 0

Secure: yes, Though Features Missing; and Bugs
by miroslav.rovis1＠zg.ht.hr April 3, 2015

April 3, 2015

Hi! To me it is most important to avail myself of the security that dillo pretty much provides to me. What I can say, and recommend to anybody who has problems with `bulk collection' that they see in typical kind of actions deployed inside or on the way to, or on the way from, their machines... Sadly with `bulk collection' (previously known as `mass surveillance'; it comprises data harvesting and more) often go even worse kind of actions in privacy-repressive regimes: intrusions, even attacks... What I can say, is: I have so much fewer cases of the aforementioned issues when browsing with dillo, then I do when I have to, due to Javascript haven't yet been implemented in dillo, [than when I have to] use SchmoogleFox. So much fewer of those kind of problems! And yes, the Google, the Octopus of the Internet and the Surveillance Engine of the World, yes the Schmoog is sitting in the Firefox, in most of the regular users' machines who little depart from default configuration, and I don't think Mozilla harvesting itself can be easily disabled (you may remove direct Google harvesting/spying/other, but the Mozilla cloud is there, rest assured, for Google to use, fully!), and you can not, not that I know of an easy way --disprove me somebody!-- easily disable harvesting in Firefox... The security of dillo is generally such that I can usually rest calmly when I browse with dillo. And so I can recommend dillo to anybody who has problems with censorship, and when censorship of an oppressive regime is revealed, usually some kind of intrusion attempts, and/or attacks, are made against the one who managed to reveal it. To see more in depth about this claim of mine, read about dillo in the topics where I mention it on Gentoo Forums (just search for `dillo'): Updating and keeping your Gentoo non-poetterized https://forums.gentoo.org/viewtopic-t-1012022-start-0.html (currently three pages, dillo mentioned in 1st and 2nd. Before I close this first message, I'd like to show you this page where I demonstrated not just how the first Firefox harvest looks like on a Chinese style censorship deployed on dissenters in Croatia (that part is already posted: Google - can not open any link - malware ?? https://forums.gentoo.org/viewtopic-t-912056-start-25.html#7715646 but that topic I plan to improve adn add more content to yet) You can see that while I'm not really a programmer, I dabble with some ideas. This is my proposal for a program: https://github.com/miroR/uncenz I've been having censorship and related issues for really quite a number of years, By this current stage in my necessity-imposed research about it, I'm just about always traffic capturing when online, and you can find real and undeniable clickjacking and other intrusions (and learn about the Chinese style censorship and more; but, WARNING, the presentation is not so well made, and is unfinished) at: Postfix smtp/TLS, Bkp/Cloning Mthd, Censorship/Intrusion https://forums.gentoo.org/viewtopic-t-999436.html I believe that an objective reader, with a little time to read from my research there, can see that my praising of dillo is based on my sufficient understanding and experience. I really wish that you dillo developers may gather enough developer power to make dillo happen in the sooner rather than later future, much more capable than it already is. I can imagine what tremendous work creating and developing of a browser is! With that aim and wish in mind, I'd like to write and send another message about another buggish behavior in dillo. But in this message I can explain more about what I wrote on page 2nd of the topic already mentioned: Updating and keeping your Gentoo non-poetterized: https://forums.gentoo.org/viewtopic-t-1012022-start-25.html#7713858 > Other then one thing. dillo, which I used, has a little problem with > cache, that can be easily circumvented, but the user needs to remember > to refresh the page, and I inadvertently lost a little text... The above behavior occurs sometimes on my system, it occurs rather erratically, but rather often, when posting on Gentoo Forums. Not when posting a completely new post, but after editing an already existing post. It is easy to circumvent it, by simply, after having posted the previously edited post in question, refreshing the page which the post appears in. You can often see text literally changing upon refreshing it. The bug often occurs `in reverse', concerning posting. What I mean, is if you open a post for at least the third time --yes it must be a problem related to dillo caching; I understand so much even though I'm not a programmer, but just an advanced user-- so [if you open a post for the third time for editing], unless you refresh the editing texarea, in the same fashion: by clicking on the "Reload" button, you miight find yourself inadvertently to be editing the text that you posted the time before last, and not the immediately previous edit to this third edit of that text (even though the last text, the immediately previous, has, obviously, also been already committed, and should have been shown to you). The other bug, or is it my misconfiguration, or is it something else, I will try and write about in my next post. I sure will try and prepare the next message sson, and send it in a matter of hours or maximally a day or two. But if it does not arrive, the likelihood is that it is waiting for spies at my providers' to read it, and decide whether to send it on, or filter it out and not send it to dillo mailing list at all. Should the latter happen, pls. find that message at not much later time than maximally a day or two from now, in the topic Google - can not open any link - malware ?? https://forums.gentoo.org/viewtopic-t-912056-start-25.html surely, as a new post (which will, in that case, be yet to be written and posted there), and share the link with others on this list, please). (This note NOT related to dillo: Censorship is really a hard issue to overcome. Have a look at: Recover partly overwritten luks volume? https://forums.gentoo.org/viewtopic-t-1004014.html#7724054 --even though I praised dillo in that topic too-- nobody helped me there!) -- Miroslav Rovis Zagreb, Croatia http://www.CroatiaFidelis.hr

3 4

unicode combining chars and PRE
by eocene＠gmx.com April 3, 2015

April 3, 2015

Looking at http://doc.rust-lang.org/1.0.0-beta/book/more-strings.html#indexing-strings and I see that dillo doesn't like combining characters in PRE. Small example attached.

1 0