https://github.com/tabcat/limo-hijacker
client-side verifying ENS+IPFS resolver firefox extension
https://github.com/tabcat/limo-hijacker
Last synced: about 1 year ago
JSON representation
client-side verifying ENS+IPFS resolver firefox extension
- Host: GitHub
- URL: https://github.com/tabcat/limo-hijacker
- Owner: tabcat
- License: unlicense
- Created: 2024-05-29T12:51:02.000Z (about 2 years ago)
- Default Branch: master
- Last Pushed: 2024-06-04T18:00:21.000Z (about 2 years ago)
- Last Synced: 2024-10-12T12:21:28.419Z (over 1 year ago)
- Language: JavaScript
- Homepage:
- Size: 248 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# limo hijacker 🕴️
client-side verifying ENS/IPFS resolver firefox extension
## Disclaimer
This project is more of an **art project** and **learning process** for myself. I recommend using eth.limo without this extension normally.
⚠️ **Only working in Firefox as it relies on [webRequest.filterResponseData](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/filterResponseData).** ⚠️
## How does it work?
The extension:
1. Intercepts requests to eth.limo
2. Resolves the contenthash field of the .eth domain being visited via [@ensdomains/ensjs](https://github.com/ensdomains/ensjs-v3).
3. Replaces data of responses from eth.limo with response data from a trustless ipfs gateway using [@helia/verified-fetch](https://github.com/ipfs/helia-verified-fetch/tree/main).
## The problem
There are a few different ways to view IPFS sites resolved through ENS:
| | client verified | unique origin (per domain) | low friction | aesthetic address |
|----|----------|----------|---|---|
| IPFS Gateway (e.g. dweb.link) |❌|❌|✅|❌|
| ENS Gateway (e.g. eth.limo) |❌|✅|✅|✅|
| eth.local (local DNS/ENS resolver) |✅|✅|❌|✅|
| limo-hijacker |☑️|✅|✅|✅|
| ens+ipfs:// protocol handler (hypothetical) |⭐|⭐|⭐|⭐|
☑️: IPNS/IPFS resolutions are verified locally on the client, however the ENS resolutions are not.
None existing are perfect.
The endgame is either extensions being able to handle ens+ipfs:// links or built in browser support.
This will allow resolving web content without needing to interact with any trusted third-parties or systems that use them.
## Prerequisits
[`pnpm`](https://pnpm.io/)
[`web-ext`](https://www.npmjs.com/package/web-ext) (installed globally)
## Build
```bash
pnpm install
pnpm build
```
## Dev server
```bash
web-ext run --source-dir . --devtools
```
Sometimes when visiting a site the extension is able to load the content from ipfs but the site is unable to load the content from the extension (from the filtered http response).
Haven't investigated this bug much and it could interfere with trying to visit .eth.limo sites.