Jump to content

VistaLover

Member
  • Posts

    2,084
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. ... Well, all I can tell you is that "my inner circle" most probably doesn't know what FUD means ; I have picked that up some years ago, by reading posts on the net ; and yes, I had to first look up its proper meaning ...
  2. ... Respectfully, "there" is off-topic , "here" it is NOT ... Actually, I did read chermany4ever's comment in the "roytam1 browsers" thread and specifically elected to respond to him inside the "proper" Supermium thread here, rather than there; and when I changed tab focus to this thread (to finish my reply), your "comment" there wasn't yet public/visible ; hence, I "continued on my merry way" ... Regards ...
  3. GitHub member Okmeque1 has recently reported that the very latest Hotfix (R2) release, https://github.com/win32ss/supermium/releases/tag/v122-hf is able to launch and run successfully in his machine; it has WinXP SP2 x86 as the OS : https://github.com/win32ss/supermium/issues/341#issuecomment-1984464451 https://github.com/win32ss/supermium/issues/341#issuecomment-1987143081 Full thread here ; you may then want to give it a try yourself ...
  4. ... I did some further testing today and it appears that the cut-off value has been set at Chrome/100.0 (for the tests to work, one has to wipe out browser cache and "sciencedirect.com"-set cookies before testing a different "Chrome/*" value ); 100+ will load the site fine in 360EEv13.x/KMB , 99- will redirect to the "browser-out-of-date" page ; since this is a block purely based on UA-sniffin', I would argue they had blocked older clients for "security-related FUD"; I don't believe their servers risk any harm by allowing those older clients though, the tactics smell of forcing the user to switch to a more "secure" browser version (however, v100 is still far from v122 , the current Google Chrome) ...
  5. ... It's probably this one : https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/getTransform Requires Fx70+ , Ch68+ ...
  6. ... Erh , you mean "previous" month ... ... That's probably true , but the other-way-round isn't a given; not the whole of UXP has been backported to St55 (but. at the same time, St55 has some vestiges inherited from Fx53.0a1); please also try, if you will, 2.16-"legacy" on UXP (probably won't work there, too, but...) ...
  7. ... Is it the "standard" or the "legacy" dist(ribution) for current UXP?
  8. ... There exist several "caches" in Chromium-based browsers: Browser Cache, App Cache, ShaderCache, GrShaderCache, Code Cache, GPUCache (this list from my KMB profile; Ch87-based ); I'm not aware of a "method" to clear browser cache on a "per-site" basis (probably exists, just not aware of it ) ... As for the second part of your question, it seems to be a recurring one : https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1216282 ... and an answer from "yours, truly": https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1216289 Then again: https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1223512 ... and an answer from NHTPG: https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1223515 For your convenience , it might be best to use the Bookmarks feature on your browser ... Cheers ...
  9. ... Apologies for asking, but your statement isn't quite clear to me ... SumatraPDF is a standalone application that can handle (local) PDF files, how can it be used "with" Serpent 52's native (built-in) PDF viewer (pdf.js, written in Javascript) ? Do you actually mean that for PDF files on your system, you sometimes use SumatraPDF and other times you use St52 (as a PDF viewer) ? FWIW, SumatraPDF used to come with a NPAPI plugin that could be configured to handle PDF files inside a supported browser (St52 is one ), but that NPAPI plugin was removed, starting with SumatraPDF-3.0 ; apparently, there's a hacky way to keep using the last available plugin version (2.5.2) with newer versions of the SumatraPDF application, but this is an unsupported configuration, i.e. "you're on your own": https://web.archive.org/web/20170424012056/https://github.com/sumatrapdfreader/sumatrapdf/wiki/Browser-plugin
  10. The initial implementation has issues correctly displaying emojis under Windows XP, e.g. on GitHub: https://github.com/win32ss/supermium/issues/333 A hack-y "fix" has been made available by the author: https://github.com/win32ss/supermium/issues/333#issuecomment-1982403569 (will ONLY render monochrome emojis in Win<8.1 )
  11. There exists a project (now, seemingly, an "abandonware" ), last updated in June 2020, which offers "pdf.js" in the form of a "legacy" XUL extension: https://github.com/IsaacSchemm/pdf.js-seamonkey/releases/tag/v2.3.235 The release notes of the last version state that it's based on pdf.js-v2.3.200, so you got further than them ; the provided XPI file comes with l10n support , which was the main reason I had tested it back then in my "dirty" St52 profile ; after some days of testing, I bumped on some incompatibilities (the details of which evade me now ), so I ended up uninstalling it and reverting to the St52-embedded (English-only) "native pdf.js viewer" ...
  12. (redacted) InitializeProcThreadAttributeList requires Vista SP2 as "minimum supported client" ... This crashpad crash under Windows XP has been fixed, for now in source code, only: https://github.com/win32ss/supermium/commit/08170feefcfbcd750b377d4c11a4efc67279ed9e No binary fix available yet; the next "hotfix" release should incorporate it, hopefully ..
  13. Given that the current Google Chrome "stable" release is at v122.0 as I type this, it comes as no real surprise that sites are starting to "blacklist" our "legacy" Chromium browsers (360EEv13.x, KMB) via "User-Agent-Sniffin'", simply because they report a Chrome/86[/87] slice inside their default UA string... So far, they're not many , but this is expected to change in the future ... The most recent case I encountered is the one of "sciencedirect.com", after a Google Search result had pointed me to: https://www.sciencedirect.com/topics/computer-science/protected-storage I was "greeted" by: I'd have expected a "science-related" site to have implemented truly scientific means (i.e. feature-detection) to check whether "my" browser is able to display it properly, but, hey, even "scientists" must have "sold their souls" to Google and company (a figure of speech, surely, but ...) ... At this point in time, I've opted for a SSUAO rather than a "global" one via the " --user-agent" cmdline flag ; several extensions offer this functionality, I've chosen Custom UserAgent String ; you need the older v0.2.1, the last on MV2 : At last, I was then able to be "scientifically" informed using 360EEv13 ...
  14. ... Other people on XP SP3 have experienced that error, too : https://github.com/win32ss/supermium/issues/318 InitializeProcThreadAttributeList requires Vista SP2 as "minimum supported client" ...
  15. ... For those not closely following the development in GitHub , Supermium v122 has been publicly released: https://github.com/win32ss/supermium/releases/tag/v122 https://github.com/win32ss/supermium/discussions/316 The new installer (both 32 & 64-bit) promises WinXP compatibility; the portable distributions appear to be, again, behind a paywall: https://www.patreon.com/posts/supermium-122-99791603 https://www.patreon.com/win32/shop/supermium-plus-package-march-2024-30-day-138343
  16. ... Besides .\browser\!omni.ja\chrome\pdfjs\content\* ... I find some locale files are also relevant: .\browser\!omni.ja\chrome\en-US\locale\pdfviewer\* (St52) ; have these been taken into account while "testing" ?
  17. ... FTR, you did not say (rather, write ) the "no sense" part; you actually "said": ; the "no sense" "argument" was brought up by Anbima: ... and it was this "argument" by him the portion of my reply you quoted above was addressing ; just as a disambiguation ... ... If I'm not terribly mistaken , Mozilla were the first to do this thing in their own browser, Firefox, many years ago already: https://bugzilla.mozilla.org/show_bug.cgi?id=1269807 https://www.ghacks.net/2015/10/08/mozilla-announces-the-end-of-npapi-plugins-in-firefox/ https://support.mozilla.org/en-US/kb/npapi-plugins https://support.mozilla.org/en-US/questions/1270346 ... Unless you were referring to the Firefox-based forks "we here" use, which just consolidates my prior argument : Best regards ...
  18. ... Well, the relevant info has been already posted inside Supermium's official GitHub issue tracker, https://github.com/win32ss/supermium/issues/127#issuecomment-1868304931 so its author should be aware already ; given that the linked comment hasn't received yet any reaction or subsequent reply , one can assume that the "CastLabs route" isn't being considered, at least not at this point ...
  19. ... That's NOT accurate to say ; while both OSes are NT 6.0, per your linked documentation: Windows Vista SP2 x86 & x64 Official Extended Support was EoL'ed on Apr 11th, 2017 : https://learn.microsoft.com/en-us/lifecycle/products/windows-vista It is indeed true that the WS 2008 SP2 targeting updates released some two years after Vista's official End of Extended Support can be installed manually on the OS and bestow SHA-2 support on it, but this practice isn't considered "official" by either the vendor (Microsoft) or the rest of the third party vendors (Norton in this case ) ... Kindest regards ...
  20. ... I launched my Kafan MiniBrowser (KMB) copy (Chromium 87 based) on my Vista SP2 x86 OS with below command-line argument: --user-agent="Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36" Then I navigated to: https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm?hl=en Guess what? Yes, the previous banner: no longer displayed, but ONLY to be replaced by a new banner, stating: WT... ?
  21. @rereser : I only posted my newer screenshot (of "new" CWS) above as an indication that Google's wording has changed in the interim since my previous screenshot of Feb 15th, 2024, when they offered a (non-working ) alternative choice: "... visit the legacy store" ... As for your posted mitigation in the shape of a userscript, I've already talked about it (and its shortcomings ) in my post of Feb 15th: Kind regards ...
  22. However, clicking on the "Visit legacy store" area (JS-controlled button) will only start a vicious circle , resulting in that same "new CWS" page ... Well, it's March 1st in my timezone already , and the "in-page info banner" no longer offers the alternative of "visiting the legacy store" :
  23. ... I don't want to "burst your bubble" , but even if you manage to sort out all dependencies of the DLL under NT 5.1, the CDM will be practically non-functional on most popular DRM'ed services (e.g. Netflix, Amazon Prime, Hulu, Spotify, Apple Music, Tidal, etc.) ; since years now, Google (owners of Widevine CDM) have implemented the Verified Media Path (aka VMP) security feature: https://www.expressplay.com/products/google-widevine-drm/ In layman's terms, this means that the application within which the CDM is run (Supermium in your case) must've been previously whitelisted/sanctioned by Google ; this process involves acquiring special certificates from Google, for DRM purposes only, and signing various browser components (e.g. "chrome.dll") with said certificates; when the CDM is requesting decryption keys (aka "licence") from a Widevine lic server, it first sends (obfuscated) a payload with extreme detail of the environment it's currently running on; this detail includes exact browser specifics, as well as the OS/device the browser is running on; the WV lic server can reject the licence request if the CDM version/browser/OS/device is not to Google's liking; browser applications are being accepted if they have been signed with that special VMP certificate, and this fact limits the selection to ones offered by the major vendors, ONLY (Google Chrome/Mozilla Firefox and a few Chromium variants) ... Supermium hasn't been granted VMP compliance (being a one-man, open-source, project) and even if its author (win32) applied for such, it could well take several years for this to materialise, if at all ... In addition to VMP, you said you manually edited the DLL: This fact alone changes the CDM's hash value/invalidates its file signature (which is SHA-2, BTW, incompatible with XP) and when the CDM identifies itself to the WV lic servers (yes, it does send its hash inside that obfuscated payload I mentioned earlier), it "screams": "I've been tampered with, just ignore me", thus no decryption keys are delivered to it ... FYI, some Supermium issues relating to its DRM (Widevine) support: https://github.com/win32ss/supermium/issues/127 https://github.com/win32ss/supermium/issues/169 https://github.com/win32ss/supermium/issues/242 FWIW, Widevine related documentation used to be publicly accessible until a few years ago, when evil Google decided to put it behind corporate gmail accounts, for media-enterpises members only, who also have to sign strict NDAs ... At this point in time, it seems DRM-savvy private individuals are to be found only inside private discord servers, no more open to "outsiders"; I used to be part of such a server back in the day, but got kicked-out because I wasn't "active enough" (at least according to the server's owner ) ...
  24. Fortunately, that one has been salvaged by crx4chrome : https://www.crx4chrome.com/crx/299038/
  25. ... With respect , you did not make an effort, it seems, to follow what I have already posted in a previous post ; whether a PDF on-line URI will generate a "Save As" file download prompt (case 1 in your previous post) or the PDF file will be auto-downloaded in the background and rendered+displayed inside the browser's Native PDF Viewer (case 2 in your previous post) is something beyond the user's (initial) control, in fact it's a server-side configuration: the PDF file on the hosting server has been configured with a content-disposition value, by the server admins... In case 2, the value is "inline"; this (alongside a suitable Content-Type header) instructs the browser to handle the PDF file "in-line", i.e display it inside a tab via the native viewer (or via a PDF reader plugin, where applicable); in case 1, the value is "attachment"; this instructs the browser to simply "download" the PDF file to disk, for storage. I have already mentioned an extension in my previous post which changes the "attachment" Content-Disposition value to "inline", but the problem with such an extension is it's not specific to PDF files; other types of files you may want to download to disk (e.g. images, audio, video, etc.) will attempt to be displayed directly in the browser (if the browser is able to render them natively); that's why I said I only enable that extension at will...
×
×
  • Create New...