3 ms·
I am working on a simple system of that sort. I'm not sure I trust myself using crypto, so consider it a proof-of-concept. The system provides key-based domains
by JeremyBanks 15y ago
I am working on a simple system of that sort. I'm not sure I trust myself using crypto, so consider it a proof-of-concept. The system provides key-based domains, and allows sites to update them automatically over http or distribute them through websites.
This system can also work alongside ordinary DNS. When it is running, any domain you visit can provide a record and a public key. If the DNS record changes in future but the signed record isn't updated to match, the user continues to use the signed record.
The first version is probably going to be an HTTP proxy, but I'd like to make it a browser plugin if I can figure out how (it looked more difficult than I expected).
Example Scenario:
- I'm running wikileaks.com. I generate a key and upload a signed record with the IP.
- Clients visit wikileaks.com and automatically download the record and associate the key with the domain.
- Government sizes wikileaks.com domain.
- Clients are redirected to wikileaks.com-via-a-long-generated-domain...
- Clients are able to visit the site without interruption.
- I now register wikileaks.ch, and I use my key to sign an updated record with the new domain.
- Clients check wikileaks.ch and associate it with the key, then redirect any requests to wikileaks.com or the-long-generated-domain... to to wikileaks.ch.
I will provide a link when it's a little more complete.