elective-stereophonic
elective-stereophonic
NRS v1.10.1
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 [2] 3  All

Author Topic: NRS v1.10.1  (Read 32463 times)

Butthead

  • Jr. Member
  • **
  • Karma: +1/-0
  • Offline Offline
  • Posts: 16
    • View Profile
Re: NRS v1.10.1
« Reply #20 on: August 11, 2016, 05:09:33 pm »

Installed in Windows 10.

Worked and forging.
Logged

Jose

  • Global Moderator
  • Hero Member
  • *****
  • Karma: +78/-1
  • Offline Offline
  • Posts: 768
    • View Profile
Re: NRS v1.10.1
« Reply #21 on: August 11, 2016, 06:48:06 pm »

Quote
This message should appear when you are connected to a remote node and trying to submit an action which requires sending your passphrase to the remote node, including:
Start Forging, Stop Forging, Start Shuffler, Start Monitor, Set Hallmark.
What exactly are you doing when getting this message ?
Which configuration ? Web Wallet/Desktop Wallet, Full client, light client, roaming client.

The same message
Quote
WARNING: Your passphrase will be sent to the server!
shows up to me when trying to start forging in a Raspberry Pi that is running NRS 1.10.1 in my private network (not a public node, just forging). I can see that the blockchain is fully up to date, so I guess NRS it's not working in "light" mode (connected to a remote node).
I accesss to the Raspi's NRS gui throught the web explorer in my PC (192.168.X.X:7876, not 127.0.0.1:7876)


Apart from that "issue", everything works fine.
« Last Edit: August 11, 2016, 06:53:52 pm by Jose »
Logged

martismartis

  • Hero Member
  • *****
  • Karma: +73/-10
  • Offline Offline
  • Posts: 1238
    • View Profile
Re: NRS v1.10.1
« Reply #22 on: August 11, 2016, 06:48:21 pm »

Please update forum header with link to 1.10.1 mandatory update.
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.10.1
« Reply #23 on: August 12, 2016, 01:26:53 pm »

I'm getting all the time "Warning: Your passphrase will be sent to the server!"
Is that new? Or is it related to some wrong setting I have?
What about the admin password. Is there a risk not to have that?
I am running a public node.
Thanks!

This message should appear when you are connected to a remote node and trying to submit an action which requires sending your passphrase to the remote node, including:
Start Forging, Stop Forging, Start Shuffler, Start Monitor, Set Hallmark.
What exactly are you doing when getting this message ?
Which configuration ? Web Wallet/Desktop Wallet, Full client, light client, roaming client.

I'm using the full client and it happens, for example, when starting forging.
But why do I get this warning? I guess I'm connected to my own server. Maybe the settings with hallmark and my public ip address are letting the client believe that I'm going on a remote node?
Thanks!

It is indeed a bug, the code currently ignores the isLocalhost check and always assumes the client is connected to a remote node.
This means that transactions are locally signed even when they can be signed by the local node, passphrase warning is displayed with no reason and the forging indicator is not updated automatically during login. I can't think of a real problem that is caused by this except for these minor annoyances.
Anyway, this will be fixed in 1.10.2
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

TheWireMaster

  • Sr. Member
  • ****
  • Karma: +27/-0
  • Offline Offline
  • Posts: 356
    • View Profile
    • NXT Folks
Re: NRS v1.10.1
« Reply #24 on: August 12, 2016, 01:46:20 pm »

I'm getting all the time "Warning: Your passphrase will be sent to the server!"
Is that new? Or is it related to some wrong setting I have?
What about the admin password. Is there a risk not to have that?
I am running a public node.
Thanks!

This message should appear when you are connected to a remote node and trying to submit an action which requires sending your passphrase to the remote node, including:
Start Forging, Stop Forging, Start Shuffler, Start Monitor, Set Hallmark.
What exactly are you doing when getting this message ?
Which configuration ? Web Wallet/Desktop Wallet, Full client, light client, roaming client.

I'm using the full client and it happens, for example, when starting forging.
But why do I get this warning? I guess I'm connected to my own server. Maybe the settings with hallmark and my public ip address are letting the client believe that I'm going on a remote node?
Thanks!

It is indeed a bug, the code currently ignores the isLocalhost check and always assumes the client is connected to a remote node.
This means that transactions are locally signed even when they can be signed by the local node, passphrase warning is displayed with no reason and the forging indicator is not updated automatically during login. I can't think of a real problem that is caused by this except for these minor annoyances.
Anyway, this will be fixed in 1.10.2

Thanks Riker! Then I will restore the settings and make my node public again. Address in my browser is localhost so I also don't think that there is any danger. :)
Logged
NXT-5WW2-XQ63-CFGM-G7YAJ

neofelis

  • Hero Member
  • *****
  • Karma: +74/-12
  • Offline Offline
  • Posts: 568
    • View Profile
MAC problem
« Reply #25 on: August 14, 2016, 03:38:44 am »

I've got three MACs and can only get the NRS to run on one of them.  The two where it won't run have both run multiple previous versions. Could there be some residual nxt software that won't allow them to run?  The current version starts to run but no wallet appears.

Anybody?
Logged

