Skip to content

Commit

Permalink
chore: Updated changelog
Browse files Browse the repository at this point in the history 
Signed-off-by: UncleSp1d3r <[email protected]>
  • Loading branch information
@unclesp1d3r
unclesp1d3r committed Sep 13, 2024
1 parent b11aed6 commit d6950f2
Show file tree
Hide file tree
Showing 3 changed files with 518 additions and 291 deletions.
106 changes: 85 additions & 21 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
@@ -1,3 +1,25 @@

<a name="v0.5.4"></a>

## [v0.5.4](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.5.3...v0.5.4)

> 2024-09-12
### Code Refactoring

* Heavily cleanup and optimization.

* Refactored the agentClient


### Features

* Added initial Windows client support

This is very experimental and has not been adequately tested. Since we haven’t tested it, use caution in this version. I firmly recommend not using the legacy device detection mode.



<a name="v0.5.3"></a>

## [v0.5.3](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.5.2...v0.5.3)
Expand All @@ -8,6 +30,7 @@

* Finished enabling support for opencl-devices


### Code Refactoring

* Code changes to try and make golangci-lint happy
Expand All @@ -16,18 +39,18 @@

* Minor code cleanup


### Features

* Devices are now identified using hashcat rather than a brittle shell script

The system now runs a tiny attack job upon the agent’s startup, which verifies that the hashcat is working correctly
and then identifies the devices detected by the hashcat. This is much more accurate than the legacy technique since it
conforms to what hashcat will actually use.
The system now runs a tiny attack job upon the agent’s startup, which verifies that the hashcat is working correctly and then identifies the devices detected by the hashcat. This is much more accurate than the legacy technique since it conforms to what hashcat will actually use.

* Added automatic hashcat capability

The hashcat session will be stored in the data directory, and if one is detected, it will automatically attempt to
resume it when starting the attack. When the attack is complete, the restore file will be removed.
The hashcat session will be stored in the data directory, and if one is detected, it will automatically attempt to resume it when starting the attack. When the attack is complete, the restore file will be removed.



<a name="v0.5.2"></a>

Expand All @@ -39,13 +62,13 @@

* Fixed an issue causing SegFaults on weird HTTP errors

There was a condition where an HTTP error outside of the 4XX and 5XX range could cause a seg fault. I added more error
checking to ensure that it only throws a verbose error and doesn’t crash the agent.
There was a condition where an HTTP error outside of the 4XX and 5XX range could cause a seg fault. I added more error checking to ensure that it only throws a verbose error and doesn’t crash the agent.

* Fixed an issue causing SegFaults on weird HTTP errors

There was a condition where an HTTP error outside of the 4XX and 5XX range could cause a seg fault. I added more error
checking to ensure that it only throws a verbose error and doesn’t crash the agent.
There was a condition where an HTTP error outside of the 4XX and 5XX range could cause a seg fault. I added more error checking to ensure that it only throws a verbose error and doesn’t crash the agent.



<a name="v0.5.1"></a>

Expand All @@ -57,6 +80,8 @@

* Added significant error checking to client to prevent nil crashes



<a name="v0.5.0"></a>

## [v0.5.0](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.4.2...v0.5.0)
Expand All @@ -67,6 +92,8 @@

* Added support for mask list files from v0.5.0 of API



<a name="v0.4.2"></a>

## [v0.4.2](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.4.1...v0.4.2)
Expand All @@ -79,10 +106,13 @@

The API was refactored, introducing breaking changes in the SDK, so we needed to rename some packages and objects.


### Code Refactoring

* Minor cleanup to meet formatting standards



<a name="v0.4.1"></a>

## [v0.4.1](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.4.0...v0.4.1)
Expand All @@ -93,10 +123,9 @@

* Automatic benchmark now performs all hash types

Since the benchmarking function determines what hash types this agent supports, we needed to change the feature to
benchmark all hash types, not just the common ones. The agent’s initial startup is significantly slower now but
supports more functionality. This can be turned off by setting `enable_additional_hash_types: false` in the agent
config.
Since the benchmarking function determines what hash types this agent supports, we needed to change the feature to benchmark all hash types, not just the common ones. The agent’s initial startup is significantly slower now but supports more functionality. This can be turned off by setting `enable_additional_hash_types: false` in the agent config.



<a name="v0.4.0"></a>

Expand All @@ -110,8 +139,9 @@

This enables running tasks to be notified of hashes cracked in another task and pause tasks currently running.

We also added support for using a shared directory as a zap synchronization point. If configured, cracked hashes will be
written to a directory, and the client will monitor that directory for new zaps.
We also added support for using a shared directory as a zap synchronization point. If configured, cracked hashes will be written to a directory, and the client will monitor that directory for new zaps.



<a name="v0.3.1"></a>

Expand All @@ -123,6 +153,8 @@ written to a directory, and the client will monitor that directory for new zaps.

* Tasks are accepted before the downloads start



<a name="v0.3"></a>

