A local namecoin proxy to implement most of the draft spec
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.
Re: A local namecoin proxy to implement most of the draft sp
Il give this a shot when im at home. looks a bit complicated but il try see if i can get it working
-
- Posts: 172
- Joined: Wed Jun 15, 2011 12:46 pm
- os: linux
Re: A local namecoin proxy to implement most of the draft sp
Finally found the time to install it and to configure bind to use it. Was no hassle and seems to work so far. Do we have a list of known working .bit addresses? Most of the few domains I tested are not properly configured
Access .bit domains with Firefox in 4 easy steps: https://masterpool.eu/proxy
MasterPool Namecoin Mining Pool
MasterPool Namecoin Mining Pool
-
- Posts: 1
- Joined: Wed Nov 16, 2011 11:49 pm
- os: linux
Re: A local namecoin proxy to implement most of the draft sp
I'm really interested in this project. I love python, but I think node is also really cool and have played a little with it.
At first I started to build the project with node v0.6, but soon realized that nmcsocks hasn't been updated to use that version yet.
Then I tried to get it compiled with v0.4, but I am still having issues. More specifically, I cannot get your dcrypt to build (npm install dcrypt complains similarly).
I am running Ubuntu 10.04.3 (the current stable with everything up to date) and I have both libssl-dev and libcrypto++-dev
Whats weird is I that I am pretty sure I got further building dcrypt when I was using node 0.6 and dcrypt doesn't even support 0.5, but now I have that source deleted and don't have those log files.
I tried building without ecdsa just to see, but that failed very similary
I posted a few of my fixes as pull requests on github. But am out of ideas.
======
If I run a BIND9 server and have it forward requests to nmcsocks, is it "safe" to publish the DNS server's IP publicly? I would like to make it easier for people to resolve .bit names (including names that point to tor or i2p). I know a lot of work has gone into BIND (like running the app in a jail) to reduce the security risks when maliciously crafted requests are made. Are there any attacks that might break nmcsocks in some horrific way and then compromise my server? I'm assuming not, but just wanted to know the possible problems of running a public DNS with a very beta proxy to another DNS system.
At first I started to build the project with node v0.6, but soon realized that nmcsocks hasn't been updated to use that version yet.
Then I tried to get it compiled with v0.4, but I am still having issues. More specifically, I cannot get your dcrypt to build (npm install dcrypt complains similarly).
Code: Select all
[bwstitt@server /home/bwstitt/src/nmcsocks/node_modules/dcrypt]$ node-waf configure build
Checking for program g++ or c++ : /usr/lib/ccache/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for node path : not found
Checking for node prefix : ok /usr/local
Checking for header openssl/ecdsa.h : no such environment: default
Traceback (most recent call last):
File "/usr/local/bin/node-waf", line 16, in <module>
Scripting.prepare(t, os.getcwd(), VERSION, wafdir)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 145, in prepare
prepare_impl(t, cwd, ver, wafdir)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 135, in prepare_impl
main()
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 188, in main
fun(ctx)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 241, in configure
conf.sub_config([''])
File "/usr/local/bin/../lib/node/wafadmin/Configure.py", line 221, in sub_config
self.recurse(k, name='configure')
File "/usr/local/bin/../lib/node/wafadmin/Utils.py", line 634, in recurse
f(self)
File "/home/bwstitt/src/nmcsocks/node_modules/dcrypt/wscript", line 22, in configure
if Options.options.without_ecdsa or not conf.check(header_name='openssl/ecdsa.h', compile_mode='cxx'):
File "/usr/local/bin/../lib/node/wafadmin/Tools/config_c.py", line 444, in check
ret = self.run_c_code(*k, **kw)
File "/usr/local/bin/../lib/node/wafadmin/Tools/config_c.py", line 521, in run_c_code
o = bld(features=kw['features'], source=test_f_name, target='testprog')
File "/usr/local/bin/../lib/node/wafadmin/Build.py", line 343, in __call__
return TaskGen.task_gen(*k, **kw)
File "/usr/local/bin/../lib/node/wafadmin/TaskGen.py", line 118, in __init__
self.env = self.bld.env.copy()
AttributeError: 'NoneType' object has no attribute 'copy'
Whats weird is I that I am pretty sure I got further building dcrypt when I was using node 0.6 and dcrypt doesn't even support 0.5, but now I have that source deleted and don't have those log files.
I tried building without ecdsa just to see, but that failed very similary
Code: Select all
[bwstitt@minecraft dcrypt]$ node-waf clean || true; node-waf configure build --without-ecdsa=true
Nothing to clean (project not configured)
Checking for program g++ or c++ : /usr/lib/ccache/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for node path : not found
Checking for node prefix : ok /usr/local
Configuring Dcrypt to skip bindings on ECDSA
'configure' finished successfully (0.064s)
Waf: Entering directory `/home/bwstitt/src/nmcsocks/node_modules/dcrypt/build'
no such environment: default
Traceback (most recent call last):
File "/usr/local/bin/node-waf", line 16, in <module>
Scripting.prepare(t, os.getcwd(), VERSION, wafdir)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 145, in prepare
prepare_impl(t, cwd, ver, wafdir)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 135, in prepare_impl
main()
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 188, in main
fun(ctx)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 386, in build
return build_impl(bld)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 399, in build_impl
bld.add_subdirs([os.path.split(Utils.g_module.root_path)[0]])
File "/usr/local/bin/../lib/node/wafadmin/Build.py", line 981, in add_subdirs
self.recurse(dirs, 'build')
File "/usr/local/bin/../lib/node/wafadmin/Utils.py", line 634, in recurse
f(self)
File "/home/bwstitt/src/nmcsocks/node_modules/dcrypt/wscript", line 28, in build
obj = bld.new_task_gen("cxx", "shlib", "node_addon")
File "/usr/local/bin/../lib/node/wafadmin/Build.py", line 335, in new_task_gen
ret = cls(*k, **kw)
File "/usr/local/bin/../lib/node/wafadmin/Tools/ccroot.py", line 162, in __init__
TaskGen.task_gen.__init__(self, *k, **kw)
File "/usr/local/bin/../lib/node/wafadmin/TaskGen.py", line 118, in __init__
self.env = self.bld.env.copy()
AttributeError: 'NoneType' object has no attribute 'copy'
======
If I run a BIND9 server and have it forward requests to nmcsocks, is it "safe" to publish the DNS server's IP publicly? I would like to make it easier for people to resolve .bit names (including names that point to tor or i2p). I know a lot of work has gone into BIND (like running the app in a jail) to reduce the security risks when maliciously crafted requests are made. Are there any attacks that might break nmcsocks in some horrific way and then compromise my server? I'm assuming not, but just wanted to know the possible problems of running a public DNS with a very beta proxy to another DNS system.
Re: A local namecoin proxy to implement most of the draft sp
Is there any command line to test if nmcsocks is working properly? I have nmcsocks (as part of the BamecoinBundle) running. It's listening on port 9055:
but I can't get the FoxyProxy browser add-on to work with it. I'd like to know if it's FoxyProxy or nmcsocks that's misbehaving.
Code: Select all
rune@runescomp:~/Desktop/NamecoinBundleLinux$ netstat -na|grep 9055
tcp 0 0 127.0.0.1:9055 0.0.0.0:* LISTEN
Re: A local namecoin proxy to implement most of the draft sp
nmcsocks has a bug with some .bit domains (some of those configured with the "ns/dns" keyword).
Could you test with "http://ns.bit" ? (configured with the "ip" keyword)
If it works, it means you hit the bug and it affects the other domains you tested.
Could you test with "http://ns.bit" ? (configured with the "ip" keyword)
If it works, it means you hit the bug and it affects the other domains you tested.
NamecoinID: id/khal
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T
Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T
Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent
Re: A local namecoin proxy to implement most of the draft sp
It seems like it is the Chrome FoxyProxy plugin that is buggy. I just tried with the same plugin for Firefox, and it works perfectly. All .bit domains I've tried so far work.
EDIT: I just tried Chrome's built-in proxy configuration, it works as well. So it is FoxyProxy for Chrome that is the culprit. Non-.bit domains work as well, it seems, with Chrome's own proxy configuration, so it seems FoxyProxy isn't needed after all (at least for Chrome).
EDIT: I just tried Chrome's built-in proxy configuration, it works as well. So it is FoxyProxy for Chrome that is the culprit. Non-.bit domains work as well, it seems, with Chrome's own proxy configuration, so it seems FoxyProxy isn't needed after all (at least for Chrome).
Re: A local namecoin proxy to implement most of the draft sp
runeks: good stuff.runeks wrote:It seems like it is the Chrome FoxyProxy plugin that is buggy. I just tried with the same plugin for Firefox, and it works perfectly. All .bit domains I've tried so far work.
EDIT: I just tried Chrome's built-in proxy configuration, it works as well. So it is FoxyProxy for Chrome that is the culprit. Non-.bit domains work as well, it seems, with Chrome's own proxy configuration, so it seems FoxyProxy isn't needed after all (at least for Chrome).
... would be nice if you could do short write-up with tips, hints for others who follow in your trails and leave it (or a link to it) on the wiki
https://dot-bit.org/HowToBrowseBitDomains
or more specifically its own little section somewhere here maybe
https://dot-bit.org/HowToBrowseBitDomains#With_NmcSocks
thnx.
Re: A local namecoin proxy to implement most of the draft sp
^ I have added a note in https://dot-bit.org/HowToBrowseBitDomains#With_NmcSocks on avoiding FoxyProxy for Chrome and sticking with its built-in proxy configuration. I think this sums up the additional information I needed to make it work.
Re: A local namecoin proxy to implement most of the draft sp
I'm not getting how to install this.
When I try to install from source, I do:
./build.sh <~/software_source_packages/node-v0.10.31.tar.gz> /usr/bin
& get:
/usr/bin is a directory
I thought you give it a path to the node tarball, & a path to openssl. What do I have to do to make that work?
Also, when I try to install the binary, I do:
sudo ./nmcsocks
& I get:
No such file or directory
...But when I do:
dir
It's there.
Please give me a hand here.
Thanks,
-F
When I try to install from source, I do:
./build.sh <~/software_source_packages/node-v0.10.31.tar.gz> /usr/bin
& get:
/usr/bin is a directory
I thought you give it a path to the node tarball, & a path to openssl. What do I have to do to make that work?
Also, when I try to install the binary, I do:
sudo ./nmcsocks
& I get:
No such file or directory
...But when I do:
dir
It's there.
Please give me a hand here.
Thanks,
-F
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: A local namecoin proxy to implement most of the draft sp
As far as I know no one is maintaining NMCSocks; it's been mainly obsoleted by NMControl and FreeSpeechMe.FULl wrote:I'm not getting how to install this.
When I try to install from source, I do:
./build.sh <~/software_source_packages/node-v0.10.31.tar.gz> /usr/bin
& get:
/usr/bin is a directory
I thought you give it a path to the node tarball, & a path to openssl. What do I have to do to make that work?
Also, when I try to install the binary, I do:
sudo ./nmcsocks
& I get:
No such file or directory
...But when I do:
dir
It's there.
Please give me a hand here.
Thanks,
-F