Jump to content

Mathwiz

Member
 View Profile  See their activity

  • Posts

    1,867

  • Joined

  • Last visited

  • Days Won

    51

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by Mathwiz

  1. Mathwiz
    New one today: KB4462172 File Oart.dll was updated. Seems harmless, albeit probably pointless since KB4462157 can't be installed on XP.
  2. Mathwiz
    There's a simple workaround:
  3. Mathwiz
    Come to think of it, I remember @VistaLover mentioning that too. (The drawback is, you have to redo that for every new update.) But I rolled back to legacy for other reasons anyway.
  4. Mathwiz
    The quickest solution is probably ProxHTTPSProxyMII v1.5: Works for IE8 and Chrome. @Thomas S. has made an updated version of the above; PM him if interested.
  5. Mathwiz
    1.17.4 is also the latest for @roytam1's Basilisk 52 build. (Basilisk 55 went up to 1.18.2 last I checked.) But I downgraded to 1.16.4.7 (for reasons I explained in the New Moon thread). I also had to disable automatic updates to keep Basilisk from updating uBO again. I'll give 1.16.4.8 a try. Edit: Looks like the only difference is the addition of Spanish. Everything else still working as before AFAICS.
  6. Mathwiz
    How do you enable WebGL compatibility? I only see gecko & firefox
  7. Mathwiz
    New version (1.5) of ProxHTTPSProxyMII released by the original author: The full version, compiled with Python 3.4, is at http://jjoe.proxfilter.net/ProxHTTPSProxyMII/files/ProxHTTPSProxyMII 1.5 34cx_freeze5.0.1urllib3v1.22Win32OpenSSL_Light-1_0_2o-1_1_0h.zip. (Whew; what a file name) I'm running it now; seems to work fine. I can access Wikipedia from IE8. (I know; why would you want to? But it's a good test due to Wikipedia's ECC cert. )
  8. Mathwiz
    So you need a legal bcrypt.dll that runs on XP. ReactOS? Wine?
  9. Mathwiz
    Have you tried YouTube without the spoof? Since it thinks you're Chromium 71 it may send incompatible code.
  10. Mathwiz
    The versions of ProxHTTPSProxyMII we've been using all derive from version 1.4 of the original, but apparently it's still being maintained by the original author, and last June a version 1.5 was released with some changes: Edit: The link @-SnooPY- provided had Python code only. I guess that's what @-SnooPY- is trying to get working with Python 3.7. The full version, compiled with Python 3.4, is at http://jjoe.proxfilter.net/ProxHTTPSProxyMII/files/ProxHTTPSProxyMII 1.5 34cx_freeze5.0.1urllib3v1.22Win32OpenSSL_Light-1_0_2o-1_1_0h.zip. (Whew; what a file name)
  11. Mathwiz
    Darn: WebRTC option still greyed out on uBO 1.18.2 on Basilisk 55. Apparently, enabling that option requires a FF version > 53, which makes it a no-go for XP. I'm switching to the legacy version of uBO in Basilisk 55 too....
  12. Mathwiz
    Evidently it works; all my WE add-ons are still enabled.
  13. Mathwiz
    I'll have to try the WE version of uBO on Basilisk 55 just to see what happens.
  14. Mathwiz
    Cool! Keeping WE was as simple as specifying a build option?
  15. Mathwiz
    That put my mind somewhat at ease, although I'm not directly affected since I don't use modern Firefox anyway. BTW, I think this statement was wrong: As you know, I just switched to the legacy version of uBO because it has a capability the WE version doesn't have: blocking WebRTC from leaking your local IP address. Of course the WE version probably has some capabilities the legacy version lacks too, but it's not as clear-cut as Handsome_Jack implied.
  16. Mathwiz
    I don't think folks should have to click through to see what's being discussed, so TL;DR: So, it's still just a proposal, but I'd bet on more Chromium forks like Advanced Chrome if it goes through. And Mozilla following suit would be MC's wet dream. The popularity of PM & especially Basilisk would increase tenfold overnight. But since neither Chrome nor FF supports XP or Vista any more, none of this matters to us anyway.
  17. Mathwiz
    Try the following registry entries: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client] "DisabledByDefault"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server] "DisabledByDefault"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "DisabledByDefault"=dword:00000000
  18. Mathwiz
    So for WebRTC protection, I too ended up going with uBO 1.16.4.7, for the following reasons: Been using uBO anyway Gorhill still maintaining the legacy version (1.16.4.7 was released 2 days ago) No need for separate WebRTC add-on No need to modify anything to allow installation (which would need to be redone for each update) No need to disable WebRTC entirely in about:config Edit: I should have known this, but didn't realize it until now. If you downgrade to 1.16.4.7 you need to turn off automatic updates, or Basilisk will just re-update you to 1.17.4.
  19. Mathwiz
    OK.... Hid that one too....
  20. Mathwiz
    Yes it does, and in fact it supports WE even better than 52, but I have a couple of add-ons (Abine's Blur and Exif Viewer) that are incompatible with 55. Also most of my plug-ins don't seem to work.
  21. Mathwiz
    Wow - that didn't take long: 16 hours from @Sampei.Nihira's initial post to the actual code commit. (Of course I know it was actually longer since the PM team made the decision, but still....) That means the commit will be in the next official Basilisk release. Guess we'll see how long @roytam1 can hold out. Mozilla wants me to toss all my legacy add-ons; MC wants me to toss all my WE add-ons. AFAIK the only browser left that will support both is Waterfox. Not XP compatible; yet it might work on the Win 7 side - except it's a 64-bit browser, so I'd still need to replace all my 32-bit add-ons with 64-bit versions. Three choices; three hassles. Why can't I just keep running the add-ons I have?
  22. Mathwiz
    Thanks. I have UBO. The WebRTC checkbox on my UBO settings page is greyed out; possibly because I installed the WebRTC add-on (via @VistaLover's suggested mods) for testing. Really, the only advantage of a dedicated add-on is that you can toggle your internal IP address on or off with one click. Otherwise, you have to go into UBO, open the dashboard, click settings, and click the checkbox. Or you have to go into about:config, filter, and toggle the media.peerconnection.enabled setting. I would think either is too much trouble for folks that actually use WebRTC.
  23. Mathwiz
    I was about to suggest you try that! It seems to be a variant of Murphy's Law: Every "upgrade" will include one or more actual downgrades.
  24. Mathwiz
    I get their point; but the obvious problem is, some of us are already using some WebExtension add-ons in Basilisk, so this breaks compatibility with our browser set-ups. IMO it would be better to leave WebExtensions in the code & just not do any further development on them (except for security fixes). Editorial: I wonder if the PM team is unclear on the problem with WebExtensions. As I see it, the problem isn't that they exist; the problem is that Mozilla decided to force everyone to rewrite their add-ons to use them, in order to install on newer FF versions; thus disabling any legacy add-ons that weren't actively being maintained. This is the main reason I switched to Basilisk in the first place - I didn't want to have to find replacements for all my legacy add-ons - but now the PM team is about to make the exact same mistake, in the opposite direction! Maybe there are also a couple of unstated reasons for the PM team to remove WebExtensions from Basilisk: To remove any incentive to move from PM to Basilisk in order to use newer WebExtension add-ons To further incentivize add-on developers to maintain legacy versions of their add-ons I may have to start using your XP builds even on Win 7, just to keep compatibility with my existing set of add-ons.
  25. Mathwiz
    Thanks for the clarification. Good to know that "appears to be corrupt" might only mean "not supported." Since I, personally, don't use WebRTC, I just disabled it in about:config on my browser. But as I posted, someone who does use WebRTC needs a more convenient way to toggle it on/off.
×
×
  • Create New...