Topic: Closed Thread - page 392. (Read 677687 times)
I have lost track of what NXTL (node) has been doing. I was one of first ones to get a stake. Am I too late, I don't see my name on the list anymore apart from the original one?
@ 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!
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!
Getting a 404 when trying to download.
We disabled, wait for the next version
Probably a good call.
Getting a 404 when trying to download.
We disabled, wait for the next version
Getting a 404 when trying to download.
so next version when will release？
This password access to the IP logs
The Commission knows
What do you want to say it?
The Commission knows
What do you want to say it?
I know, it is just funny in the context of my having found coins behind the low entropy password.
I've just finished skimming the app.js and everything looks decent.
I am happy to see that the address generation is not nearly as broken as it appeared from external analysis! No worry of address collisions.
Now I go on to verify the node_modules packages and the frontend. Things are looking up, but you will certainly want to run this with newest nodejs versions, v0.8.28 and v0.10.30. The version in the distribution is older, and has known vulnerabilities which appear to be able to be exploited through the peering. (Specifically, I just tested the most recent stack munging from Fedor et al in a sandbox and was able to (at least
) remotely crash a peer.)
people !!! send emails to BITTREX E-MAIL LINK to add NODE ... we want more people sending emails to bittrex add our coin
OOPS...
Well that is good news anyhow. Good for you and me too... was getting anxious to get home from work to double check my account
OOPS... PLEASE DELETE ALL MESSAGES IN WHICH YOU HAVE QUOTED ME REPORT THE PASSPHRASE ISSUE... I HAD THE WRONG PIECE OF PAPER IN FRONT OF ME!?!?! ROFLMAO!
...I will delete all my posts immediately...
No, let's show it to everybody) People should check everything on their side before starting freaking out and blaming devs
Source inside the binary was partially obfuscated, but not very well. Here is the source to the app.js: http://pastebin.com/a7JzU7kv
EDIT: These devs love those low entropy passwords, eh?
<3 that serverKey!
EDIT: These devs love those low entropy passwords, eh?
Code:
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?
Source inside the binary was partially obfuscated, but not very well. Here is the source to the app.js: http://pastebin.com/a7JzU7kv
EDIT: These devs love those low entropy passwords, eh?
<3 that serverKey!
EDIT: These devs love those low entropy passwords, eh?
Code:
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 guy @hunterminer.... only want to spread fud to this coin ...
Only want to see the source running safely and decentralized, as was promised, still.
The nodewebkit binary version shipped for the client has some known vulnerabilities. I would not recommend to anyone to run this version until we can easily run against our own nodewebkit.
Are you trying to say it doesn't run locally?
Dunno, haven't actually run the thing just yet.
All I'm saying is that it appears that the node binary included is not most recent, so some known vulnerabilities are there.
The nodewebkit binary version shipped for the client has some known vulnerabilities. I would not recommend to anyone to run this version until we can easily run against our own nodewebkit.
Are you trying to say it doesn't run locally?
Loading ... Please wait! how long do I have to wait?
can not open the wallet , have waited 10 minutes
Loading ... Please wait! how long do I have to wait?
can not open the wallet , have waited 10 minutes Jump to: