Haha :pneofutur wrote:( no need for GUI, and no need for windows
The DNS server is already here in last release, even if .bit support is still primitive.
Haha :pneofutur wrote:( no need for GUI, and no need for windows
Code: Select all
$ ./nmcontrol domain lookup 'dot-bit.bit'
ERROR: {u'id': 1, u'result': u'Exception : list indices must be integers, not str', u'error': True}
By giving the file the execution permission & the OS can also read the file a bit to guess it's type :phelix wrote:One important thing: the main file nmcontrol should be called nmcontrol.py !
only then can you run it on windows (how the heck do you recognize executables on unix ?)
Code: Select all
file nmcontrol
nmcontrol: Python script, ASCII text executable
I know about the shebang. But how can a human see it? I think there are some shells that show different colors for executable files. On my vServer consoles there are no colors...khal wrote:By giving the file the execution permission & the OS can also read the file a bit to guess it's type :phelix wrote:One important thing: the main file nmcontrol should be called nmcontrol.py !
only then can you run it on windows (how the heck do you recognize executables on unix ?)the execution persmission allow to do : ./nmcontrolCode: Select all
file nmcontrol nmcontrol: Python script, ASCII text executable
the first line in the file launch it with python and avoid doing "python nmcontrol"
Actually I tried it and it works. Nobody would expect that, though. OK, probably we need an installer for windows.On windows, you can't do c:\\python.exe nmcontrol ? (without .py)
No worries. DNS is not working? I am quite sure it worked for meThanks for reporting all the bugs. We be fixed soon, or not :p
The domain plugin is not ready for use and need a major refactoring (same for the DNS service).
deiban automatically (or I've uncommented the alias) add a --color to the /bin/ls command.phelix wrote: I know about the shebang. But how can a human see it? I think there are some shells that show different colors for executable files. On my vServer consoles there are no colors...
Actually I tried it and it works. Nobody would expect that, though. OK, probably we need an installer for windows.
If I'm right (its a bit old :p) : the dns code & namecoin json analysis are mixed (wrong place/architecture), and json analysis only support spec v1.phelix wrote: No worries. DNS is not working? I am quite sure it worked for me
I can create a frozen python .exe so it is not necessary to install python. Also innosetup installer should be no problem (besides time )khal wrote:deiban automatically (or I've uncommented the alias) add a --color to the /bin/ls command.phelix wrote: I know about the shebang. But how can a human see it? I think there are some shells that show different colors for executable files. On my vServer consoles there are no colors...
Actually I tried it and it works. Nobody would expect that, though. OK, probably we need an installer for windows.
.py will be added, and yes, we need an installer for windows (or a bundle that one can unzip at least)
Sounds good.If I'm right (its a bit old :p) : the dns code & namecoin json analysis are mixed (wrong place/architecture), and json analysis only support spec v1.phelix wrote: No worries. DNS is not working? I am quite sure it worked for me
I had written a quick tor plugin (as a proof of concept, not published to git) that does the following :
In browser : http://any-domain.tor => dns resolution by nmcontrol => 127.0.0.2 => http server of nmcontrol : read the name "tor/domain" => reply an http redirect to : xxxxx.onion
The domain name change from .tor to .onion in the browser, you don't have to remember .onion addresses, but you are still redirected to an unreadable address.
Not sure it's the good way to do it ? Maybe as a first step ?
(It could also allow a tor search engine once tor domains are registered in namecoin).
Code: Select all
* Available commands for plugin dns :
getFingerprint
getFreenet
getI2p
getIp4
getIp6
getOnion
Code: Select all
{u'name': u'd/ns', u'nameKey': u'ip', u'flatDomains': [u'www', u'*', u''], u'nameData': {u'map': {u'': u'10.0.0.0'}}, u'host': u'ns', u'subdomain': u'www'}