PoofKnuckle

  • Hero Member
  • *****
  • Karma: +111/-7
  • Offline Offline
  • Posts: 849
  • Your Concern is Noted.
    • View Profile
    • NXT FreeMarket
Re: MAC problem
« Reply #26 on: August 14, 2016, 09:41:25 am »

I've got three MACs and can only get the NRS to run on one of them.  The two where it won't run have both run multiple previous versions. Could there be some residual nxt software that won't allow them to run?  The current version starts to run but no wallet appears.

Anybody?

What version of Java do you have installed on them?

Logged
NXT: NXT-WBVP-83YM-FRB3-9MQLY
BM-NBTVHaA41Ejh2G6krD9p5vM62vk84isM

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: NRS v1.10.1
« Reply #27 on: August 14, 2016, 11:33:54 am »

Great job on the light client! I really like it.

Small improvement to be made:
With the flag isLightClient=true, it is not need to prompt the same text in the confirmation box when shutting down then NRS server:


The thing with suffler and other is confusing and not need. Only the first sentence is fully adequate.
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

neofelis

  • Hero Member
  • *****
  • Karma: +74/-12
  • Offline Offline
  • Posts: 568
    • View Profile
Re: MAC problem
« Reply #28 on: August 14, 2016, 01:49:08 pm »

I've got three MACs and can only get the NRS to run on one of them.  The two where it won't run have both run multiple previous versions. Could there be some residual nxt software that won't allow them to run?  The current version starts to run but no wallet appears.

Anybody?

What version of Java do you have installed on them?

I'm not sure. The latest though. I always update whenever I get a message to. What version do you recommend and I'll install that.  You're probably right, though, it's probably a Java problem.

Logged

neofelis

  • Hero Member
  • *****
  • Karma: +74/-12
  • Offline Offline
  • Posts: 568
    • View Profile
Acct control issue
« Reply #29 on: August 14, 2016, 02:04:50 pm »

So I have two main accounts and I was playing with acct control to have one control the other with mandatory approval of all transactions. It worked fine, but when I went to disable mandatory approval, I kept getting an error message.  So my solution was to change the number of accts needed for oapproval to zero. But that didn't fix the problem. Now I have to approve all my own transactions, effectively paying double for every transaction. When I call up acct control to view the status of the previously controlled acct, the area where it would usually have the RS of the controlling acct is blank.

In short, I can't turn off mandatory approval. I'm considering just starting over with a fresh acct, but thought the devs might want to know about this problem.




Also, I found out that you can approve a transaction that has already been approved. You can do this as many times as you'd like, costing you lots of transaction fees.  Don't know why you'd want to approve a transaction that had already been approved, but some error message not allowing you to do that might be nice.

Logged

PoofKnuckle

  • Hero Member
  • *****
  • Karma: +111/-7
  • Offline Offline
  • Posts: 849
  • Your Concern is Noted.
    • View Profile
    • NXT FreeMarket
Re: MAC problem
« Reply #30 on: August 14, 2016, 02:12:36 pm »

I've got three MACs and can only get the NRS to run on one of them.  The two where it won't run have both run multiple previous versions. Could there be some residual nxt software that won't allow them to run?  The current version starts to run but no wallet appears.

Anybody?

What version of Java do you have installed on them?

I'm not sure. The latest though. I always update whenever I get a message to. What version do you recommend and I'll install that.  You're probably right, though, it's probably a Java problem.

The new Nxt client is supposed to include Java inside it, so you don't have to install it. However, I tend to install the latest JDK (not JRE) manually.

You can get the latest JDK here:

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

That might set things straight for you.

Logged
NXT: NXT-WBVP-83YM-FRB3-9MQLY
BM-NBTVHaA41Ejh2G6krD9p5vM62vk84isM

ScripterRon

  • Hero Member
  • *****
  • Karma: +75/-2
  • Offline Offline
  • Posts: 523
    • View Profile
Re: NRS v1.10.1
« Reply #31 on: August 14, 2016, 03:27:24 pm »

I was not comfortable with storing my secret phrase on a public node in the script: start-forging
Instead I have now encrypted the script as follows:
Code: [Select]
sudo apt-get install p7zip-full
7za a start-forging start-forging -tzip -mem=AES256 -mx9 -p
When I need to upgrade the NRS version and re-start forging on the server:
Code: [Select]
7z x start-forging.zip #Enter password
./start-forging
rm start-forging
Storing the password is a concern.  But my Ubuntu system is set up with no login passwords, SSH uses shared keys, and the firewall restricts SSH to my desktop IP address.  The forging account has no balance (my account balance is leased to the forging account).
Logged

ScripterRon

  • Hero Member
  • *****
  • Karma: +75/-2
  • Offline Offline
  • Posts: 523
    • View Profile
Re: NRS v1.10.1
« Reply #32 on: August 14, 2016, 05:40:34 pm »

