
Mathwiz
MemberContent Type
Profiles
Forums
Events
Everything posted by Mathwiz
-
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
I'll have to try the WE version of uBO on Basilisk 55 just to see what happens. -
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
Cool! Keeping WE was as simple as specifying a build option? -
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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. -
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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. -
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
-
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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. -
Beware of Office 2010 Updates!
Mathwiz replied to Dave-H's topic in Pinned Topics regarding Windows XP
OK.... Hid that one too.... -
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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. -
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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? -
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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. -
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.
-
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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. -
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
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. -
Wikipedia uses a certificate with an Elliptic Curve public key algorithm. XP still doesn't support that. I doubt we'll get a patch by April either.
-
My Browser Builds (Part 1)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
I'd been using that myself, but decided to stop in favor of the "Canvas Defender" add-on. The purpose of the canvas.poisondata pref is to randomize canvas data to avoid fingerprinting. However, there's a problem with this approach: most browsers don't have that feature. Even NM/Basilisk don't enable it by default. So all Facebook, Google, etc. have to do is to run the fingerprint twice, observe that the browser returns different results each time, and they'll know that the user belongs to the small subset who have browsers or add-ons that poison canvas data. Then other, less precise fingerprinting techniques can still uniquely identify users within that small subset. Canvas Defender, in contrast, changes canvas data periodically rather than every time a fingerprint is attempted. The rate of the periodic changes can be set anywhere from once per minute to once per week (or turned off completely so you can change it manually as desired). The idea is to look like one of the "unwashed masses" who don't poison their canvas data (thus allowing tracking for a while), while in reality poisoning canvas data often enough to render said tracking useless. -
Yes, it's there and set to Always Activate. Edit: Turning off e10s didn't help. It runs in Safe Mode though, so it's probably conflicting with some add-on. Edit 2: Found it! It was Canvas Blocker.
-
Interesting. Runs fine in IE8, Advanced Chrome (NPAPI support restored), and NM 28, but not Seamonkey 2.49.5 or Basilisk/UXP (neither official on Win 7 nor Roytam's build on XP). On those I just get prompted to install Silverlight Anyway, it's clearly XP-compatible.
-
If @rockmaster113 is lucky, Slack is just blocking older browsers so that they have fewer configurations to test, and fewer variables to contend with when they take support calls. I'm hopeful that a spoof will let Slack work, if not with FF 47, then at least with FF 52 or one of @roytam1's Basilisk builds, which were forked from FF 52 & 53 with few changes. It may look different when rendered by Gecko or Goanna vs. Quantum or Chromium but hopefully it'll still be usable. Anyway, we'll find out in March.
-
I'm not sure, but if you only install kb4019276, you may need to make some registry changes to enable it. More info here: https://support.microsoft.com/en-us/help/4019276/update-to-add-support-for-tls-1-1-and-tls-1-2-in-windows I included those registry changes in my .reg file to disable insecure algorithms, posted right after the post I linked to.
-
Scribd.com only supports TLS 1.2 with AES now. Make sure you have the updates listed here (you can ignore the references to Skype): KB4019276 adds TLS 1.1 & 1.2 support to XP; KB4230450 (or any subsequent cumulative IE8 update) adds them to IE8 (which may or may not be necessary for Internet Download Manager).
-
Adobe Flash, Shockwave, and Oracle Java on XP (Part 2)
Mathwiz replied to Dave-H's topic in Windows XP
Yes, @Dave-H & I both decided to post about today's Silverlight update at around the same time. He picked this thread & I picked another -
Adobe Flash, Shockwave, and Oracle Java on XP (Part 2)
Mathwiz replied to Dave-H's topic in Windows XP
It is - if you spoofed 32-bit Win 7 or later in your browser's user agent string. (Actually, spoofing a 32-bit browser on 64-bit Windows would probably work too, but I didn't try that.) Vista and XP are offered older versions. 64-bit Win 7 is offered a 64-bit version, of course. BTW, on Firefox or its derivatives (NM/Serpent/MyPal/Seamonkey/etc.), make sure to use/spoof version 52, since later versions don't permit any plug-ins besides Flash. Edit: BTW, does anyone know of a good Silverlight test page (other than Amazon Prime)? -
Believe it or not, 5.1.50907 may not be the final release. On Win 7, WU just today updated Silverlight to 5.1.50918! Edit: It looks like one of those updates to handle the new Japanese era (like the Office 2010 updates M$ keeps fouling up), so it may or may not be compatible with XP. I checked MU on my XP VM. The update wasn't there, but since POSReady '09 is still supported, it still might appear in a day or two. Edit 2: Downloaded the new Silverlight to my XP VM and installed it. Does anyone know of a good Silverlight test page?
-
Adobe Flash, Shockwave, and Oracle Java on XP (Part 1)
Mathwiz replied to dencorso's topic in Windows XP
I realize this is several months late, but Shockwave for Director 12.3.4.204 was released on June 6, 2018. I just found out! Edit: Here's the download link. http://fpdownload.macromedia.com/get/shockwave/default/english/win95nt/latest/sw_lic_full_installer.exe