Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/05/2021 in all areas

  1. yeah, because there are some bit width problems in variable, and problem is revealed in the conditions in the code after security patches applied. fix is simple as well: https://github.com/roytam1/basilisk55/commit/fc7f3915a7bd9d30615f0430c9c014f7fd758b76 EDIT: also reported to upstream: https://github.com/classilla/tenfourfox/commit/4f70dd5c954cfcfd55357527da98c15f8355fbe5#r59478686
    3 points
  2. NewMoon28: ok K-Meleon: ok Mypal: ok Serpent52: ok Serpent55: same result as you / "This address is restricted"
    2 points
  3. Now long EOS Windows Embedded 2009 still living it large in my local Marks and Spencer store! Not quite XP or course, but as near as makes no difference now as far as I'm concerned.
    1 point
  4. I'm just using ".ipsQuote {background: unset !important;}" for now. I hope very strongly that we don't find a way to post those intentionally. It would be very annoying for everbody to start posting "look at me" posts and everybody having their own background color.
    1 point
  5. Since the beginning, several years ago, I have W. firewall disabled. No problems. I use SterJo NetStalker...
    1 point
  6. And fine with FF 53 too. Evidently a very unique bug. I see; the procedure is passed a 32-bit value, and wants to ensure it's a valid port number (in the range 1 to 65535), so that you'll get the error if you enter something idiotic like microsoft.com:0 or google.com:65536; but it was first assigning the 32-bit value to a 16-bit value, cutting off the high-order bits and rendering the check for being over 65535 meaningless. Worse, it was a signed 16-bit value, so anything over 32767 tested as less than 0 and was blocked as an invalid port number! Edit: Roytam's fix works! BTW, I saw that he found and fixed the same coding mistake in FF 45 and the Tycho browsers (PM 27 and KM); yet it didn't cause the same bug, at least in the FF 45 build I was using. (Haven't tried the others.) Like later FF versions, FF 45 accessed port 50100 just fine.
    1 point
  7. Good - sounds like the issue was unique to the Moebius platform and doesn't affect UXP browsers. Which sort of makes sense, because IceApe is itself a UXP browser - I think they would've noticed if they couldn't browse their own change log!
    1 point
  8. I only connect through wireless router which uses hardware firewall via cable box. If I connect "direct" (which I used to do), I used Comodo, version 8.4 if I remember correctly. But on WIRELESS and living on the outskirts of town basically in the country where the closest neighbor is a quarter of a mile away, I do not use "software" firewalls as I see them as no different than anti-virus software - a "bottleneck" to SLOW THINGS DOWN, throwing so many FALSE alarms that the user just blindly clicks 'ok' or 'continue' without even realizing what they are "allowing", et cetera.
    1 point
  9. Hi there, I sent a small donation of USD 10.00 via PayPal for the forum but in my account it still reads I already sent a message about it using the contact option but I got no reply. Is there any staff around to check if it was received? Regards, Hyper.nl
    1 point
  10. 50100 is not banned as it is not listed in https://github.com/roytam1/basilisk55/blob/master/netwerk/base/nsIOService.cpp#L98 you may check if there is pref `network.security.ports.banned` and try resetting it. or you may add 50100 to string pref `network.security.ports.banned.override` in about:config.
    1 point
×
×
  • Create New...