Storing the password is a concern.  But my Ubuntu system is set up with no login passwords, SSH uses shared keys, and the firewall restricts SSH to my desktop IP address.  The forging account has no balance (my account balance is leased to the forging account).
Isn't there also a risk of exploit through the API? For example, through the API someone is able to list the contents of the file: start-forging ? Is it recommended to run NRS with a user account (not root) ?
I'm not aware of an NRS API that will list the contents of local files.  It is a good security practice to run NRS under a non-root account (NRS does not need root access for anything).
Logged

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: NRS v1.10.1
« Reply #33 on: August 15, 2016, 10:04:01 am »

I was not comfortable with storing my secret phrase on a public node in the script: start-forging
The usual approach is to lease your balance to an empty account and forge with that. That way, if someone does manage to get access to the script, all they can steal is the forging revenue.

Actually I keep 1,000+ NXT in the forging account, so if I forget to renew the lease I can still start forging with it during the 1440 blocks it takes to register the renewal. Using the Argus notification email service makes me less likely to forget to in the first place. If someone does steal the 1,000, then it means my PC is hacked and frankly I'll be glad to have found out about it. If they have got as far as reading the script (and understanding its significance) I wouldn't trust they don't also have the ability to write to my machine, and install a keylogger or their own version of NRS or whatever. The forging account is like a canary.

For this reason I think it would be good if forging could be initiated from the properties.nxt file, so we didn't have to bother with scripts. Adding this feature would not require a hard fork, and making forging more convenient might increase the number of accounts that forge.
Logged

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.10.1
« Reply #34 on: August 15, 2016, 12:31:01 pm »

The usual approach is to lease your balance to an empty account and forge with that. That way, if someone does manage to get access to the script, all they can steal is the forging revenue.
If this is the recommended approach (empty account with a leased balance), then the NSC initiative should also be updated to encourage this setup. Currently, to earn NSC coins at the highest level for a public node, it is encouraged to have 9999 NXT or more in the account, see: https://nxtforum.org/assets-board/(ann)-nxt-security-coin-(nsc)-get-paid-for-supporting-the-nxt-network!

Hallmarking and forging are not related. You can hallmark a node with your main account in a cold wallet and receive NSC for the big balance hallmark.
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

neofelis

  • Hero Member
  • *****
  • Karma: +74/-12
  • Offline Offline
  • Posts: 568
    • View Profile
Re: MAC problem
« Reply #35 on: August 15, 2016, 08:04:05 pm »


The new Nxt client is supposed to include Java inside it, so you don't have to install it. However, I tend to install the latest JDK (not JRE) manually.

You can get the latest JDK here:

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

That might set things straight for you.

Thanks Poof,  I'll try that.  I had Java version 8 and reloaded it but no luck.  I'll try the JDK.
Logged

kseistrup

  • Sr. Member
  • ****
  • Karma: +48/-0
  • Offline Offline
  • Posts: 465
  • Fortune favours the lucky
    • View Profile
    • @kseistrup
Re: NRS v1.10.1
« Reply #36 on: August 16, 2016, 06:52:03 am »

It's time you refresh your copy of the key ;-)

Ahh, so it's that time of the year :)
Thanks!

You could put the following in your crontab and have it done automatically every day (or week, or whatever):

Code: [Select]
@daily * * * gpg2 --refresh-keys >/dev/null 2>&1

 :)

beammeup

  • Jr. Member
  • **
  • Karma: +0/-0
  • Offline Offline
  • Posts: 24
    • View Profile
Re: NRS v1.10.1
« Reply #37 on: August 17, 2016, 06:36:10 am »

i am running a raspberry pi 3, i removed the lib folder from v1.9.2 then unpacked the v1.10.1 overwriting existing files. When i run.sh i now get this error;

Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/simple/JSONObject
   at java.lang.Class.getDeclaredMethods0(Native Method)
   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
   at java.lang.Class.getMethod0(Class.java:3018)
   at java.lang.Class.getMethod(Class.java:1784)
   at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544)
   at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526)
Caused by: java.lang.ClassNotFoundException: org.json.simple.JSONObject
   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
   ... 7 more
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError: org/json/simple/JSONObject
   at java.lang.Class.getDeclaredMethods0(Native Method)
   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
   at java.lang.Class.getMethod0(Class.java:3018)
   at java.lang.Class.getMethod(Class.java:1784)
   at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544)
   at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526)
Caused by: java.lang.ClassNotFoundException: org.json.simple.JSONObject
   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
   ... 7 more
everything was working fin in v1.9.2 i was forging ok
Logged

beammeup

  • Jr. Member
  • **
  • Karma: +0/-0
  • Offline Offline
  • Posts: 24
    • View Profile
Re: NRS v1.10.1
« Reply #38 on: August 17, 2016, 07:17:59 am »

OK i removed the old one except the db and conf then installed the new one and replace conf and db files now it is working. Is there anything else from the old v1.9.2 that I should put into the v1.10.1?
Logged

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.10.1
« Reply #39 on: August 17, 2016, 07:20:15 am »

OK i removed the old one except the db and conf then installed the new one and replace conf and db files now it is working. Is there anything else from the old v1.9.2 that I should put into the v1.10.1?

Normally copy the db and nxt.properties file to the new release folder. For any release. This is what I did for 1.9.2 to 1.10.1 update and it has worked for me as before.
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7
Pages: 1 [2] 3  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly