mirror of
https://github.com/tlsnotary/tlsn-extension.git
synced 2026-01-09 21:18:02 -05:00
53ba6f69b8
* wip: testing extism host function * wip * wip * wip: adding ui for plugin * feat: add cache for headers and cookies by host * feat: add plugin stores * feat: add a plugin and render plugin list * feat: add plugin config db * feat: add basic plugin steps ui * feat: add completion status to steps ui * fix: refactor twitter profile plugin * fix: refactor steps execution * fix: testing plugin * Added README to plugins folder * feat: fix twitter profile plugin * improved README: document how to run the twitter plugin example * remove ddos * WIP: Reddit plugin * fix: steps circular reference * feat: open popup * Reddit plugin (result too big) * feat: add view proof * chore: add plugins to eslint ignore * fix: twitter plugin * fix: remove logs * feat: add permission for approved request, notary, and proxy url in plugin --------- Co-authored-by: Hendrik Eeckhaut <hendrik@eeckhaut.org>
Chrome Extension (MV3) for TLSNotary
Important
⚠️ When running the extension against a notary server, please ensure that the server's version is the same as the version of this extension
License
This repository is licensed under either of
at your option.
Installing and Running
Procedures:
- Check if your Node.js version is >= 18.
- Clone this repository.
- Run
npm installto install the dependencies. - Run
npm run dev - Load your extension on Chrome following:
- Access
chrome://extensions/ - Check
Developer mode - Click on
Load unpacked extension - Select the
buildfolder.
- Access
- Happy hacking.
Building Websockify Docker Image
$ git clone https://github.com/novnc/websockify && cd websockify
$ ./docker/build.sh
$ docker run -it --rm -p 55688:80 novnc/websockify 80 api.twitter.com:443
Running Websockify Docker Image
$ cd tlsn-extension
$ docker run -it --rm -p 55688:80 novnc/websockify 80 api.twitter.com:443
Packing
After the development of your extension run the command
$ NODE_ENV=production npm run build
Now, the content of build folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look at the official guide to more infos about publishing.