Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 1931. (Read 2761645 times)

hero member
Activity: 687
Merit: 500

Hey CfB... will there be a new thread for the official NXT source code release?

U should ask Jean-Luc. I'll create a thread about the bounties for found flaws.

@Jean-Luc and CfB: Is there a concrete timeline or do we just have to refresh the browser every minute tomorrow?  Grin
hero member
Activity: 784
Merit: 500
Isn't there a javascript library to check sha256 sums? If so, somebody more fluent than me in javascript can easily add an update.html page to the client. It can request the value of the NRSversion alias from localhost, which contains the latest stable version and sha256, and I can also start putting the download url as a value of NRSrelease alias. Then download the zip file from that url, check if sha256 matches, and notify the user whether the downloaded zip file is legitimate or not. No need to trust a third party or manually check sha256 sums. Only the first time you download a client need to verify manually.


Great idea! Anyone fit in javascript?
legendary
Activity: 1540
Merit: 1016
with 0.4.9e,can not synchronize the blockchain.
Need to copy .nxt from 0.4.8 to 0.4.9e?
maybe add more wellknownpeers
full member
Activity: 126
Merit: 100
with 0.4.9e,can not synchronize the blockchain.
Need to copy .nxt from 0.4.8 to 0.4.9e?

Yes copy them over from the .4.8 to the new one
No need to delete *.nxt files between releases.
legendary
Activity: 1512
Merit: 1004
with 0.4.9e,can not synchronize the blockchain.
Need to copy .nxt from 0.4.8 to 0.4.9e?
legendary
Activity: 1540
Merit: 1016

There is an NXT thread for Chinese people and all of you. Wink
中国人的NXT。

https://bitcointalksearch.org/topic/nxt-361812

