Chrome 78 Canary blocks injection to Chrome renderer processes

[zheung]

According Chromium Issue #990640 and Chromium Review #1629607, Chrome 78 Canary is starting to block injection to Chrome renderer processes. Mactype Beta 6 can not work correctly since 78.0.3874.0. Currently, we can use --disable-features=RendererCodeIntegrity to avoid block

I think I should bring this messsage to you, no matter that it would be fixed or not.

Here is some screenshots. It's more obvious and different in Chinese. Please take two screenshots in image viewer, and switch sometimes: Without any argument. work incorrectly and cannot enable in Process Manager:

Work fine with `--disable-features=RendererCodeIntegrity:

[hamjin]

The problem of my new method is that it doesn’t only allow Mactype to be injected into the chrome. Like disabling code integrity check, all the other tools can be injected.

I think the CIG is not suitable for Chrome because the browser's dynamic libraries like chrone_elf.dll is in the whitelist, so it doesn't need Microsoft's certificate. We can make an new dynamic library which only add an rule to whitelist and pass other functions to the original chrome_elf.dll

[snowie2000]

As you can see, Chrome was started without any command-line parameters and I didn't set any policy to it, yet it loads MacType correctly in Windows 10.

I tried several other ways today and they are either too hard to implement or have potential risks that I'd rather not put them into the final release.

I know I can just hook SetProcessMitigationPolicy and stop some mitigations from applying, but I'd prefer to treat it as our last hope.

[snowie2000]

Update:

I figured out a perfect way to load MacType into the latest Chrome in Windows 10, and the method also worked for Microsoft Edge (chromium-based) with very little compromise on security.

[kcohar]

Wow that's amazing, props! Are we gonna see this in master?

On Tuesday, April 28, 2020, snowie2000 notifications@github.com wrote:

Update:

I figured a perfect way to load MacType into the latest Chrome in Windows 10, and the method also worked for Microsoft Edge (chromium-based). [image: edge] https://user-images.githubusercontent.com/11767189/80449416-af9ed600-8951-11ea-9e3c-cfefda6e4484.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/snowie2000/mactype/issues/597#issuecomment-620384668, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALJKQE2O46RKJTX5BLTG5J3ROZQO5ANCNFSM4IK5PPGA .

[Alex-Hou]

awesome

[sky31even]

update: this version of chromium Edge (83.0.478.54 ) still works under "--disable-features=RendererCodeIntegrity"

[sky31even]

Update:

I figured out a perfect way to load MacType into the latest Chrome in Windows 10, and the method also worked for Microsoft Edge (chromium-based) with very little compromise on security.

looking forward it lollllll

[Lucire]

Hi there, for a while I’ve used the solution of the command line "C:\Program Files\Vivaldi\Application\vivaldi.exe" --disable-features=RendererCodeIntegrity and forcing Windows 8 compatibility in order for MacType to work inside Vivaldi. However, after Windows updates KB5000842 and KB4589212 were installed, this no longer seems to work.

I’ve never been able to do the registry method outlined above as the keys simply are not there for Vivaldi. Under HKLM\Software\Policies I only have Adobe and Microsoft, and no Google. Is there somewhere else I can add the registry key(s)?

Edit: I have updated MacType to the latest version. Also one of my shortcuts was missing the --disable-features=RendererCodeIntegrity; I’ve now added --disable-lcd-text as well. This appears to have solved the problem.

[kcohar]

create a key called HKLM\SOFTWARE\Policies\Vivaldi, and put a DWORD in there called RendererCodeIntegrityEnabled, with a value of "0"

once the next version of mactype comes out we won't have to do this anymore

On Sat, Apr 10, 2021 at 1:17 AM Lucire @.***> wrote:

Hi there, for a while I’ve used the solution of the command line "C:\Program Files\Vivaldi\Application\vivaldi.exe" --disable-features=RendererCodeIntegrity and forcing Windows 8 compatibility in order for MacType to work inside Vivaldi. However, after Windows updates KB5000842 and KB4589212 were installed, this no longer seems to work.

I’ve never been able to do the registry method outlined above as the keys simply are not there for Vivaldi. Under HKLM\Software\Policies I only have Adobe and Microsoft, and no Google. Is there somewhere else I can add the registry key(s)?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/snowie2000/mactype/issues/597#issuecomment-817021425, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALJKQE6WBWHFFW3ZHZOLYKDTH6DHVANCNFSM4IK5PPGA .