README: Ingot will not work on Chrome 106 or after

[Nebelung-Dev]

Don't make an issue for this I can not fix it, sorry :(

Also developer mode just lets you see the extension id and version not sideload extensions

[Crushstar]

What on chrome OS build 106 is stopping ingot. I'm wondering if there is a way around it?

[RedGuyVR]

do you know why it stopped working?

[n9vo]

I used this for a couple days then it got patched with the new chrome version, is there any alternative to this? anything that has the same effect, just disabling extensions.

[bohrium2b]

It seems that a Content Security Policy is blocking this from working.

[n9vo]

It seems that a Content Security Policy is blocking this from working.

Maybe if the script was actually within the bookmarklet instead of fetching it from that site it would work?

[sylvxa]

The loophole LTBEEF and Ingot used was patched in Chrome 106, it is not a CSP issue or anything and unfortunately, unless there is another "exploit" found they won't work for a while.

[DodoSeal]

I'm on version 102. My friend is also on version 102. Our chromebooks have no differences in policies, versions, model. Somehow this works on his device and nobody else's. If I log into my account on his it still works.

[DodoSeal]

whelp, i have a recommendation. create something of a policy destroyer
…

That's not possible...

[raventhecrabraver]

whelp, i have a recommendation. create something of a policy destroyer
…

That's not possible...

dude dont say its not possible you dont know that for sure.

[DodoSeal]

whelp, i have a recommendation. create something of a policy destroyer

…

That's not possible...

dude dont say its not possible you dont know that for sure.

Are you the one with the experience here. Just think, Google is a billion dollar company. They have extremely smart engineers.

[Aka-but-nice]

Here's what you do, make a bookmark with chrome://restart in it and name it something like Restart then make another bookmark with chrome://signOut the o has to be capitalized then click the signOut button first and press the blue button then press the restart and wait for it to load up, and your good!

[miiuzu]

Here's what you do, make a bookmark with chrome://restart in it and name it something like Restart then make another bookmark with chrome://signOut the o has to be capitalized then click the signOut button first and press the blue button then press the restart and wait for it to load up, and your good!

Hey! so I've tried that it apparently doesn't work at all. what is the blue button?

[Antgod4]

There is a bypass for iboss https://spacesaver.github.io/Ingot-for-iBoss maybe you could add that to your bypassing list the repository is https://github.com/SpaceSaver/Ingot-for-iBoss.

[miiuzu]

thanks!!

[Aka-but-nice]

It seems that a Content Security Policy is blocking this from working.

Literally csp shit, you can't just load scripts, fetch doesn't work either.

[Aka-but-nice]

whelp, i have a recommendation. create something of a policy destroyer

…

That's not possible...

dude dont say its not possible you dont know that for sure.

Are you the one with the experience here. Just think, Google is a billion dollar company. They have extremely smart engineers.

What I'm saying, no IQ, you can't just edit policies, bro is straight up stupid.

[Aka-but-nice]

The loophole LTBEEF and Ingot used was patched in Chrome 106, it is not a CSP issue or anything and unfortunately, unless there is another "exploit" found they won't work for a while.

Nobody said it was about CSPs, it was a Chrome mistake involving the API management, this one was the only API, that can fuck up extensions how it did with ltbeef, there are many more exploits, just you can't delete
extensions without management, it is intended behavior, without management you wouldn't be able to delete extensions and more, Chrome needed the management API, Chrome didn't expect people would use that API, for bypassing.

[Aka-but-nice]

do you know why it stopped working?

Yes, when Chrome added the management API, they didn't specify which extensions the webstore could disable, this also included admin ones. When Chrome realized their error, they made it so the webstore couldn't just disable an admin extensions, and this will most likely stay as there is no problems with this, you're not supposed to be able to delete admin extensions in the first place.