Conversation
The default -m/-b wordlist path was derived from sys.argv[0], which under `uv run cloud_enum` is the console-script shim in .venv/bin. The default became .venv/bin/enum_tools/fuzz.txt, so the tool exited with "Cannot access brute-force file" even when -m was passed. Resolve it from the module's own __file__ instead. fuzz.txt was also never declared as package data, so clean wheel builds (uv tool install, pip install .) shipped without it. Declare it under [tool.setuptools.package-data]. Add a regression test that runs parse_arguments with argv[0] pointing at a venv shim. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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 was wrong
The default wordlist path pointed at the wrong folder (cloud_enum.py:38). The code built the default path for -m and -b from sys.argv[0]. Under uv run
cloud_enum, that's the launcher uv creates in .venv/bin/, so the default became .venv/bin/enum_tools/fuzz.txt, which doesn't exist. You passed -m yourself,
but -b still used the bad default, hence "Cannot access brute-force file". It now uses the module's own location (file) instead.
fuzz.txt was never actually packaged (pyproject.toml). A build from a clean clone left fuzz.txt out of the package, so uv tool install, pip install . or
any wheel install had no wordlist at all. The old setup.py didn't include it either. A leftover cloud_enum.egg-info/ folder in the working tree made local
builds look fine. I added [tool.setuptools.package-data] for fuzz.txt.