Jump to content

Mathwiz

Member
  • Posts

    1,830
  • Joined

  • Last visited

  • Days Won

    50
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Mathwiz

  1. But curiously, GM 4.1 does work (at least well enough to download Youtube videos) on the "official" Basilisk browser (version 52.9.2018.09.27); just not on @roytam1's XP builds (always say version 52.9.0). I'd think both versions would have the same WE APIs Nevertheless, since I reverted to the WE add-on for Basilisk on XP, I think this is the best solution: I'll try it when I get back to my work PC on Monday and let you all know if it solved the problem. Edit: Ugh. Chase has made some annoying changes to their Web site: network.http.sendRefererHeader must be set at the default of 2 now; otherwise you don't even get the login prompt! User agent must be a "classic" FF UA (no mention of Goanna or Basilisk), or you get their "your browser is out of date" nonsense and are redirected to Chase's mobile site. ("Official" Basilisk mentions both Gecko and Goanna, and both Firefox and Basilisk in its UA when FF compatibility mode is set to "true;" this is fine for most sites but not Chase's.) Oh, well, the option to disable SF.net for the Chase website seems to work, at least on "official" Win 7 Basilisk; so I'm hopeful it will work on Roytam1's XP builds too. As I said, I'll find out Monday.
  2. New Moon uses different config options than Basilisk. In NM you have to set it in Preferences / Advanced / General / Compatibility:
  3. So, I installed the web extension in Basilisk and Greasemonkey and the sf-helper user script in NM. Both work fine. However.... ... the web extension version prevents me from logging into Chase.com on Basilisk! I would never have figured that out, except I have the "official" version of Basilisk for the Win 7 side of my PC, and I didn't install the web extension there. The user script version didn't block me from logging into Chase from NM 28, so I'll try it on the Win 7 side and see if it gives me the best of both worlds.... Edit: The script seems to work with Greasemonkey 4.1, and without interfering with me logging into Chase. So now I'll try it that way on the XP side. Edit 2: No joy. Greasemonkey 4.1 installs on @roytam1's Basilisk XP build, but doesn't seem to work for some reason. So I guess the easiest solution on Basilisk XP is still to use the web extension, and just disable it when I want to log into Chase, and re-enable it when I want to download Youtube videos.
  4. This problem has been reported since August. Changing the user agent usually seems to be enough; apparently Twitter likes to feed Basilisk (but not FF) a format it won't decode properly. IIRC @dencorso reported that installing Adobe's PrimeTime CDM and disabling ffvpx also fixed this strange problem, in case changing the user agent isn't your thing (or doesn't work for some reason).
  5. Looks like buggy browser detection by Twitter. Probably doesn't know that PM 28.2 is equivalent to FF 52.9. Their code probably misparses the user agent and "assumes" you're running an ancient version of FF. Try setting general.useragent.override.twitter.com to "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.9) Gecko/20100101 Firefox/52.9" in order to spoof FF 52.9 on Windows 7. If that doesn't work, try replacing the "52.9" in both places in the string with a newer FF version until Twitter likes it. Or you can try an IE 11 override: "Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko"
  6. Thanks. I've been wondering for some time if using Primetime would bypass the 23 min. bug. Sorry to hear it doesn't, but at least now we all know. The bug probably appears in all recent FF versions and forks, including PM/NM and Basilisk/Serpent. Does anyone know of any exceptions? Basilisk 55 perhaps? Or do we just have to use Chrome/Chromium for long YouTube videos?
  7. I have mine set that way too, on both versions of Windows. Most sites are on TLS 1.2 now but there are a few that still need TLS 1.0. Personally, I wish there was an option to have TLS 1.0 enabled, but with some sort of visual cue that the site was using a less-secure protocol. But with Win XP, I'll take what I can get these days.
  8. Ideally yes, but in practice I've found a few sites still using TLS 1.0 (!) and at least one (www.fedex.com) which only supports weaker cipher suites. So you may find you need to keep a few that SSLLabs marks with orange. Try to keep them to a minimum, though.
  9. I thought Kindle was a great idea; yet I never trusted it for that very reason: from the get-go it was designed so Amazon could pull back anything you thought you owned. BTW you need to update the link above to https://en.wikipedia.org/wiki/Amazon_Kindle#Criticism. Wikipedia's editors didn't send the criticism of Kindle down the memory hole, but they did relabel it a bit
  10. It's not just computers and printers either. About a year ago someone reported on AVSForum that a working Amazon Prime app got pulled off his Vizio TVs! I posted this on that forum in response: I could understand it if Amazon changed something that broke the Vizio streaming app - his Vizios are five years old, after all. I've heard of built-in YouTube apps being rendered useless the same way: Google changes something, and old apps stop working. If you can't get an update, you're SOL. But as I understand it, it's not just that technology advanced and rendered the streaming app in his Vizio TVs useless. Read Don's quote: (Emphasis added.) IOW, someone (it was probably Vizio, not Amazon, but it doesn't really matter) went in to his older TVs over the Internet and deliberately removed a working app from them! That's not just the inevitable march of technology, or even planned obsolescence - it borders on hacking.... We're living in a brave new world where corporations feel free to meddle with the products we thought we owned, possibly even to just make them less useful so we'll have to upgrade. I've had Micro$oft do this with WMC more than once (not to mention their yearlong push to "upgrade" me to Windows 10, which would have removed WMC entirely), and I've had Facebook do it with their app for older BlackBerrys. Of course, you can take that too far. I know folks who now refuse even security updates from Micro$oft because of the distrust generated by M$'s "free" Windows 10 upgrade campaign, the telemetry (read: spyware) that M$ has built into some updates, etc. Of course that leaves them vulnerable to viruses, ransomware, etc., so I think they're going too far; nevertheless I understand their decision even if I don't take the same chances with my own PC.
  11. My concern, though, is that once Jan. 2020 arrives, M$ will change the "ApplicabilityInfo" string for newer updates to just read "Windows 7.0 Embedded;" etc. and they will no longer install on our Windows 7 Client systems without patching. Edit: OTOH M$ didn't do that with Windows Server 2012 updates; they still install on Windows 8 Client, so maybe there's nothing to worry about. I guess we'll all find out in 2020.
  12. Well, it isn't really used for DRM content decryption anymore, and Vista users have the Windows Media Framework to fall back on if ffvpx fails them in some way (like the Twitter audio bug). So if you're on Vista, I can't see why you would need or want it. But it is useful on XP. Since the same browser is used by users of both OSes, it probably makes sense to keep it separate. That way XP users can install it if they need it, without bloating the package for Vista users. Besides, like any add-on it gets installed in your profile folder, not the main program folder, so it would be tricky to include in the browser package anyway.
  13. Good. I didn't think you would have any problems, but it's always good to hear that everything still works.
  14. I'm pretty sure the Twitter audio bug was narrowed down to the ffvpx library. Go to about:config, search for media.ffvpx.enabled and switch it to false. If you're using XP you'll also need to download and install the Adobe Primetime CDM as described in the next sticky. Edit: Aaand, I just remembered, that only works in Serpent, not NM 28. :(
  15. Slightly OT, but I tried Basilisk on both Win 7 and XP. Both have Primetime version 17 installed, but only the Win 7 version has Widevine (v1.4.8.903). On Win 7, Bitmovin detects both plugins and tries to use Widevine. Unfortunately the stream stalls after 0:43 seconds have downloaded and won't play. If I disable Widevine, it detects Primetime but plays a non-DRM version of the video. Looking at the Javascript, it appears only Widevine and Playready DRM are supported. On XP, Bitmovin doesn't detect Primetime, even though it's installed and usable for non-DRM content. Castlabs won't play DRM versions on either platform. When a DRM stream is used, on Win 7 the "Stream Info" shows DRM Used: Loading... and stalls. On XP it stalls without the "Stream Info" box appearing at all. Both browers are set to spoof FF 52.9 on Win 7, so it can't be a user agent difference.
  16. One small note: on the Serpent (Basilisk) browser, you click "What's New?" vs. "Release Notes" on NM.
  17. You should also uncheck "Use SSL 2.0" and "Use SSL 3.0" in Internet Options / Advanced under Security. Nobody uses those anymore (unless they're trying an exploit).
  18. He has a precompiled version. Everything is built into the .exe. No need to install Python or OpenSSL. But if you'd prefer to try the updates, they are: KB3055973 (adds AES to the base OS); KB4019276 (download / info; adds TLS 1.2 to the base OS); and the latest IE8 cumulative update (KB4462949; updates IE8 to use the support added by 1 & 2). All are POSReady '09 updates. I think there's a way to install them without putting the POSReady entry in the registry, but it's probably more complicated than just going with POSReady. Also, those updates may not be enough. There is still no support for Elliptic Curve Cryptography, so any sites that use it won't work even with all the POSReady updates. ProxHTTPSProxy replaces native support completely, so it supports ECC and can be updated to support any other new security requirements, such as TLS 1.3. But I agree with @siria. There's no "simple" update for IE8. If you want simple, just use Firefox 52.9 ESR and be done with it.
  19. PM @heinoganda and ask for his latest version of ProxHTTPSProxy. I believe he also has instructions on setting it up. I just tried https://mobile.twitter.com in an IE tab, and with ProxHTTPSProxy it came up fine, images and all. Edit: BTW if you enable the POSReady '09 updates, there are updates to IE8 that let it support some of what you need (specifically TLS 1.2 and the AES cipher) without ProxHTTPSProxy. But ProxHTTPSProxy supports all that whether or not you enable the POSReady '09 updates.
  20. Free download at SourceForge: https://sourceforge.net/projects/naraeon-ssd/
  21. Probably need to benchmark decoding. If ffmpeg 4 is faster at that, then it'd be worth patching it for XP; but otherwise just leave it at the current version.
  22. Thanks! I saw those preferences but wasn't sure what they did, so I didn't mention them. It may be better to just ignore the whole mess and put your preferred user-agent string in general.useragent.override. That way you can spoof the Windows version as well as the FF version of your choice. Some sites are starting to balk at NT versions less than 6.1 (Win 7).
  23. Calling @FranceBB; your Avast expertise is needed
  24. There are a number of preferences that affect the user agent in the about:config page. general.useragent.compatMode.firefox is a Boolean preference, which tells PM/NM and Basilisk/Serpent to spoof Firefox. It defaults to "false" in PM/NM and "true" in Basilisk/Serpent. You could set that to "false," and these browsers would then identify themselves more accurately, but few Web sites recognize PM specifically, so this may just confuse them even more. general.useragent.compatMode.version is a string preference that defaults to 52.9 and tells PM/NM (and Basilisk/Serpent) which Firefox version to spoof. So the simplest answer to your question is to change this to the FF version you want NM to spoof, say, 60.2. general.useragent.override is a string preference you can create to send whatever string you assign as the user agent. Using this you can pretend to be an iPhone using Safari or any other platform/browser combo you want. You'd need to know the user agent string for the combo you wanted to be, of course. general.useragent.site_specific_overrides is a Boolean preference that defaults to "true." You could set this to false to temporarily turn this feature off to test/debug specific Web sites, but the default of "true" allows NM to recognize additional preferences of the form.... general.useragent.override.facebook.com = "<custom user agent string to be sent to facebook.com>" The idea behind those last two is that you don't have to send every Web site the same user agent; helpful if spoofing FF 60.2 (or whatever) causes some websites to send content NM doesn't handle properly.
  25. Confirmed, sort of; at least with the latest build of New Moon (28.2.0.a1 dated 2018-09-28). I had to add all the required preferences manually; after that, my gmp-adobe-eme\17 folder didn't get deleted, but Primetime still wouldn't show up in about:addons or about:plugins. Looks like the PM team did more to disable EME than just removing those preferences. Don't know if Primetime will work with MyPal but I sort of doubt it at this point. Primetime does work with Basilisk, and I suspect it will also work with @roytam1's FF 45 build for pre-SSE2 machines. And of course it works with FF 52.9.
×
×
  • Create New...