Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on November 28, 2016, 12:02:48 pm

Title: NRS v1.11.1e
Post by: Jean-Luc on November 28, 2016, 12:02:48 pm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.11.1e

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

sha256:

d21b5055bec47bce21b4db7b346354dfcf2fa182bce4262a951ebe906866333f  nxt-client-1.11.1e.zip

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

sha256:

63025295af640e48df024551cdcfb9ea4cceb528839c8953690c988b51439a2f  nxt-client-1.11.1e.sh

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

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

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


Change log:

Implemented "Store Remembered Passphrase" setting in the device settings page.
When checked, the client stores the remembered passphrase in the local browser
settings or mobile app settings so that the next time the client is launched
it will login in automatically.
For the mobile app this setting defaults to true. In other configurations it
defaults to false. The stored passphrase is deleted when logging out of the
wallet.

Desktop Application now supports request confirmations when running as light or
roaming client.

Sign Transaction modal now signs the transaction bytes on the client side.

When the mobile app cannot connect to a randomly selected remote node, it will
popup the device settings modal to allow the user to configure a specific node.

When the mobile device is offline, the device settings modal allows signing
transactions and generating tokens to support cold storage functionality.

Additional client side bug fixes and refactoring.

Updated Jetty to version 9.3.14 and H2 to version 1.4.193, delete the old lib
folder before unpacking on top.

Updated localization component i18next to version 3.4.4

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

iQIcBAEBCgAGBQJYO/nUAAoJENqvaxkWiP4Z1uYP/117WCT4ekCUJrbkH7hrl4oY
swmQSUwjI1ZwugtrQ6H+6wEcWQ9daXdvumANQMzknFDG/L1L1urNxWT1u7vp0OdB
kyuPK5vcVO0j3Pf9kqqYbb8qDWMWgUFrLKRG6952f6YCv8TaPp+AqIYKhNkuj7Oy
OlVNjXXCWJeFrkoicYUBfkBnTeB2iAdQ7vHZYcgiYQ4mf4F/vP7N0VDpH6oEP3KN
y1Ou+6BMKVsvS+Y6NV3mLWYm7/3Dr6sDp3hZ2fm8scw5c8EB0wBKXUjUcccb7km8
xXX39r2UGoaP0uI14jcjxCC0sKLAoP2MN8QwgxZslozTnDc+gyodD+knJB6O9B7+
1TTpR2VfxEP6tPurDZw8MK3Q2LRqBP/2k+OfFYwMHUeAKnz9fUc/r1XYH9xzZ0DR
T9Ik/gQLyFdiBi4FC84TRlVbEnZw4igz62MUiTPpaAzu8oxnNBBnV4KZWjMQzccF
CxmOgSS5nOKeyXHylg8TQuoHRFhV4l+SG/3Crt6txans8z0PzEW+4HQPd86mR6Ey
0iV27kDxGaL2JqUiMxXK6FaYzxnCVMDza5C43+kFeJRtRYw9C/+mSYv+TCFZi2E6
wPV9DUR9zy+ziEKLOPs1TsdT86KEENl03lpX5EQ0Z4O7cVEOG0xSJ0a+N9/H4tuu
pUmCKATWbdjWXgunmIvZ
=SSWW
-----END PGP SIGNATURE-----
Title: Re: NRS v1.11.1e
Post by: Riker on November 28, 2016, 12:19:23 pm
Mobile app packages:

Android:
https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-mobile-client-android-1.11.1.0e.apk

sha256:
4906d5b050896f31d746660366b7da53aeeed79abc7ebd7ffa6ebbb1d65b8c16

i/OS:

Only available from ionic view

Android and i/OS packages were uploaded to ionic view, as explained in the NXT Wiki page https://nxtwiki.org/wiki/Mobile_App
Title: Re: NRS v1.11.1e
Post by: Riker on November 28, 2016, 12:39:03 pm
The problem which prevented the desktop application from opening up without a refresh has been fixed on the Windows release and Linux releases by down grading the Java version since it was caused by a regression problem in Java 1.8.0_111

For the Mac release the problem still exists, it will be fixed in the next release so no need to report it now. To workaround it, choose "Refresh Wallet" from the tray icon after starting the server.
Title: Re: NRS v1.11.1e
Post by: yassin54 on November 28, 2016, 01:18:28 pm
Thank you!! :)
Tweeted : https://twitter.com/NxtCommunity/status/803226325301465088 ;)
Title: Re: NRS v1.11.1e
Post by: lurker10 on November 28, 2016, 02:02:16 pm
Good job!

Should a new configuration option (disabled by default) be added for experienced users of the mobile app to allow connecting to nodes with a self-signed SSL, skipping the SSL validity check but still using https for communication? Perhaps the option should be coupled with selection of a specific trusted node, validity check of SSL on one's own node can be safely skipped.
Title: Re: NRS v1.11.1e
Post by: martismartis on November 28, 2016, 03:03:29 pm
Sometimes I get just blue screen in browser, without login section. After few refreshes I can see login fields. Here is an console log of Chrome:

Code: [Select]
Failed to load resource: the server responded with a status of 404 (Not Found)
jquery.js:9064 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.send @ jquery.js:9064
nrs.js:1742 document.ready
nrs.js:153 Spinner initialized
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_check_remember_me = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_simulate_app = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_testnet = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.remote_node_address =
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.remote_node_port = 7876
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_remote_node_ssl = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.validators_count = 3
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.bootstrap_nodes_count = 5
nrs.js:185 load server constants
nrs.console.js:39 2016-11-28T16:49:53 Send request getConstants to url /nxt?requestType=getConstants
nrs.constants.js:113 done loading server constants
nrs.js:190 calling getState
nrs.console.js:39 2016-11-28T16:49:54 Send request getState to url /nxt?requestType=getState
nrs.js:194 getState response received
nrs.console.js:39 2016-11-28T16:49:54 Send request getPlugins to url /nxt?requestType=getPlugins
nrs.console.js:39 2016-11-28T16:49:54 navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
nrs.console.js:39 2016-11-28T16:49:54 navigator.platform = Win32
nrs.console.js:39 2016-11-28T16:49:54 navigator.appVersion = 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
nrs.console.js:39 2016-11-28T16:49:54 navigator.appName = Netscape
nrs.console.js:39 2016-11-28T16:49:54 navigator.appCodeName = Mozilla
nrs.console.js:39 2016-11-28T16:49:54 navigator.hardwareConcurrency = 4
nrs.console.js:39 2016-11-28T16:49:54 navigator.maxTouchPoints = 0
nrs.console.js:39 2016-11-28T16:49:54 navigator.languages = en-US,en,lt,ru
nrs.console.js:39 2016-11-28T16:49:54 navigator.language = en-US
nrs.console.js:39 2016-11-28T16:49:54 navigator.userLanguage = undefined
nrs.console.js:39 2016-11-28T16:49:54 navigator.cookieEnabled = true
nrs.console.js:39 2016-11-28T16:49:54 navigator.onLine = true
nrs.console.js:39 2016-11-28T16:49:54 NRS.isTestNet = false
nrs.console.js:39 2016-11-28T16:49:54 NRS.needsAdminPassword = true
nrs.js:238 getState response processed
nrs.js:244 continue initialization
nrs.plugins.js:196 Uncaught TypeError: $.t is not a function
    at http://192.168.0.150:7876/js/nrs.plugins.js:196:26
    at Object.<anonymous> (http://192.168.0.150:7876/js/nrs.server.js:456:25)
    at fire (http://192.168.0.150:7876/js/3rdparty/jquery.js:3187:31)
    at Object.fireWith [as resolveWith] (http://192.168.0.150:7876/js/3rdparty/jquery.js:3317:7)
    at Object.then.failureArgs (http://192.168.0.150:7876/js/3rdparty/ajaxretry.js:101:12)
    at Object.<anonymous> (http://192.168.0.150:7876/js/3rdparty/jquery.js:3366:33)
    at fire (http://192.168.0.150:7876/js/3rdparty/jquery.js:3187:31)
    at Object.fireWith [as resolveWith] (http://192.168.0.150:7876/js/3rdparty/jquery.js:3317:7)
    at done (http://192.168.0.150:7876/js/3rdparty/jquery.js:8757:14)
    at XMLHttpRequest.<anonymous> (http://192.168.0.150:7876/js/3rdparty/jquery.js:9123:9)
nrs.settings.js:459 Uncaught (in promise) TypeError: $.t is not a function
    at Object.NRS.createRegionalFormatSelect (http://192.168.0.150:7876/js/nrs.settings.js:459:65)
    at Object.NRS.getSettings (http://192.168.0.150:7876/js/nrs.settings.js:474:8)
    at http://192.168.0.150:7876/js/nrs.js:271:9
Title: Re: NRS v1.11.1e
Post by: box1413 on November 28, 2016, 10:15:45 pm
going to test it out on testnet.
Title: Re: NRS v1.11.1e
Post by: box1413 on November 28, 2016, 10:48:21 pm
getting these errors. not sure what it means address already in use. How do resolve this?

Quote
2016-11-28 16:47:02 SEVERE: Errors running startup tasks:
java.net.BindException: Address already in use
java.net.BindException: Address already in use

java.lang.RuntimeException: Errors running startup tasks:
java.net.BindException: Address already in use
java.net.BindException: Address already in use

        at nxt.util.ThreadPool.runAll(ThreadPool.java:150)
        at nxt.util.ThreadPool.start(ThreadPool.java:78)
        at nxt.Nxt$Init.<clinit>(Nxt.java:383)
        at nxt.Nxt.init(Nxt.java:312)
        at nxt.Nxt.main(Nxt.java:299)
2016-11-28 16:47:02 INFO: Shutting down...
2016-11-28 16:47:02 INFO: nxt.maxNumberOfMonitors = "100"
2016-11-28 16:47:02 INFO: shutting down sendingService
2016-11-28 16:47:02 INFO: shutting down peersService
2016-11-28 16:47:03 INFO: Database shutdown completed
2016-11-28 16:47:03 INFO: Nxt server 1.11.1e stopped.
Title: Re: NRS v1.11.1e
Post by: squidgle on November 28, 2016, 11:50:13 pm
updated my node. seems good so far. keep up the good work!
Title: Re: NRS v1.11.1e
Post by: qq2536007339 on November 29, 2016, 05:39:16 am
Update my testnet,so far so good.
Title: Re: NRS v1.11.1e
Post by: Riker on November 30, 2016, 11:06:00 am
Sometimes I get just blue screen in browser, without login section. After few refreshes I can see login fields. Here is an console log of Chrome:

Code: [Select]
Failed to load resource: the server responded with a status of 404 (Not Found)
jquery.js:9064 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.send @ jquery.js:9064
nrs.js:1742 document.ready
nrs.js:153 Spinner initialized
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_check_remember_me = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_simulate_app = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_testnet = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.remote_node_address =
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.remote_node_port = 7876
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_remote_node_ssl = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.validators_count = 3
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.bootstrap_nodes_count = 5
nrs.js:185 load server constants
nrs.console.js:39 2016-11-28T16:49:53 Send request getConstants to url /nxt?requestType=getConstants
nrs.constants.js:113 done loading server constants
nrs.js:190 calling getState
nrs.console.js:39 2016-11-28T16:49:54 Send request getState to url /nxt?requestType=getState
nrs.js:194 getState response received
nrs.console.js:39 2016-11-28T16:49:54 Send request getPlugins to url /nxt?requestType=getPlugins
nrs.console.js:39 2016-11-28T16:49:54 navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
nrs.console.js:39 2016-11-28T16:49:54 navigator.platform = Win32
nrs.console.js:39 2016-11-28T16:49:54 navigator.appVersion = 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
nrs.console.js:39 2016-11-28T16:49:54 navigator.appName = Netscape
nrs.console.js:39 2016-11-28T16:49:54 navigator.appCodeName = Mozilla
nrs.console.js:39 2016-11-28T16:49:54 navigator.hardwareConcurrency = 4
nrs.console.js:39 2016-11-28T16:49:54 navigator.maxTouchPoints = 0
nrs.console.js:39 2016-11-28T16:49:54 navigator.languages = en-US,en,lt,ru
nrs.console.js:39 2016-11-28T16:49:54 navigator.language = en-US
nrs.console.js:39 2016-11-28T16:49:54 navigator.userLanguage = undefined
nrs.console.js:39 2016-11-28T16:49:54 navigator.cookieEnabled = true
nrs.console.js:39 2016-11-28T16:49:54 navigator.onLine = true
nrs.console.js:39 2016-11-28T16:49:54 NRS.isTestNet = false
nrs.console.js:39 2016-11-28T16:49:54 NRS.needsAdminPassword = true
nrs.js:238 getState response processed
nrs.js:244 continue initialization
nrs.plugins.js:196 Uncaught TypeError: $.t is not a function
    at http://192.168.0.150:7876/js/nrs.plugins.js:196:26
    at Object.<anonymous> (http://192.168.0.150:7876/js/nrs.server.js:456:25)
    at fire (http://192.168.0.150:7876/js/3rdparty/jquery.js:3187:31)
    at Object.fireWith [as resolveWith] (http://192.168.0.150:7876/js/3rdparty/jquery.js:3317:7)
    at Object.then.failureArgs (http://192.168.0.150:7876/js/3rdparty/ajaxretry.js:101:12)
    at Object.<anonymous> (http://192.168.0.150:7876/js/3rdparty/jquery.js:3366:33)
    at fire (http://192.168.0.150:7876/js/3rdparty/jquery.js:3187:31)
    at Object.fireWith [as resolveWith] (http://192.168.0.150:7876/js/3rdparty/jquery.js:3317:7)
    at done (http://192.168.0.150:7876/js/3rdparty/jquery.js:8757:14)
    at XMLHttpRequest.<anonymous> (http://192.168.0.150:7876/js/3rdparty/jquery.js:9123:9)
nrs.settings.js:459 Uncaught (in promise) TypeError: $.t is not a function
    at Object.NRS.createRegionalFormatSelect (http://192.168.0.150:7876/js/nrs.settings.js:459:65)
    at Object.NRS.getSettings (http://192.168.0.150:7876/js/nrs.settings.js:474:8)
    at http://192.168.0.150:7876/js/nrs.js:271:9

Did you get this message once after the upgrade or is it still reproducible?
Are you running any plugins?
Title: Re: NRS v1.11.1e
Post by: Riker on November 30, 2016, 11:08:08 am
getting these errors. not sure what it means address already in use. How do resolve this?

Quote
2016-11-28 16:47:02 SEVERE: Errors running startup tasks:
java.net.BindException: Address already in use
java.net.BindException: Address already in use

java.lang.RuntimeException: Errors running startup tasks:
java.net.BindException: Address already in use
java.net.BindException: Address already in use

        at nxt.util.ThreadPool.runAll(ThreadPool.java:150)
        at nxt.util.ThreadPool.start(ThreadPool.java:78)
        at nxt.Nxt$Init.<clinit>(Nxt.java:383)
        at nxt.Nxt.init(Nxt.java:312)
        at nxt.Nxt.main(Nxt.java:299)
2016-11-28 16:47:02 INFO: Shutting down...
2016-11-28 16:47:02 INFO: nxt.maxNumberOfMonitors = "100"
2016-11-28 16:47:02 INFO: shutting down sendingService
2016-11-28 16:47:02 INFO: shutting down peersService
2016-11-28 16:47:03 INFO: Database shutdown completed
2016-11-28 16:47:03 INFO: Nxt server 1.11.1e stopped.

Most likely, you still have another NXT node running and listening on the same address
Title: Re: NRS v1.11.1e
Post by: Riker on November 30, 2016, 11:27:08 am
Good job!

Should a new configuration option (disabled by default) be added for experienced users of the mobile app to allow connecting to nodes with a self-signed SSL, skipping the SSL validity check but still using https for communication? Perhaps the option should be coupled with selection of a specific trusted node, validity check of SSL on one's own node can be safely skipped.

The problem is that Android webview won't allow an ajax connection over Https to a site which has a self signed certificate.
I can't find a workaround for this.

If you connect from a browser URL you can ignore the certificate warning.
If you connect from Java code you can trust all certificates.
But if you connect from an Android webview using ajax like we do, there is no workaround.

Perhaps you can try to import the site certificate into your mobile device certificates as explained here:
http://stackoverflow.com/questions/4461360/how-to-install-trusted-ca-certificate-on-android-device
https://www.globalsign.com/en/blog/installing-certificates-onto-android-devices/

If you make it work, would be nice if you can share which method has worked for you.
Title: Re: NRS v1.11.1e
Post by: martismartis on November 30, 2016, 12:09:27 pm
Sometimes I get just blue screen in browser, without login section. After few refreshes I can see login fields. Here is an console log of Chrome:

Code: [Select]
Failed to load resource: the server responded with a status of 404 (Not Found)
jquery.js:9064 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.send @ jquery.js:9064
nrs.js:1742 document.ready
nrs.js:153 Spinner initialized
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_check_remember_me = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_simulate_app = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_testnet = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.remote_node_address =
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.remote_node_port = 7876
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.is_remote_node_ssl = false
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.validators_count = 3
nrs.console.js:39 2016-11-28T16:49:53 NRS.mobileSettings.bootstrap_nodes_count = 5
nrs.js:185 load server constants
nrs.console.js:39 2016-11-28T16:49:53 Send request getConstants to url /nxt?requestType=getConstants
nrs.constants.js:113 done loading server constants
nrs.js:190 calling getState
nrs.console.js:39 2016-11-28T16:49:54 Send request getState to url /nxt?requestType=getState
nrs.js:194 getState response received
nrs.console.js:39 2016-11-28T16:49:54 Send request getPlugins to url /nxt?requestType=getPlugins
nrs.console.js:39 2016-11-28T16:49:54 navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
nrs.console.js:39 2016-11-28T16:49:54 navigator.platform = Win32
nrs.console.js:39 2016-11-28T16:49:54 navigator.appVersion = 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
nrs.console.js:39 2016-11-28T16:49:54 navigator.appName = Netscape
nrs.console.js:39 2016-11-28T16:49:54 navigator.appCodeName = Mozilla
nrs.console.js:39 2016-11-28T16:49:54 navigator.hardwareConcurrency = 4
nrs.console.js:39 2016-11-28T16:49:54 navigator.maxTouchPoints = 0
nrs.console.js:39 2016-11-28T16:49:54 navigator.languages = en-US,en,lt,ru
nrs.console.js:39 2016-11-28T16:49:54 navigator.language = en-US
nrs.console.js:39 2016-11-28T16:49:54 navigator.userLanguage = undefined
nrs.console.js:39 2016-11-28T16:49:54 navigator.cookieEnabled = true
nrs.console.js:39 2016-11-28T16:49:54 navigator.onLine = true
nrs.console.js:39 2016-11-28T16:49:54 NRS.isTestNet = false
nrs.console.js:39 2016-11-28T16:49:54 NRS.needsAdminPassword = true
nrs.js:238 getState response processed
nrs.js:244 continue initialization
nrs.plugins.js:196 Uncaught TypeError: $.t is not a function
    at http://192.168.0.150:7876/js/nrs.plugins.js:196:26
    at Object.<anonymous> (http://192.168.0.150:7876/js/nrs.server.js:456:25)
    at fire (http://192.168.0.150:7876/js/3rdparty/jquery.js:3187:31)
    at Object.fireWith [as resolveWith] (http://192.168.0.150:7876/js/3rdparty/jquery.js:3317:7)
    at Object.then.failureArgs (http://192.168.0.150:7876/js/3rdparty/ajaxretry.js:101:12)
    at Object.<anonymous> (http://192.168.0.150:7876/js/3rdparty/jquery.js:3366:33)
    at fire (http://192.168.0.150:7876/js/3rdparty/jquery.js:3187:31)
    at Object.fireWith [as resolveWith] (http://192.168.0.150:7876/js/3rdparty/jquery.js:3317:7)
    at done (http://192.168.0.150:7876/js/3rdparty/jquery.js:8757:14)
    at XMLHttpRequest.<anonymous> (http://192.168.0.150:7876/js/3rdparty/jquery.js:9123:9)
nrs.settings.js:459 Uncaught (in promise) TypeError: $.t is not a function
    at Object.NRS.createRegionalFormatSelect (http://192.168.0.150:7876/js/nrs.settings.js:459:65)
    at Object.NRS.getSettings (http://192.168.0.150:7876/js/nrs.settings.js:474:8)
    at http://192.168.0.150:7876/js/nrs.js:271:9

Did you get this message once after the upgrade or is it still reproducible?
Are you running any plugins?

After upgrade it worked normally, then suddenly not. Can't reproduce it now, but if it will happen again, I'll look what is in console.
And no, I do not run any plugins.
Title: Re: NRS v1.11.1e
Post by: Riker on November 30, 2016, 01:23:19 pm
Good job!

Should a new configuration option (disabled by default) be added for experienced users of the mobile app to allow connecting to nodes with a self-signed SSL, skipping the SSL validity check but still using https for communication? Perhaps the option should be coupled with selection of a specific trusted node, validity check of SSL on one's own node can be safely skipped.

The problem is that Android webview won't allow an ajax connection over Https to a site which has a self signed certificate.
I can't find a workaround for this.

If you connect from a browser URL you can ignore the certificate warning.
If you connect from Java code you can trust all certificates.
But if you connect from an Android webview using ajax like we do, there is no workaround.

Perhaps you can try to import the site certificate into your mobile device certificates as explained here:
http://stackoverflow.com/questions/4461360/how-to-install-trusted-ca-certificate-on-android-device
https://www.globalsign.com/en/blog/installing-certificates-onto-android-devices/

If you make it work, would be nice if you can share which method has worked for you.

I found a possible solution for this explained here http://ivancevich.me/articles/ignoring-invalid-ssl-certificates-on-cordova-android-ios/ and https://www.ibm.com/developerworks/community/blogs/mobileblog/entry/apache_cordova_working_with_certificates_on_android?lang=en
I'll give it a try sometime. Perhaps can implement this for the next release.
Title: Re: NRS v1.11.1e
Post by: lurker10 on November 30, 2016, 02:48:32 pm
Good job!

Should a new configuration option (disabled by default) be added for experienced users of the mobile app to allow connecting to nodes with a self-signed SSL, skipping the SSL validity check but still using https for communication? Perhaps the option should be coupled with selection of a specific trusted node, validity check of SSL on one's own node can be safely skipped.

The problem is that Android webview won't allow an ajax connection over Https to a site which has a self signed certificate.
I can't find a workaround for this.

If you connect from a browser URL you can ignore the certificate warning.
If you connect from Java code you can trust all certificates.
But if you connect from an Android webview using ajax like we do, there is no workaround.

Perhaps you can try to import the site certificate into your mobile device certificates as explained here:
http://stackoverflow.com/questions/4461360/how-to-install-trusted-ca-certificate-on-android-device
https://www.globalsign.com/en/blog/installing-certificates-onto-android-devices/

If you make it work, would be nice if you can share which method has worked for you.

I found a possible solution for this explained here http://ivancevich.me/articles/ignoring-invalid-ssl-certificates-on-cordova-android-ios/ and https://www.ibm.com/developerworks/community/blogs/mobileblog/entry/apache_cordova_working_with_certificates_on_android?lang=en
I'll give it a try sometime. Perhaps can implement this for the next release.

It would be awesome, thank you!
elective-stereophonic
elective-stereophonic
assembly
assembly