Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on August 10, 2016, 03:53:29 pm

Title: NRS v1.10.1
Post by: Jean-Luc on August 10, 2016, 03:53:29 pm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.10.1

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.10.1.zip

sha256:

fd4ac1811a7fa968356d0391988c9a08f796748324e8cb43124b7f6b0c683823  nxt-client-1.10.1.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.10.1.sh

sha256:

9b928a253227f4c68245f6b5c3fc0eea67224858100e4ad0c0317361f541c061  nxt-client-1.10.1.sh

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.10.1.exe

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.10.1.dmg

The exe, dmg, and sh packages must have a digital signature by "Stichting NXT".


Change log:

This release adds transaction replay protection, to be enabled at the hard fork
scheduled for block 1,000,000. Upgrading to 1.10.1 or later before that block
is mandatory for all.

The ecBlockId and ecBlockHeight transaction fields, previously populated but
not used, will begin to be used for enforcing that a transaction submitted on
one blockchain or fork will not be accepted on another blockchain or fork that
shares the same code. These fields by default will be set to a block 720 blocks
behind the last block at the time the transaction is created, and transactions
will only be accepted if their ecBlockId and ecBlockHeight values point to an
existing block when they are included in the blockchain. This default setting
provides protection against replaying the transaction on a hard fork that has
diverged more than 720 blocks from the one where the transaction was created.

Light clients that have no way of verifying the ecBlock values returned by a
remote node will use hardcoded values, to be updated manually at some releases.
Transactions from legacy light clients that leave eBlockId and height set to 0
will still be accepted, but cannot benefit from such replay protection.

All CreateTransaction APIs now accept additional ecBlockId and ecBlockHeight
parameters, allowing the default values to be overridden by the client.

Minor bugfixes and UI improvements.

Updated Jetty to version 9.3.11, delete the old lib folder before unpacking on
top.


-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXq0cAAAoJENqvaxkWiP4ZfPAQANqR3760FscXaV0zIQ8yFLYK
muUjnHG4/vflG8HEVIe89Ujsi9EE7Kkbv6/R7GprterKFbpBMlroxon9oX0ex3xj
IOHhcJEQsrLslu8lTxhX5/ggJCkKCWnohK7w04ch1P/AJrDsbtgJoGMrhsnkUNb6
qael5Shm+/KNEfVsUVRo0NzWTOS+WyBsdpbFyiGX4lqrACe8wMS1Wz8rBcQa1hPe
SwWAUtt81PfaAbCNSXo2SA+/09Fj2UZ1I6YNwGFLVQYi+KmtppwUBGrn2BhewWhI
jrTlgff2jqGfU8EnhjGMrZpKgqtTXWGbaPqy/vOrv0kQqFfXTO8OaeuPl+CidTJO
JoHMc3HYw4e+sekAgHb/XzJAmriE0JC8JeY1ueLwaHwA+CGxdFfPHlupnMWqNe7H
djUpCZMpg0Fiy2N1KCZnGJAqjlW2US259TtkjtfiqD8XunxPyqAZ9FywU4n2mlI7
1GGwcN+ijYOnIt/F5tSMsxh6WE2DQk7zUOYpJbKhTQtr9k6+c3d9uq/6jZJDtHr7
imObpa1HrLCl9z8HefqINNDa7NXB07iNiSq/vdxaAwSH43toyrTLpeshpDKcK+9+
LkzaCJNfuyXTNlnhjoIlKtTl357rbzaJRsbW8fj3iw8pqfbTs9aPjgfklZaHxH+P
opqlEGyOAT5EqLZZCVa6
=tZIn
-----END PGP SIGNATURE-----
Title: Re: NRS v1.10.1
Post by: yassin54 on August 10, 2016, 04:02:42 pm
Thank you!! :)
Tweeted!! https://twitter.com/NxtCommunity/status/763404875975753728  8)
Title: Re: NRS v1.10.1
Post by: jnsptrsn on August 10, 2016, 04:10:13 pm
Thanks,

seems like it's time to renew your key:

Code: [Select]
pub   4096R/E1E4240C 2015-07-29 [expired: 2016-07-28]
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp@secure.mailbox.org>
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp@mailbox.org>
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp666@yandex.ru>
Title: Re: NRS v1.10.1
Post by: Riker on August 10, 2016, 04:15:07 pm
Important - light clients and new nodes which still download the blockchain, may see the message "Server Connection Error No openAPI peers found" on the login screen.
These nodes, temporarely, won't be able to connect.
The reason is that in version 1.10.1 we introduced additional parameters to existing APIs. Therefore light clients are required to connect to a public node with open API running version 1.10.1 and cannot use the existing 1.9.2 nodes.
But since there are only few such nodes, users may not be able to connect.

Therefore, users running public nodes please do your best to upgrade quickly to this release.
This should be a temporary issue, once enough nodes upgrade the problem should resolve itself.
Title: Re: NRS v1.10.1
Post by: Riker on August 10, 2016, 04:25:01 pm
As a temporary workaround you can force your light client to connect to a node which has already been upgraded.

For example in nxt.properties add the following setting:
nxt.forceAPIProxyServerURL=https://162.243.242.8:7876

This setting should be removed as soon as enough open API nodes upgrade so that this poor node won't become the single source of data to your light client.
Title: Re: NRS v1.10.1
Post by: lurker10 on August 10, 2016, 04:44:27 pm
It appears that when nxt.apiServerHost is pointed to one of the two ip addresses on a vps, the API flag is not advertised in 'services' for getPeer and addPeer. The workaround is setting nxt.apiServerHost=0.0.0.0. Is this a bug or a feature?
This is the same for 1.9.2.
Title: Re: NRS v1.10.1
Post by: shugo on August 10, 2016, 05:26:22 pm
My node runs 1.9.2 on my raspberry. What do I have to do to update to 1.10.1??
Title: Re: NRS v1.10.1
Post by: lurker10 on August 10, 2016, 05:33:58 pm
My node runs 1.9.2 on my raspberry. What do I have to do to update to 1.10.1??

wget https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.10.1.zip ;
kill -15 `pidof java`;
rm -rf ./nxt.old;
mv nxt nxt.old;
unzip nxt-client-1.10.1.zip;
mv nxt.old/nxt_db nxt;
cp nxt.old/conf/nxt.properties nxt/conf/;
cd nxt; nohup ./run.sh &
Title: Re: NRS v1.10.1
Post by: martismartis on August 10, 2016, 05:34:23 pm
My node runs 1.9.2 on my raspberry. What do I have to do to update to 1.10.1??

1. Stop node with ctrl+c and wait until it shutdowns completely.
2. Delete "lib" directory from your nxt installation directory.
3. Download and unzip 1.10.1 over your nxt installation, overwriting all files
4. start run.sh from your terminal window.
Title: Re: NRS v1.10.1
Post by: shugo on August 10, 2016, 05:51:59 pm
thanks for your help, seems to be working. the node shows 1.10.1. but i receive a lot of blocks from the future. I'll just wait until my node shows up @peerexplorer to see if it finally worked

edit: peer explorer shows 1.9.2 on the overview but if i click on my node it shows 1.10.1 - i guess it worked and peerexplorer has to update/refresh properly
Title: Re: NRS v1.10.1
Post by: martismartis on August 10, 2016, 07:40:36 pm
If I am forging on a server and then stop it for upgrade, I guess I can be penalized if my server misses it's turn to generate a block? For this reason, I try to do the upgrade as quickly as possible. Do I have to restart the forging as well after an upgrade?

Yes, if you stop a node and start it again, you need to start forging again.
Title: Re: NRS v1.10.1
Post by: hob on August 10, 2016, 10:05:30 pm
seems like it's time to renew your key:
It's time you refresh your copy of the key ;-)
expires: 2017-07-28

 gpg --refresh-keys 0x811D6940E1E4240C
Title: Re: NRS v1.10.1
Post by: jnsptrsn on August 10, 2016, 10:09:54 pm
It's time you refresh your copy of the key ;-)

Ahh, so it's that time of the year :)
Thanks!
Title: Re: NRS v1.10.1
Post by: TheWireMaster on August 10, 2016, 10:22:25 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!
Title: Re: NRS v1.10.1
Post by: ScripterRon on August 10, 2016, 10:48:07 pm
Yes, if you stop a node and start it again, you need to start forging again.
ScripterRon has a shell script for starting forging, see: https://nxtforum.org/general/command-line-arguments-documentation
Could this script be shared on the forum?
I run Ubuntu on Amazon Web Services (currently Ubuntu 16.04).  Nxt is installed in $HOME/nxt (/home/ubuntu/nxt) and runs under the 'ubuntu' user.  The -Dnxt.type parameter is not used by NRS - I use it to distinguish between the mainnet and testnet servers.  I use the nxt.log.lck file as an easy check to see if NRS is running.  The only drawback is you will need to manually delete this file if the NRS java vm crashes (the file is automatically deleted when NRS shuts down).

Script to start NRS (start-nxt)
Code: [Select]
#!/bin/sh
#############
# Start NRS #
#############

cd /home/ubuntu/nxt

if [ -f logs/nxt.log.lck ] ; then
  echo "NRS is already running"
  exit 1
fi

if [ -f logs/nxt.log ] ; then
  mv logs/nxt.log logs/nxt.log.bak
fi

nohup java -Dnxt.type=mainnet -Xmx784m -cp "classes:lib/*:conf" nxt.Nxt 1>/dev/null 2>&1 &
exit $?

Script to stop NRS (stop-nxt)
Code: [Select]
#!/bin/sh
#######################
# Stop the NRS server #
#######################

PID=`ps -f -u ubuntu | grep -v grep | grep nxt.type=mainnet | tr -s ' ' | cut -f 2 -d ' '`
if [ -z "$PID" ] ; then
  echo "NRS is not running"
  exit 1
fi
echo "Stopping NRS $PID"
kill $PID
exit 0

Script to display the NRS log (show-nxt)
Code: [Select]
#!/bin/sh
#########################################
# Show the last 50 lines of the NRS log #
#########################################

tail -n 50 /home/ubuntu/nxt/logs/nxt.log
exit $?


Script to compact the NRS database (compact-nxt)
Code: [Select]
#!/bin/sh
############################
# Compact the NRS database #
############################

cd /home/ubuntu/nxt

if [ -f logs/nxt.log.lck ] ; then
  echo "NRS is running"
  exit 1
fi

if [ -f logs/nxt.log ] ; then
  mv logs/nxt.log logs/nxt.log.bak
fi

java -Xmx768m -cp "classes:lib/*:conf" nxt.tools.CompactDatabase
exit $?

Script to start forging (start-forging).  You need to replace YOUR-SECRET-PHRASE with the secret phrase for the forging account.
Code: [Select]
#!/bin/sh
#################
# Start forging #
#################

SECRET='YOUR-SECRET-PHRASE'
curl --data "requestType=startForging" --data-urlencode "secretPhrase=$SECRET" http://localhost:7876/nxt
echo
exit $?
Title: Re: NRS v1.10.1
Post by: Riker on August 11, 2016, 12:10:09 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.
Title: Re: NRS v1.10.1
Post by: TheWireMaster on August 11, 2016, 12:23:02 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!
Title: Re: NRS v1.10.1
Post by: Riker on August 11, 2016, 01:23:01 pm
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!

If you connect to addresses localhost or 127.0.0.1 you won't get this message.
When using any other address we have to assume that your passphrase can be at risk when transported to the remote node or in case the remote node is hacked, therefore we warn you about this.
Use your best judgement. Setup an https connection and secure the access to your remote node.
Title: Re: NRS v1.10.1
Post by: ScripterRon on August 11, 2016, 02:02:25 pm
Thanks for the scripts, ScripterRon :-)
Regarding curl, it is not installed by default on Ubuntu 16.04, so I had to:
Code: [Select]
sudo apt-get update
sudo apt-get install curl
I assume that the NXT-account to forge is extracted from the secret phrase? If I have two NXT-accounts which I want to forge with on the same server, I can simply extend your script as follows:
Code: [Select]
#!/bin/sh
#################
# Start forging #
#################

SECRET1='YOUR-SECRET-PHRASE-ACCOUNT-1'
SECRET2='YOUR-SECRET-PHRASE-ACCOUNT-2'
curl --data "requestType=startForging" --data-urlencode "secretPhrase=$SECRET1" http://localhost:7876/nxt
curl --data "requestType=startForging" --data-urlencode "secretPhrase=$SECRET2" http://localhost:7876/nxt
echo
exit $?
The server update can now be automated:
Code: [Select]
./stop-nxt
wget https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.10.1.zip
rm -rf nxt/lib
unzip nxt-client-1.10.1.zip #(answer A for [A]ll)
./start-nxt
sleep 60
./start-forging
The blockchain and nxt.properties from the previous version remain in place after unzip.
Yes, the secret phrase specifies the account to be used as well as the private key used to sign generated blocks.

NRS does not stop immediately since it needs to wait for H2 to close the database.  So you need to wait before updating the code.  An easy check is to just wait until the nxt.log.lck file is removed.  Something like this:
Code: [Select]
until [ ! -f nxt/logs/nxt.log.lck ] ; do
  echo "Waiting for NRS to stop"
  sleep 15
done
Title: Re: NRS v1.10.1
Post by: TheWireMaster on August 11, 2016, 02:25:16 pm
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!

If you connect to addresses localhost or 127.0.0.1 you won't get this message.
When using any other address we have to assume that your passphrase can be at risk when transported to the remote node or in case the remote node is hacked, therefore we warn you about this.
Use your best judgement. Setup an https connection and secure the access to your remote node.

Hi Riker
I actually am connected to my localhost (http://localhost:7876/index.html)
But it looks like it's related to the settings I've changed to make my node a public node. When I go back to the default settings then I don't have those warnings.
This is the diff between the original and my properties file:
"
61c61
< nxt.myAddress=
---
> nxt.myAddress=mypublicIPaddress
67c67
< nxt.myHallmark=
---
> nxt.myHallmark=3dc6529a.............ba4a9359afc5ddd9ce
234c234
< nxt.allowedBotHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
---
> nxt.allowedBotHosts=*
244c244
< nxt.enableAPIUPnP=false
---
> nxt.enableAPIUPnP=true
249c249
< nxt.apiServerHost=127.0.0.1
---
> nxt.apiServerHost=0.0.0.0
365c365
< nxt.allowedUserHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
---
> nxt.allowedUserHosts=127.0.0.1; localhost; mypublicipaddress; [0:0:0:0:0:0:0:1];
"

Also with the modified properties file when I pass over the "Forging" status I get a message: "Cannot determine forging status, please define administrator password".

Does this make sense to you?

thanks

Title: Re: NRS v1.10.1
Post by: Butthead on August 11, 2016, 05:09:33 pm
Installed in Windows 10.

Worked and forging.
Title: Re: NRS v1.10.1
Post by: Jose 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.
Title: Re: NRS v1.10.1
Post by: martismartis on August 11, 2016, 06:48:21 pm
Please update forum header with link to 1.10.1 mandatory update.
Title: Re: NRS v1.10.1
Post by: Riker 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
Title: Re: NRS v1.10.1
Post by: TheWireMaster 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. :)
Title: MAC problem
Post by: neofelis 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?
Title: Re: MAC problem
Post by: PoofKnuckle 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?

