Skip to content

Releases: GoSimpleLLC/nbvcxz

1.5.1

29 Jan 06:45
607bb57
Compare
Choose a tag to compare

Release 1.5.1 brings a new maxLength configuration, and fixes for performance edge cases.

  • Max Length is 256 by default, but should be set to match your hash functions maximum if it has one.

1.5.0

03 Aug 16:12
Compare
Choose a tag to compare

Release 1.5.0 brings performance improvements for edge cases, improved thread safety, reduced memory usage, and more language support.

  • Add Chinese, Finnish, and Swedish language support
  • Improve memory churn when creating a new Nbvcxz() instead of reusing the object multiple times
  • Add automatic module name
  • Can now add a collection of words to the dictionaries at once rather than word-at-a-time
  • Improve Nbvcxz thread safety
  • Update cracking speed for different algorithms to match what's available today

1.4.3

04 Dec 16:10
Compare
Choose a tag to compare

Release 1.4.3 fixes some performance issues which could lead to extremely long estimation times, and adds some new features.

  • Add support for scaling the offline guess speeds by a hardware cost.
  • Set minimum entropy now is able to be set by passing in how much time you want an attack to take using a specific guess type.
  • There is now a getBasicScore() method on Result which emulates the zxcvbn score (0-4)

1.4.2

20 Jul 18:58
Compare
Choose a tag to compare

Release 1.4.2 adds support for using nbvcxz with Java 1.7+.

1.4.1

24 Mar 18:34
Compare
Choose a tag to compare

Release 1.4.1 improves some translations, as well as adds support for additional languages.

The new languages supported are:

  • Dutch (nl)
  • German (de)
  • Italian (it)
  • Telugu (te)

Thanks again to all who contributed their help with translation.

Other features in this release are...

  • Updated the guesses / second for offline modes to provide more accurate representation of current hardware.
  • Improvements to feedback. We now give more customized recommendations based on the analysis of the password.

1.4.0

29 Mar 13:38
Compare
Choose a tag to compare

Release 1.4.0 contains a few user visible features, most notably of which: Nbvcxz now supports 8 languages.

The languages supported are:

  • English (default)
  • French (fr)
  • Spanish (es)
  • Portuguese (pt)
  • Russian (ru)
  • Ukrainian (uk)
  • Afrikaans (af)
  • Hungarian (hu)

Thanks to all who contributed their help in translating.

Other features in this release are...

  • Default guesses/sec for offline guess types now have a Maintainer-hit-by-a-bus scaling mode.
    • In the case this library is no longer maintained (or you choose to stay on an old version of it), we will scale the existing values by Moore's law every year.
  • Feedback now returns a "result" text, letting the user know if their password met the minimum entropy or not.

1.3.4

27 Feb 18:42
Compare
Choose a tag to compare

Update the default hashing speed to reflect new advances in hardware in the last 8 months. ~$20k will buy you approximately 1.7x hashing power now than it would prior to the Nvidia Pascal release.

1.3.3

17 Feb 18:13
Compare
Choose a tag to compare

Release 1.3.3 - Fix for: #7

Exclusion dictionaries were not working as expected with partial words. They previously only matched if the value in the exclusion dictionary matched the entire password. Now they will match a portion of the password.

For example, if we added the users last name to an exclusion dictionary: Johnson
and their password was mylongjohnson, it previously wouldn't match that exclusion dictionary on the "johnson" portion of that password. Now it will (giving that portion of the password 0 bits of entropy).

I also added a new builder class for creating custom dictionaries, because they require all lower case words within them to work properly, so we need to make an easy way for users to do so. I also updated all javadoc comments to reflect that dictionaries need to contain lower case words.

1.3.2

09 Feb 18:19
Compare
Choose a tag to compare

Release 1.3.2 - Fix for: #6

Implemented a timeout for the findBestMatches algorithm which can be configured. If it exceeds the time specified, it will fallback to the findGoodEnoughMatches algorithm which is much faster, but also less likely to find the optimal match combination.

1.3.1

23 Dec 22:06
Compare
Choose a tag to compare

Hotfix for last release.