j7n Posted December 8, 2024 Posted December 8, 2024 Would the result of fixing Chrome be much different than Supermium, which has already been fixed? There is not much difference between vairous Chrome-variants. 1
Jaguarek62 Posted February 9 Author Posted February 9 On 12/8/2024 at 11:47 AM, j7n said: Would the result of fixing Chrome be much different than Supermium, which has already been fixed? There is not much difference between vairous Chrome-variants. Actually yeah, I have been forced to use windows 11 to watch netflix etc.. DRM does not work under supermium or firefox 1
D.Draker Posted February 10 Posted February 10 On 2/9/2025 at 3:20 PM, Jaguarek62 said: I have been forced to use windows 11 to watch netflix etc.. It already does not work under Win10? 2
D.Draker Posted February 10 Posted February 10 On 12/8/2024 at 6:47 AM, j7n said: Would the result of fixing Chrome be much different than Supermium, which has already been fixed? There is not much difference between vairous Chrome-variants. One would need to write a dedicated Kernel for that, otherwise it's too much time to fix those frequently released versions. 3
D.Draker Posted February 10 Posted February 10 On 12/8/2024 at 6:47 AM, j7n said: There is not much difference between vairous Chrome-variants. You could probably try Opera (based on Chrome, some newer versions still work on 8.1), but it's a heavy and bloated spyware. 3
mjd79 Posted February 10 Posted February 10 (edited) Opera will probably work up to around version 110 (Chromium 125?) with DWrite.dll from Windows 10, replacing DiscardVirtualMemory with VirtualAlloc (or what I also recently discovered, DiscardVirtualMemory is in 8.1 in kernelbase.dll, so you can add by ExportTableTester redirection to this function in kernel32.dll exports and using it for opera_browser.dll e.g. as kernel33.dll) and with --no-sandbox. This is completely pointless due to depriving the browser of security, but for viewing DRM content you can do so. In my case, interestingly enough, DRM works on 8.1 after copying the widvine from Firefox to any compatible browser on Chromium. On 12/6/2024 at 11:38 PM, Jaguarek62 said: I know that we have supermium browser and that it works flawlessly, I myself use it on daily basis, but I was bored the other day and discovered, that the newest chrome works on Windows "10" 9888, so how hard is it really to fix it for 8.1? Does it work without --no-sandbox? If so, the differences are unfortunately much greater than DWrite and DiscardVirtualMemory. The biggest problem of Windows versions lower than 10 is the Set/GetProcessMigitationPolicy functions. 8.0 and 8.1 have them, but their implentation is insufficient for Chromium. Edited February 10 by mjd79
D.Draker Posted February 10 Posted February 10 11 hours ago, mjd79 said: Chromium 125 Yes, right, it's the highest I could get working on Vista, do you know what prevents 126 from starting. even on Win 8? 3
Jaguarek62 Posted February 10 Author Posted February 10 2 hours ago, mjd79 said: Opera will probably work up to around version 110 (Chromium 125?) with DWrite.dll from Windows 10, replacing DiscardVirtualMemory with VirtualAlloc (or what I also recently discovered, DiscardVirtualMemory is in 8.1 in kernelbase.dll, so you can add by ExportTableTester redirection to this function in kernel32.dll exports and using it for opera_browser.dll e.g. as kernel33.dll) and with --no-sandbox. This is completely pointless due to depriving the browser of security, but for viewing DRM content you can do so. In my case, interestingly enough, DRM works on 8.1 after copying the widvine from Firefox to any compatible browser on Chromium. Does it work without --no-sandbox? If so, the differences are unfortunately much greater than DWrite and DiscardVirtualMemory. The biggest problem of Windows versions lower than 10 is the Set/GetProcessMigitationPolicy functions. 8.0 and 8.1 have them, but their implentation is insufficient for Chromium. this is really interesting.. and yes on windows "10" build 9888 it works without --no-sandbox flag, just needs the virtualalloc hack. will definitely try the widevine method you mentioned. really cool.
mjd79 Posted February 10 Posted February 10 (edited) 2 hours ago, D.Draker said: Yes, right, it's the highest I could get working on Vista, do you know what prevents 126 from starting. even on Win 8? The problem starts with version 127, it looks like chrome.dll is not able to create any process. because after substituting chrome.dll along with the kernel32 wrapper (and nothing more) by cracker who you probably known, D.Draker, from github, the browser starts up. Unfortunately the information that x64dbg gives me at this stage of my knowledge doesn't give me much. Edited February 10 by mjd79
D.Draker Posted February 10 Posted February 10 11 hours ago, mjd79 said: The problem starts with version 127, it looks like chrome.dll is not able to create any process. because after substituting chrome.dll along with the kernel32 wrapper (and nothing more) by cracker who you probably known, D.Draker, from github, the browser starts up. Unfortunately the information that x64dbg gives me at this stage of my knowledge doesn't give me much. A hint, what happens if you scan for delay-load dependencies? 4
Klemper Posted February 12 Posted February 12 On 2/10/2025 at 12:16 PM, mjd79 said: Opera will probably work up to around version 110 (Chromium 125?) with DWrite.dll from Windows 10, replacing DiscardVirtualMemory with VirtualAlloc (or what I also recently discovered, DiscardVirtualMemory is in 8.1 in kernelbase.dll, so you can add by ExportTableTester redirection to this function in kernel32.dll exports and using it for opera_browser.dll e.g. as kernel33.dll) and with --no-sandbox. This is completely pointless due to depriving the browser of security, but for viewing DRM content you can do so. In my case, interestingly enough, DRM works on 8.1 after copying the widvine from Firefox to any compatible browser on Chromium. Does it work without --no-sandbox? If so, the differences are unfortunately much greater than DWrite and DiscardVirtualMemory. The biggest problem of Windows versions lower than 10 is the Set/GetProcessMigitationPolicy functions. 8.0 and 8.1 have them, but their implentation is insufficient for Chromium. I'm on 8.1, too. Could you please share this programme?
mjd79 Posted February 12 Posted February 12 1 hour ago, Klemper said: I'm on 8.1, too. Could you please share this programme? https://ximonite.com/misc/tools/ExportTableTester.exe 2
D.Draker Posted February 13 Posted February 13 On 2/12/2025 at 5:50 AM, mjd79 said: https://ximonite.com/misc/tools/ExportTableTester.exe They write the link is infected https://www.virustotal.com/gui/file/ed00a77d14531ca7668b6a1205c79630147221b731c29a41ceccc33d65ba1576 ANALYZER VERDICT LERT VirusTotal malicious 4
mjd79 Posted February 13 Posted February 13 Ximonite hosted the win32ss site for a long time, so I thought it was safe....
D.Draker Posted February 13 Posted February 13 10 hours ago, mjd79 said: Ximonite hosted the win32ss site for a long time, so I thought it was safe.... Win32, yeah, I know him, but the other one, I don't. Could it be a false alarm? 4
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now