Approaching 0.2.3

After almost exactly four months into the making, it should soon be time for Pyrit 0.2.3.

In order get 0.2.3 on the road before/around Black Hat and defcon, I have decided to cut out the network functionality and delay it until 0.2.4. Right now I want to focus on stability and (yes!) some documentation… Please report any errors and glitches you might find in the svn repository.

Some of the changes since 0.2.2:
* Added CLI-function ‘delete_essid’
* Added CLI-function ‘verify’
* Added CLI-function ‘selftest’
* Added Core for OpenCL
* Added SSE2-path to CPU-Core
* Added docstrings to the code
* Fixed ‘CUDA_ERROR_INVALID_IMAGE’ when using CUDA 2.2
* Fixed process exit codes
* Improved scheduling between client and hardware
* Improved storage-code
* Improved performance for almost all CLI-functions
* Builds from SVN-directories now carry their revision-number

Changes since 0.2.2:
* Added docstrings
* Added CLI-function 'delete_essid'
* Added CLI-function 'verify'
* Added CLI-function 'selftest'
* Added Core for OpenCL
* Added SSE2-path to CPU-Core
* Fixed 'CUDA_ERROR_INVALID_IMAGE' when using CUDA 2.2
* Fixed process exit codes
* Improved scheduling between client and hardware
* Improved storage-code
* Improved performance for almost all CLI-functions
* Builds from SVN-directories now carry their revision-number

1 Comment

  1. […] from the *much* improved source-code, the more or less visible changes are already described here. There is also a lot of new documentation for Installation, Usage and […]


Comments RSS TrackBack Identifier URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

  • RSS Unknown Feed

    • An error has occurred; the feed is probably down. Try again later.