Get access to what? There is no proof that that code is connected to NODE code. So there is no fact, only fud
Special for you:
Source inside the binary was partially obfuscated, but not very well. Here is the source to the app.js:
http://pastebin.com/a7JzU7kvEDIT: These devs love those low entropy passwords, eh?
var Config = function() {
return {
port: 19775,
host: "127.0.0.1",
starPeers: ["5.45.124.65:19776", "5.45.114.108:19776"],
peerPort: 19776,
serverKey: "qwerty123456",
devMod: false
}
}();
<3 that serverKey!
This password access to the IP logs
The Commission knows What do you want to say it?
I just point that a Linux client SHOULD be released at first! Linux is for now the best OS for securing your crypto.
I had no problem running the client on Linux after extracting the source from the nodewebkit windows binary. When the client is finished and re-released I'll provide instructions for doing this yourself.
@ People of NodeKingdom
Thank you all, for being proactive with the project!
We collected all the reported errors. logs and we'll perform some "Bug Annihilation"!
- Due to this reason, we will temporarily disable the download link!
We will make some maintenance and if you notice some glitches - then it is probably us!
So, keep calm and VOTE for NODE on Exchanges !
Await further announcements and V. 0.2 Release!
Also, special Thanks for HunterMinerCrafter for pointing out issues that are only visible from aside!
Keep up the good work - and "Strip that Code Naked" xD
Peace!
The new release is still using the outdated and known-vulnerable v0.10.22 nodejs.
The new source is packed using some "actual" obfuscation this time, and is not as trivially recovered. This just makes me wonder what they are applying this effort/expense to hide something toward.
This obfuscated code also doesn't run cleanly under nodejs alone anymore. For the moment I'll not be running any node nodes since I don't want to be forced to use their insecure nodejs on windows.
Enough proofs for you? Still FUD??