## [v0.3](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.2.8...v0.3)
Expand All @@ -133,19 +165,21 @@ written to a directory, and the client will monitor that directory for new zaps.

* Fixed issue with always_use_native_hashcat on server messing up the client

When the server setting was set for the agent, the agent was not finding hashcat, but also not allowing it to be set
via config or environment variable.
When the server setting was set for the agent, the agent was not finding hashcat, but also not allowing it to be set via config or environment variable.

* Removed exessive output in standard debugging

* Files directory can be set separate of the data dir

* Replaced tail library with one still maintained


### Features

* Add support for zaps



<a name="v0.2.8"></a>

## [v0.2.8](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.2.7...v0.2.8)
Expand All @@ -156,6 +190,8 @@ written to a directory, and the client will monitor that directory for new zaps.

* Added more checking for null tasks or attacks



<a name="v0.2.7"></a>

## [v0.2.7](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.2.6...v0.2.7)
Expand All @@ -166,6 +202,8 @@ written to a directory, and the client will monitor that directory for new zaps.

* Moved utility code out of agentClient.go



<a name="v0.2.6"></a>

## [v0.2.6](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.2.5...v0.2.6)
Expand All @@ -176,6 +214,8 @@ written to a directory, and the client will monitor that directory for new zaps.

* Correctly handle when a running task is deleted



<a name="v0.2.5"></a>

## [v0.2.5](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.2.4...v0.2.5)
Expand All @@ -186,8 +226,9 @@ written to a directory, and the client will monitor that directory for new zaps.

* Fix incorrect status and benchmark output

The benchmark was incorrectly sending the time in ms to complete a hash instead of the number of hashes per second.
Additionally, the cracked count was always 2, which wrong.
The benchmark was incorrectly sending the time in ms to complete a hash instead of the number of hashes per second. Additionally, the cracked count was always 2, which wrong.



<a name="v0.2.4"></a>

Expand All @@ -201,12 +242,15 @@ written to a directory, and the client will monitor that directory for new zaps.

* Docker now finds hashcat correctly


### Features

* Added the ability to override checking checksums

This is useful when you set the data directory to be a network share



<a name="v0.2.3"></a>

## [v0.2.3](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.2.2...v0.2.3)
Expand All @@ -219,12 +263,15 @@ written to a directory, and the client will monitor that directory for new zaps.

* Docker now finds hashcat correctly


### Features

* Added the ability to override checking checksums

This is useful when you set the data directory to be a network share



<a name="v0.2.2"></a>

## [v0.2.2](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.2.1...v0.2.2)
Expand All @@ -242,6 +289,8 @@ written to a directory, and the client will monitor that directory for new zaps.

* Handle failure of getting agent config



<a name="v0.2.0"></a>

## [v0.2.0](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.1.11...v0.2.0)
Expand All @@ -252,6 +301,7 @@ written to a directory, and the client will monitor that directory for new zaps.

* Download files are now compare checksums correctly


### Features

* Agent now tells server its offline when shutting down
Expand All @@ -264,6 +314,8 @@ written to a directory, and the client will monitor that directory for new zaps.

* Added error metadata



<a name="v0.1.11"></a>

## [v0.1.11](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.1.10...v0.1.11)
Expand All @@ -276,6 +328,7 @@ written to a directory, and the client will monitor that directory for new zaps.

Fixed the bug where the agent died if there was a dangling lock.pid


### Features

* Add support for the agent error API
Expand All @@ -284,7 +337,9 @@ written to a directory, and the client will monitor that directory for new zaps.

* Add parallel file downloads

Replaced the word and rule file downloads to use go-getter in parallel using go routines
Replaced the word and rule file downloads to use go-getter in parallel using go routines



<a name="v0.1.10"></a>

Expand All @@ -296,7 +351,9 @@ written to a directory, and the client will monitor that directory for new zaps.

* Add parallel file downloads

Replaced the word and rule file downloads to use go-getter in parallel using go routines
Replaced the word and rule file downloads to use go-getter in parallel using go routines



<a name="v0.1.9"></a>

Expand All @@ -310,6 +367,8 @@ written to a directory, and the client will monitor that directory for new zaps.

Version 0.2.0 introduced major breaking changes.



<a name="v0.1.8"></a>

## [v0.1.8](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.1.7...v0.1.8)
Expand All @@ -329,10 +388,13 @@ written to a directory, and the client will monitor that directory for new zaps.

* Fix git-chglog missing config_dir


### Code Refactoring

* Update to latest Agent SDK v0.1.9



<a name="v0.1.6"></a>

## [v0.1.6](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.1.5...v0.1.6)
Expand All @@ -343,6 +405,8 @@ written to a directory, and the client will monitor that directory for new zaps.

* Added improved changelog support



<a name="v0.1.5"></a>

## [v0.1.5](https://github.com/unclesp1d3r/CipherSwarmAgent/compare/v0.1.4...v0.1.5)
Expand Down
Loading

0 comments on commit d6950f2

Please sign in to comment.