Merge pull request #96 from hahwul/release/2.4.0

Release v2.4.0

Author: hahwul

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "jwt-hack"
-version = "2.3.1"
+version = "2.4.0"
 edition = "2021"
 authors = ["hahwul"]
 description = "Hack the JWT (JSON Web Token) - A tool for JWT security testing and token manipulation"

README.md

@@ -49,7 +49,7 @@ docker pull ghcr.io/hahwul/jwt-hack:latest
 
 #### Docker Hub
 ```bash
-docker pull hahwul/jwt-hack:v2.3.1
+docker pull hahwul/jwt-hack:v2.4.0
 ```
 
 ## Features

docs/config.toml

@@ -19,7 +19,7 @@ highlight_theme = "ayu-mirage"
 
 [extra]
 logo_text = "JWT-HACK"
-badge = "v2.3.1"
+badge = "v2.4.0"
 logo_image_path = "images/logo.png"
 logo_image_padding = "10px"
 default_thumbnail = "images/preview.jpg"

docs/content/_index.md

@@ -3,7 +3,7 @@ template = "landing.html"
 
 [extra.hero]
 title = "Welcome to JWT-HACK!"
-badge = "v2.3.1"
+badge = "v2.4.0"
 description = "A high-performance toolkit for testing, analyzing and attacking JSON Web Tokens"
 image = "/images/preview.jpg" # Background image
 cta_buttons = [
@@ -45,4 +45,4 @@ icon = "fa-solid fa-robot"
 title = "Contributing"
 description = "JWT-HACK is an open-source project made with ❤️. If you want to contribute to this project, please see CONTRIBUTING.md and submit a pull request with your cool content!"
 button = { text = "View Contributing Guide", url = "https://github.com/hahwul/jwt-hack/blob/main/CONTRIBUTING.md" }
-+++
++++

docs/content/get_started/installation/index.md

@@ -50,7 +50,7 @@ docker pull ghcr.io/hahwul/jwt-hack:latest
 
 ### Docker Hub
 ```bash
-docker pull hahwul/jwt-hack:v2.3.1
+docker pull hahwul/jwt-hack:v2.4.0
 ```
 
 ## Verification
@@ -61,4 +61,4 @@ Once installed, verify that JWT-HACK is working correctly:
 jwt-hack --version
 ```
 
-You should see the version information and the JWT-HACK banner displayed.
+You should see the version information and the JWT-HACK banner displayed.

docs/content/usage/server/index.md

@@ -77,7 +77,7 @@ The following request and response shapes are supported.
 ```/dev/null/health-response.json#L1-5
 {
   "status": "ok",
-  "version": "2.3.1"
+  "version": "2.4.0"
 }
 ```
 
@@ -283,7 +283,7 @@ Notes:
 
 ## cURL Examples
 
-Replace host/port as needed. If the server was started with --api-key, include -H 'X-API-KEY: <API_KEY>' in each request.  
+Replace host/port as needed. If the server was started with --api-key, include -H 'X-API-KEY: <API_KEY>' in each request.
 
 ### Health
 ```/dev/null/curl-health.sh#L1-3
@@ -375,5 +375,5 @@ curl -s http://127.0.0.1:3000/scan \
 - Bind address: Use `--host 0.0.0.0` to accept remote connections.
 - CORS: Open (any origin, any method, any header).
 - Performance: `/crack` can be CPU-heavy and synchronous; keep search spaces small or run behind a job queue.
-- Security: This server is a testing tool. If exposed beyond localhost, use --api-key to require X-API-KEY on all requests and add additional safeguards (authN/Z, rate limits, isolation).  
-- Errors: Most endpoints return HTTP 200 with `success:false` and `error`. Handle both the HTTP status and the `success` flag in clients.
+- Security: This server is a testing tool. If exposed beyond localhost, use --api-key to require X-API-KEY on all requests and add additional safeguards (authN/Z, rate limits, isolation).
+- Errors: Most endpoints return HTTP 200 with `success:false` and `error`. Handle both the HTTP status and the `success` flag in clients.

snap/snapcraft.yaml

@@ -6,7 +6,7 @@ base: core22
 grade: stable
 confinement: strict
 license: MIT
-version: v2.3.1
+version: v2.4.0
 architectures:
   - build-on: amd64
   - build-on: arm64