Release PWMenu 1.3.7 - #14
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
aircrack-ngverification for every manually added or edited password.MapversusGPSprovenance, and live password/map actions without page reloads.list_tasks; only one best unresolved capture per AP can enter the queue.Root causes fixed
OHC candidates were previously placed in the persistent queue before export/history reconciliation, so the UI could show already submitted APs as queued and retries could revisit them. WPA-sec functionality was split across standalone plugins with overlapping state. Manual password storage trusted user input without proving that the key matched a capture. Legacy filenames and punctuation-normalized aliases also caused AP identity drift across exports, whitelist entries, and map actions.
Impact
PWMenu now owns the full WPA-sec lifecycle, refuses incorrect manual passwords, keeps exact handshake identity across the map and exports, and prevents known OHC tasks from entering the queue. Users in jurisdictions where the authenticated OHC API is unavailable can route only OHC through a configured VLESS link without proxying Pwnagotchi, bettercap, GPS, WPA-sec, or other traffic.
Validation
403; OHC-only VLESS returnedHTTP 200,success=True, and 308 tasks.127.0.0.1, and zero service restarts.