完成了!
hero member
Activity: 490
Merit: 504
Thief EpicThomas:
https://bitcointalksearch.org/user/epicthomas-172850
Owner of "epicdices.com" (http://domain-kb.com/www/epicdices.com)

Thief posts made by nick EpicThomas (originally with a link to the hacked client):
31-12-2013, 14:23:22: https://bitcointalksearch.org/topic/m.4237883
31-12-2013, 12:53:39: https://bitcointalksearch.org/topic/m.4236707
28-12-2013, 13:28:54: https://bitcointalksearch.org/topic/m.4184582

Since there were other thefts before these posts, older posts were deleted or posted by other account.

Thefts from block:
http://87.230.14.1/nxt/nxt.cgi?action=1000&blk=17240155162180650056:

01.01.2014 12:56:54 18,665 Nxt from plasticAiredale     http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=15182566201738727933
01.01.2014 12:58:03 7,808 Nxt from PaulyC   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=16204974692852323982 (more older thefts here) A
01.01.2014 13:01:45   18,197 Nxt from newcn   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=9793828175536096502
01.01.2014 13:03:39 92 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 (more older thefts here) B
01.01.2014 13:05:06 147,690 Nxt from sparta_cuss    http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=12152013998194592943

Thefts from block:
http://87.230.14.1/nxt/nxt.cgi?action=1000&blk=11727357463857289892

29.12.2013 08:21:32      99 Nxt   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=16204974692852323982 A
29.12.2013 08:20:26      55 Nxt   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=16204974692852323982 A
29.12.2013 08:19:32      502 Nxt   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=16204974692852323982 A
29.12.2013 08:19:00      499 Nxt   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=16204974692852323982 A

Single thefts (blocks checked):
27.12.2013 00:03:22      509 Nxt  http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B
26.12.2013 20:26:15      499 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B
26.12.2013 18:39:14          500 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B
26.12.2013 12:53:07           98 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B

block: http://87.230.14.1/nxt/nxt.cgi?action=1000&blk=7058684459482772470
25.12.2013 18:25:25      999   Nxt   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B
25.12.2013 18:24:54      705   Nxt   http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B

Single thefts (blocks checked):
25.12.2013 14:59:46      499  Nxt    http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B

block: http://87.230.14.1/nxt/nxt.cgi?action=1000&blk=15904983691408191996
23.12.2013 19:06:16      255 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B
23.12.2013 19:08:26         1,004 http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=10543042600713097314 (?? - not sure if theft)

23.12.2013 19:05:48  499 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542 B

22.12.2013 09:22:08 999 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542&offset=11&filter=1 B
16.12.2013 15:48:56 3,874 Nxt http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=6164081464868000542&offset=11&filter=1 B
sr. member
Activity: 392
Merit: 250
Isn't there a javascript library to check sha256 sums? If so, somebody more fluent than me in javascript can easily add an update.html page to the client. It can request the value of the NRSversion alias from localhost, which contains the latest stable version and sha256, and I can also start putting the download url as a value of NRSrelease alias. Then download the zip file from that url, check if sha256 matches, and notify the user whether the downloaded zip file is legitimate or not. No need to trust a third party or manually check sha256 sums. Only the first time you download a client need to verify manually.
legendary
Activity: 1512
Merit: 1004

There is an NXT thread for Chinese people and all of you. Wink
中国人的NXT。

https://bitcointalksearch.org/topic/nxt-361812
legendary
Activity: 1540
Merit: 1016

Hey CfB... will there be a new thread for the official NXT source code release?

U should ask Jean-Luc. I'll create a thread about the bounties for found flaws.


Hey CfB Jean-Luc... will there be a new thread for the official NXT source code release?   lmao   Grin
Grin
sr. member
Activity: 392
Merit: 250
Hey CfB Jean-Luc... will there be a new thread for the official NXT source code release?   lmao   Grin
Fine, I will start one tomorrow after I do it.
hero member
Activity: 739
Merit: 500

Going forward from this moment:

How can we be 100% sure someone coins are actually stolen? the victim could himself open an account and send the funds there....then after a period of time he then transfers the stolen funds to some new account and carries on happily ever after.

MOTIVATION: Those who have there funds stolen may get some sort of funding to compensate for their loss.  An greedy individual may take advantage of this.

 

Because of this reason, I think only PaulyC and newcn are eligible for some type of reimbursement/ bounties for uncovering the bogus client.

You guys need to rethink this.  The evidence shows pretty conclusively that Sparta_cuss was actually robbed and reported it before either PaulyC or newcn.  Plus Framewood beat them all to it by a couple of days.

So - we gonna create a loss fund to cover 300K NXT and counting?

Paying back stolen Nxt is not realistic. Shit happends.
However PaulyC (and for a smaller extent newcn) should (and did) get bounty for uncovering the method of the theft, saving others.
legendary
Activity: 1092
Merit: 1010
I just checked the nxt$Crypto.class that I downloaded yesterday via the instructions for linux, and I get this.
It doesn't match at all with what is reported should be in there, but is also different from the "modified" file posted yesterday.
Can someone explain if I need to freak out or not?

Code:
things that are confusing to Damelon

thnx for posting!

Hey devs... should users be worried about having arrayOfByte as opposed to publicKey in the code above?

Looks like arrayOfByte is just how ur decompiler translated this:

Code:
things that are also confusing to Damelon

Halleluja, seems I am still safe then. Thanks for the feedback. Smiley
legendary
Activity: 2142
Merit: 1010
Newbie

Hey CfB... will there be a new thread for the official NXT source code release?

U should ask Jean-Luc. I'll create a thread about the bounties for found flaws.
legendary
Activity: 2142
Merit: 1010
Newbie
I just checked the nxt$Crypto.class that I downloaded yesterday via the instructions for linux, and I get this.
It doesn't match at all with what is reported should be in there, but is also different from the "modified" file posted yesterday.
Can someone explain if I need to freak out or not?

Code:
import java.security.MessageDigest;
import java.util.Arrays;

class Nxt$Crypto
{
  static byte[] getPublicKey(String paramString)
  {
    try
    {
      byte[] arrayOfByte = new byte[32];
      Nxt.Curve25519.keygen(arrayOfByte, null, MessageDigest.getInstance("SHA-256").digest(paramString.getBytes("UTF-8")));
      return arrayOfByte;
    }
    catch (Exception localException) {}
    return null;
  }
  
  static byte[] sign(byte[] paramArrayOfByte, String paramString)
  {
    try
    {
      byte[] arrayOfByte1 = new byte[32];
      byte[] arrayOfByte2 = new byte[32];
      MessageDigest localMessageDigest = MessageDigest.getInstance("SHA-256");
      Nxt.Curve25519.keygen(arrayOfByte1, arrayOfByte2, localMessageDigest.digest(paramString.getBytes("UTF-8")));
      byte[] arrayOfByte3 = localMessageDigest.digest(paramArrayOfByte);
      localMessageDigest.update(arrayOfByte3);
      byte[] arrayOfByte4 = localMessageDigest.digest(arrayOfByte2);
      byte[] arrayOfByte5 = new byte[32];
      Nxt.Curve25519.keygen(arrayOfByte5, null, arrayOfByte4);
      localMessageDigest.update(arrayOfByte3);
      byte[] arrayOfByte6 = localMessageDigest.digest(arrayOfByte5);
      byte[] arrayOfByte7 = new byte[32];
      Nxt.Curve25519.sign(arrayOfByte7, arrayOfByte6, arrayOfByte4, arrayOfByte2);
      byte[] arrayOfByte8 = new byte[64];
      System.arraycopy(arrayOfByte7, 0, arrayOfByte8, 0, 32);
      System.arraycopy(arrayOfByte6, 0, arrayOfByte8, 32, 32);
      return arrayOfByte8;
    }
    catch (Exception localException) {}
    return null;
  }
  
  static boolean verify(byte[] paramArrayOfByte1, byte[] paramArrayOfByte2, byte[] paramArrayOfByte3)
  {
    try
    {
      byte[] arrayOfByte1 = new byte[32];
      byte[] arrayOfByte2 = new byte[32];
      System.arraycopy(paramArrayOfByte1, 0, arrayOfByte2, 0, 32);
      byte[] arrayOfByte3 = new byte[32];
      System.arraycopy(paramArrayOfByte1, 32, arrayOfByte3, 0, 32);
      Nxt.Curve25519.verify(arrayOfByte1, arrayOfByte2, arrayOfByte3, paramArrayOfByte3);
      MessageDigest localMessageDigest = MessageDigest.getInstance("SHA-256");
      byte[] arrayOfByte4 = localMessageDigest.digest(paramArrayOfByte2);
      localMessageDigest.update(arrayOfByte4);
      byte[] arrayOfByte5 = localMessageDigest.digest(arrayOfByte1);
      return Arrays.equals(arrayOfByte3, arrayOfByte5);
    }
    catch (Exception localException) {}
    return false;
  }
}

thnx for posting!

Hey devs... should users be worried about having arrayOfByte as opposed to publicKey in the code above?

Looks like arrayOfByte is just how ur decompiler translated this:

Code:
static class Crypto {

static byte[] getPublicKey(String secretPhrase) {

try {

byte[] publicKey = new byte[32];
Curve25519.keygen(publicKey, null, MessageDigest.getInstance("SHA-256").digest(secretPhrase.getBytes("UTF-8")));

return publicKey;

} catch (Exception e) {

return null;

}

}

static byte[] sign(byte[] message, String secretPhrase) {

try {

byte[] P = new byte[32];
byte[] s = new byte[32];
MessageDigest digest = MessageDigest.getInstance("SHA-256");
Curve25519.keygen(P, s, digest.digest(secretPhrase.getBytes("UTF-8")));

byte[] m = digest.digest(message);

digest.update(m);
byte[] x = digest.digest(s);

byte[] Y = new byte[32];
Curve25519.keygen(Y, null, x);

digest.update(m);
byte[] h = digest.digest(Y);

byte[] v = new byte[32];
Curve25519.sign(v, h, x, s);

byte[] signature = new byte[64];
System.arraycopy(v, 0, signature, 0, 32);
System.arraycopy(h, 0, signature, 32, 32);

return signature;

} catch (Exception e) {

return null;

}

}

static boolean verify(byte[] signature, byte[] message, byte[] publicKey) {

try {

byte[] Y = new byte[32];
byte[] v = new byte[32];
System.arraycopy(signature, 0, v, 0, 32);
byte[] h = new byte[32];
System.arraycopy(signature, 32, h, 0, 32);
Curve25519.verify(Y, v, h, publicKey);

MessageDigest digest = MessageDigest.getInstance("SHA-256");
byte[] m = digest.digest(message);
digest.update(m);
byte[] h2 = digest.digest(Y);

return Arrays.equals(h, h2);

} catch (Exception e) {

return false;

}

}

}
hero member
Activity: 784
Merit: 500
I volunteer as part of a doorkicking crew if he's within a reasonable distance of Amsterdam.

We could travel together  Grin



We can make a fund for that!
But you have to post photos! Smiley
legendary
Activity: 1092
Merit: 1010
I volunteer as part of a doorkicking crew if he's within a reasonable distance of Amsterdam.

We could travel together  Grin

legendary
Activity: 2142
Merit: 1010
Newbie
Currently it looks like EpicThomas only was able to get a few accounts. Hopefully now people will be more vigilante with downloading new clients. But if there is no official client, or at least one endorsed by CFB how do we even know if the posted hash is the one for the client that isn't hacked. Who else can we trust?

Just make sure it matches SHA256 checksum posted by Jean-Luc.
full member
Activity: 196
Merit: 100

You guys need to rethink this.  The evidence shows pretty conclusively that Sparta_cuss was actually robbed and reported it before either PaulyC or newcn.  Plus Framewood beat them all to it by a couple of days.

So - we gonna create a loss fund to cover 300K NXT and counting?

I'm relatively NXT poor, but I'll contribute 1k to a theft fund if it's set up.



The fact is that the stolen NXT from all five of these guys is sitting stuck in the five thief accounts and it can't get converted to BTC without going thru Dgex.   That ain't gonna happen.

This is a major crime in the tens of thousands of dollars range and we know who did it.  People go to prison for years for this kind of crap.
  
(Are you reading this, EpicThomas?  I know you are.)  

You know, if the NXT were somehow to be magically transferred back into the accounts where it is supposed to be, maybe just maybe I won't personally make it my mission to find your home address and phone number, post it right here on this forum, and call the police in your local town or city.

Do you feel lucky, punk?
hero member
Activity: 854
Merit: 1001
I am still updating my originall post.
https://bitcointalksearch.org/topic/m.4269560

EvilDave is online so he is cleaning probably. After my research I will check all quoting links for the clients, can anyone help? Like to check pages 500-550...?

Not me, salsa, I'm an innocent bystander here.
Intel got EpicThomas and EvilDave mixed up for a moment in the heat of the fight.

So do we have any leads on the realworld ID and/or location of EpicThomas ?
I volunteer as part of a doorkicking crew if he's within a reasonable distance of Amsterdam.

@Damelon...thx for the quick correction, bro.
Jump to: