This sets up a local proxy redirecting .bit requests to the proper ip addresses and also proxying legacy domains.
It's a quick modification of https://github.com/allfro/pymiproxy
http://blockchained.com/stuff/proxy.py_
http://blockchained.com/stuff/namerpc.py_
Run proxy.py and set your browser proxy settings to 127.0.0.1 port 8083
Needs NMControl (and the Namecoin client) running to work.
It will not yet work with SSL but it should be possible.
Caching for legacy domains still needs a lot of work but sometimes it's quite fast actually.
Experimental Local Proxy Resolving
Forum rules
Warning !
Avoid using binary softwares from untrusted users.
Prefer compiling it yourself and verify sources.
Warning !
Avoid using binary softwares from untrusted users.
Prefer compiling it yourself and verify sources.
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: Experimental Local Proxy Resolving
I'm not sure I understand what advantage this has over FreeSpeechMe's proxy?phelix wrote:This sets up a local proxy redirecting .bit requests to the proper ip addresses and also proxying legacy domains.
It's a quick modification of https://github.com/allfro/pymiproxy
http://blockchained.com/stuff/proxy.py
http://blockchained.com/stuff/namerpc.py
Run proxy.py and set your browser proxy settings to 127.0.0.1 port 8083
Needs NMControl (and the Namecoin client) running to work.
It will not yet work with SSL but it should be possible.
Caching for legacy domains still needs a lot of work but sometimes it's quite fast actually.
Re: Experimental Local Proxy Resolving
tbh I have only a vague idea how FreeSpeechMe works... is this any similar to it?biolizard89 wrote:I'm not sure I understand what advantage this has over FreeSpeechMe's proxy?phelix wrote:This sets up a local proxy redirecting .bit requests to the proper ip addresses and also proxying legacy domains.
It's a quick modification of https://github.com/allfro/pymiproxy
http://blockchained.com/stuff/proxy.py
http://blockchained.com/stuff/namerpc.py
Run proxy.py and set your browser proxy settings to 127.0.0.1 port 8083
Needs NMControl (and the Namecoin client) running to work.
It will not yet work with SSL but it should be possible.
Caching for legacy domains still needs a lot of work but sometimes it's quite fast actually.
I just happened to run across pymiproxy and played with it a little. It was fun and cool how little code was necessary to make .bit domains work (without TLS that is).
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: Experimental Local Proxy Resolving
Yep, quite similar to FreeSpeechMe. FreeSpeechMe uses the proxy code in Convergence, and adds a little bit of code to interface with NMControl. The main difference is that Convergence's proxy has built-in support for doing a MITM on TLS and checking the resulting certs, which is useful for us.phelix wrote:tbh I have only a vague idea how FreeSpeechMe works... is this any similar to it?biolizard89 wrote:I'm not sure I understand what advantage this has over FreeSpeechMe's proxy?phelix wrote:This sets up a local proxy redirecting .bit requests to the proper ip addresses and also proxying legacy domains.
It's a quick modification of https://github.com/allfro/pymiproxy
http://blockchained.com/stuff/proxy.py
http://blockchained.com/stuff/namerpc.py
Run proxy.py and set your browser proxy settings to 127.0.0.1 port 8083
Needs NMControl (and the Namecoin client) running to work.
It will not yet work with SSL but it should be possible.
Caching for legacy domains still needs a lot of work but sometimes it's quite fast actually.
I just happened to run across pymiproxy and played with it a little. It was fun and cool how little code was necessary to make .bit domains work (without TLS that is).
Re: Experimental Local Proxy Resolving
I should really take a closer look at FreeSpeechMe. This proxy has some kind of MITM TLS, too, but I did not yet get it to work.biolizard89 wrote:Yep, quite similar to FreeSpeechMe. FreeSpeechMe uses the proxy code in Convergence, and adds a little bit of code to interface with NMControl. The main difference is that Convergence's proxy has built-in support for doing a MITM on TLS and checking the resulting certs, which is useful for us.phelix wrote:tbh I have only a vague idea how FreeSpeechMe works... is this any similar to it?biolizard89 wrote:
I'm not sure I understand what advantage this has over FreeSpeechMe's proxy?
I just happened to run across pymiproxy and played with it a little. It was fun and cool how little code was necessary to make .bit domains work (without TLS that is).
btw: I renamed the files so that they can actually be downloaded.
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: Experimental Local Proxy Resolving
Pull requests for FreeSpeechMe are always appreciated.phelix wrote:I should really take a closer look at FreeSpeechMe. This proxy has some kind of MITM TLS, too, but I did not yet get it to work.biolizard89 wrote:Yep, quite similar to FreeSpeechMe. FreeSpeechMe uses the proxy code in Convergence, and adds a little bit of code to interface with NMControl. The main difference is that Convergence's proxy has built-in support for doing a MITM on TLS and checking the resulting certs, which is useful for us.phelix wrote:tbh I have only a vague idea how FreeSpeechMe works... is this any similar to it?
I just happened to run across pymiproxy and played with it a little. It was fun and cool how little code was necessary to make .bit domains work (without TLS that is).
btw: I renamed the files so that they can actually be downloaded.