uniaidevs / ingot

A bookmarklet to disable extensions based on LTBEEF with an interface based on the chrome extension page

Patched!

Ingot has been patched on Chrome 106 or after. This will not be updated.

Ingot

A bookmarklet to disable extensions based on LTBEEF with an interface based on the chrome extension page

Installation

For easy setup go the the website at https://fognetwork.github.io/Ingot

1. Show your bookmarks bar with ctrl + shift + b

2. Right click on the bar and choose Add Page

3. Set the name to Ingot and the URL to the code below or here

javascript:(function () {var a = document.createElement('script');a.src = 'https://cdn.jsdelivr.net/gh/FogNetwork/Ingot/ingot.min.js';document.body.appendChild(a);}())

Screenshots

ingot's Issues

Task Tile

What - description of what you me to do
Example: Hey @autopilot implement a way for users to activate the program from the browser, instead of a bookmarklet. Add this as an additional feature, and add as many programs and src as needed. It should be a self-hostable web interface.

Why - explain why this is important
Example: I want to allow users to use the javascript code from a website, in case javascript bookmarklets are blocked on their device. This insures the that web equality is included.

Welcome to Code Autopilot

Hi @uniAIDevs! 👋

I'm Code Autopilot 🤖

Want me to help you solve a bug, implement a new feature, or answer questions? 👉 Open your first task here 👈

Task Tile

What - description of what you me to do
Hey @autopilot Make changes to the front end and the back end of the application so that in case chrome.google.com/webstorex is blocked, the program can access chromewebstore.google.com and chrome://extensions/, or force access to webstorex.
Force access requirements:
To force access to blocked URLs via Chrome organization configuration, you typically need to utilize Chrome's policies for managing access to websites. This can be achieved through the use of Chrome's URLBlacklist and URLAllowlist policies. Here's how you can set this up:
Access Chrome Policies: First, ensure you have administrative access to the Chrome browser settings through your organization's management console.
URLBlacklist Policy: This policy allows you to block specific URLs. You can add the URLs you want to block by specifying them in this policy. For example, if you want to block "example.com," you would add it to the URLBlacklist.
URLAllowlist Policy: Conversely, this policy allows you to specify URLs that should always be accessible, even if they are on the blacklist. Add the URLs you want to allow access to in this policy.
Enforcement: Once you have set up the URLBlacklist and URLAllowlist policies with the desired URLs, enforce these policies one the singular device.
Force admin access:
consider implementing role-based access control (RBAC) or privilege escalation mechanisms. Here's a general approach to achieve this:
Role-Based Access Control (RBAC):
Define a custom role that has the necessary permissions and privileges similar to those of an admin but without the explicit title.
Assign this custom role to the specific account that needs elevated access.
Ensure that the permissions granted align with the responsibilities and tasks that the account needs to perform.
Privilege Escalation:
Implement a privilege escalation mechanism that allows the account to temporarily elevate its privileges when required.
This can be achieved through a secure authentication process or approval workflow where the user can request and obtain elevated access for specific tasks.

Why - explain why this is important
I want to allow all users, no matter their tech stack, to be able to use my software