Here is version 2.1 of my Windows NXT client "NXT Solaris". Changelog-Compatibilty fixes for NRS 0.8.x
-Implemented Curve25519 algorithm:
* NXT Solaris is now a bit like "Electrum for NXT" (a thin client that does not download the complete blockchain, connecting to untrusted NRS nodes)
* It is now safe to connect to public NRS nodes (except for forging).
* As default, NXT Solaris no connects to a random public node.
* Currently a static list of public nodes that allow API calls from anyone from the text file public_nodes.txt is used.
* NRS and Java are now longer distributed with NRS Solaris.
* You will get a warning in the secret input dialog if the secret is transmitted over http to the remote NRS node (only with start/stop forging).
* If you want to forge, run your own NRS instance locally and set up NXT Solaris to connect to your instance.
-Since there is no batch mode in the NRS API:
* Details for peers are no longer retrieved as default
* A maximum of 50 (yet unkown) transactions per account are fetched from the NRS node whenever there is a new block
-Fixed null exchange rates when
www.cryptocoincharts.info is down
Download64-bit Version: NXTSolaris-v2.1-64bit.zip (29.6 MB) – Download
hereSHA256 checksum for NXTSolaris-v2.1-64bit.zip: C01599EA51599AD4E2EE8D0B1762686EB7EC274118658C43F76983957F76B0D7
32-bit Version: NXTSolaris-v2.1-32bit.zip (27.5 MB) – Download
hereSHA256 checksum for NXTSolaris-v2.1-32bit.zip: EAE75B046577E771CC2C8F57D2A4B8D9AF9F87F92FE5CD400DDE9F9755589957
For more screenshots and everything else please visit:
http://nxtsolaris.wordpress.com/InstallationSimply unzip the archive and run the NXTSolarisStarter.exe file.
The current version 2.1 is NOT compatible with the previous versions. Please delete any existing files and extract the zip archive to a new directory.
Roadmap1.) Move current version of my code to XE5 and release closed source 32-bit and 64-bit versions for Windows. [DONE]
2.) Refactor code to a MVC architecture, so that I can create separate GUIs while using the same version of the business logic code. [DONE]
3.) Create new GUIs for Windows and OS X using the same business logic, but based on the cross-platform Firemonkey libraries. [DONE]
4.) Release Windows version (32 and 64 bit) based on FireMonkey. [DONE]
5.) Implement new features from the TODO list [DONE]
6.) Release source-code for FireMonkey Windows version (February 16th, 2014 latest) [DONE]
7.) Implement new features from the TODO list8.) OSX compatibility changes
9.) Release OSX version based on FireMonkey.
10.) Release source code for FireMonkey OSX version.
TODO list-Arbitrary message encryption
-Offer a simple and advanced GUI, with the simple GUI targeted at new users
-Implement client side Curve25519 encryption/signingDonationsI hope you like my client and I’d be extremely happy to see some donations for the future of this project!
NXT: 1758531264253431177
Fantastic great jobmust encourage any client developer to implement 2 factor authenticationTwo-step verification is a process involving two stages to verify the identity of an entity trying to access services in a computer or in a network. This is a special case of a multi-factor authentication which might involve only one of the three authentication factors (a knowledge factor, a possession factor, and an inherence factor) for both steps.[1][2][3] If each step involves a different authentication factor then the two-step authentication is additionally two-factor authentication.
Contents [hide]
1 Example
2 Google's two-step verification process
3 Other sites offering two-step verification service
4 References
Example[edit]
To provide an everyday example: an automated teller machine (ATM) typically requires two-factor verification. To prove that users are who they claim to be, the system requires two items: an ATM smartcard (application of the possession factor) and the personal identification number (PIN) (application of the knowledge factor). In the case of a lost ATM card, the user's accounts are still safe; anyone who finds the card cannot withdraw money as they do not know the PIN. The same is true if the attacker has only knowledge of the PIN and does not have the card. This is what makes two-factor verification more secure: there are two factors required in order to authenticate.
Note that if the ATM smartcard is merely a magnetic-stripe card it is copyable then the process is only two-step authentication but not two-factor authentication since the ATM is only verifying that the user knows the data encoded on the magnetic stripe (knowledge factor) and presented it in magnetic-stripe form. A smartcard with a chip performs a challenge/response authentication; the information transmitted from the card to the ATM is not the information required to duplicate the card's abilities.
Google's two-step verification process[edit]
Google was one of the first Internet companies which introduced a two-step verification process.[4] To access a Google service using the two-step verification process, a user has to go through the following two stages:[5][6]
The first step is to log in using the username and password. This is an application of the knowledge factor.
The implementation of the second step requires a mobile phone or the Google Authenticator application, which is an application of the knowledge factor. If the user opts to use a mobile phone, he/she has to register his/her phone number with Google. When one attempts to authenticate with username and password, Google will send via SMS a new, unique code to the phone. Receiving the SMS demonstrates that the user knows the phone's IMEI, which is sufficient to convince the phone network to direct the SMS to the attacker.
If the user opts to use the Google Authenticator (or another supported code generator application),[7] he/she simply opens the application, which generates a new code every 30 seconds. This code is to be entered to complete the log in process. As a backup option in case the registered mobile phone or device running Google Authenticator is lost, stolen, or otherwise unavailable, the user can print a set of static single-use backup codes (also the knowledge factor) and store them in a safe place.