Title: Re: NRS v1.10.1
Post by: Sebastien256 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:
(https://s3.postimg.org/v6mts765r/Capture.jpg) (https://postimg.org/image/v6mts765r/)

The thing with suffler and other is confusing and not need. Only the first sentence is fully adequate.
Title: Re: MAC problem
Post by: neofelis 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.

Title: Acct control issue
Post by: neofelis 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.

Title: Re: MAC problem
Post by: PoofKnuckle 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 (http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html)

That might set things straight for you.

Title: Re: NRS v1.10.1
Post by: ScripterRon 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).
Title: Re: NRS v1.10.1
Post by: ScripterRon 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).
Title: Re: NRS v1.10.1
Post by: Brangdon 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  (https://nxtforum.org/nxt-projects/email-notification-on-transactions/)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.
Title: Re: NRS v1.10.1
Post by: lurker10 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.
Title: Re: MAC problem
Post by: neofelis 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 (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.
Title: Re: NRS v1.10.1
Post by: kseistrup 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

 :)
Title: Re: NRS v1.10.1
Post by: beammeup 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
Title: Re: NRS v1.10.1
Post by: beammeup 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?
Title: Re: NRS v1.10.1
Post by: lurker10 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.
Title: Re: NRS v1.10.1
Post by: Peter2516 on August 17, 2016, 08:15:51 am
Doesn't forging start automatically anymore when you log into an account with the passphrase?
Seems you now have to click on the forging 'button' to start forging.
Title: Re: NRS v1.10.1
Post by: HCLivess on August 19, 2016, 11:27:46 am
will you use a different port?
Title: Re: NRS v1.10.1
Post by: Megalodon on August 22, 2016, 12:18:32 am

Doing a Start Funding Monitor to a node in the same LAN returns error message "secretPhrase not specified or not submitted to the remote node" in this version. Worked fine in previous versions. Anyway around this?
Title: Re: NRS v1.10.1
Post by: Riker on August 22, 2016, 07:44:56 pm
Doesn't forging start automatically anymore when you log into an account with the passphrase?
Seems you now have to click on the forging 'button' to start forging.

This is because of a bug https://nxtforum.org/nrs-releases/nrs-v1-10-1/msg223381/#msg223381 will be fixed in the next release.
Title: Re: NRS v1.10.1
Post by: Riker on August 22, 2016, 07:46:57 pm

Doing a Start Funding Monitor to a node in the same LAN returns error message "secretPhrase not specified or not submitted to the remote node" in this version. Worked fine in previous versions. Anyway around this?

This is because of the same bug https://nxtforum.org/nrs-releases/nrs-v1-10-1/msg223381/#msg223381 and since we do not send the passphrase to a remote node when starting a funding monitor which will be fixed in 1.10.2 since the remote node has to have the account passphrase in order to sign funding transactions.
For now your only option is to start the monitor using the API test page.
Title: Re: NRS v1.10.1
Post by: chevdor on August 22, 2016, 08:51:04 pm
The updated docker image took a tiny bit longer than usual but is now on its way:
https://nxtforum.org/general-discussion/nxt-in-a-docker-container/40/
Title: Re: NRS v1.10.1
Post by: CryptKeeper on August 24, 2016, 11:29:07 am
I've just noticed that the poll results for a followed poll aren't updating correctly.
I'm running NRS 1.10.1 on windows 10 and checked the browser and the desktop wallet, both show the same behavior. The results aren't even updating after I restarted the NRS server, very strange. If I count the votes on the list below (Votes Cast), these are correct but different to the numbers shown as poll results.

Is this a bug or is it just me?  :P
Title: Re: NRS v1.10.1
Post by: Riker on August 24, 2016, 01:36:59 pm
I've just noticed that the poll results for a followed poll aren't updating correctly.
I'm running NRS 1.10.1 on windows 10 and checked the browser and the desktop wallet, both show the same behavior. The results aren't even updating after I restarted the NRS server, very strange. If I count the votes on the list below (Votes Cast), these are correct but different to the numbers shown as poll results.

Is this a bug or is it just me?  :P

You mean 12/6 result when we have 21 votes ? I think it's because the min balance model requires 5K NXT and 3 of these accounts does not have 5K
Title: Re: NRS v1.10.1
Post by: CryptKeeper on August 24, 2016, 03:41:24 pm
I've just noticed that the poll results for a followed poll aren't updating correctly.
I'm running NRS 1.10.1 on windows 10 and checked the browser and the desktop wallet, both show the same behavior. The results aren't even updating after I restarted the NRS server, very strange. If I count the votes on the list below (Votes Cast), these are correct but different to the numbers shown as poll results.

Is this a bug or is it just me?  :P

You mean 12/6 result when we have 21 votes ? I think it's because the min balance model requires 5K NXT and 3 of these accounts does not have 5K

You are absolutely right, shame on me!  :-[

But why could I even vote if my balance was below 5000 NXT? IMHO the wallet should check that and show an error message to the user.
Title: Re: NRS v1.10.1
Post by: Riker on August 24, 2016, 07:55:14 pm
I've just noticed that the poll results for a followed poll aren't updating correctly.
I'm running NRS 1.10.1 on windows 10 and checked the browser and the desktop wallet, both show the same behavior. The results aren't even updating after I restarted the NRS server, very strange. If I count the votes on the list below (Votes Cast), these are correct but different to the numbers shown as poll results.

Is this a bug or is it just me?  :P

You mean 12/6 result when we have 21 votes ? I think it's because the min balance model requires 5K NXT and 3 of these accounts does not have 5K

You are absolutely right, shame on me!  :-[

But why could I even vote if my balance was below 5000 NXT? IMHO the wallet should check that and show an error message to the user.

Since the balances are only checked at the finish height of the poll
Title: Re: NRS v1.10.1
Post by: TheWireMaster on August 25, 2016, 11:11:26 am
I still have a strange behavior with my nrs client configured as public node. Every time I reconnect to that machine to check my NXT account, the node is not forging. It looks like it stops on its own, and it looks like it happens very often.
Is there a way to see from outside if my node is still forging besides the red dot in the client?
Title: Re: NRS v1.10.1
Post by: lurker10 on August 25, 2016, 11:25:41 am
I still have a strange behavior with my nrs client configured as public node. Every time I reconnect to that machine to check my NXT account, the node is not forging. It looks like it stops on its own, and it looks like it happens very often.
Is there a way to see from outside if my node is still forging besides the red dot in the client?

You can in http://localhost:7876/test?requestTag=FORGING   (getForging request)
This query requires submitting a passphrase for the account you would like to check status of. It's most likely submitted as plain text, meaning if you need to check it on a remote node, don't use it unless you run the node API on https:// and even then only submit passphrases for small balance accounts.
Title: Re: NRS v1.10.1
Post by: kpstolk on August 27, 2016, 12:30:28 pm
The Release 1.10.1 download is currently returning Access Denied?

<Error>
    <Code>AccessDenied</Code>
    <Message>Access Denied</Message>
    <RequestId>6AC4F9A462CF0B8B</RequestId>
    <HostId>
        6mxFr5XiLweheIGb4cGj1Bf9VxsW6LKfPtSJsJuVa3fFMFSP18X53PFC32xhLZFtQe9FrM8/qPY=
    </HostId>
</Error>
Title: Re: NRS v1.10.1
Post by: Peter2516 on August 27, 2016, 12:36:16 pm
Yep, maybe some hosting server troubles?
Title: Re: NRS v1.10.1
Post by: CryptKeeper on August 27, 2016, 12:56:57 pm
Downloads from bitbucket aren't working ATM!
I've filed a support request with the bitbucket support. If someone needs the NRS windows 1.10.1 exe, I've mirrored it here:
https://mega.nz/#!oY5hjLwL!LmkZ8geABYM5ZtUgAS_3Kc5buhYZFOnG6mi1KnRnWbw (https://mega.nz/#!oY5hjLwL!LmkZ8geABYM5ZtUgAS_3Kc5buhYZFOnG6mi1KnRnWbw)

UPDATE:
Bitbucket downloads are working again!
elective-stereophonic
elective-stereophonic
assembly
assembly