GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Fix default wordlist path under uv run and package fuzz.txt by mr-pmillz · Pull Request #84 · initstring/cloud_enum

Conversation

@mr-pmillz

@mr-pmillz mr-pmillz commented Sep 27, 2026

Copy link
Copy Markdown
Contributor

What was wrong

  1. 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.

  2. 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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@mr-pmillz @claude
Fix default wordlist path under uv run and package fuzz.txt
a89e5a8
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 <[email protected]>
@initstring

initstring commented Oct 2, 2026

Copy link
Copy Markdown
Owner

@mr-pmillz Thank you for finding this pretty serious error I made when moving to uv. Nice work. I will make time to review and merge next week.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@initstring @claude
Update stale docs to match the uv migration
229fd0b
- utils.py pointed at a requirements.txt that no longer exists; the
  missing-dependency message now says to run 'uv sync'
- -ns help text omitted its 1.1.1.1 default
- README: regenerate the usage block from the real --help output, correct
  the cloudenum/ -> enum_tools/ regions paths, document uv tool install

Co-Authored-By: Claude Opus 5 <[email protected]>
@initstring
initstring merged commit 21af4f9 into initstring:master Oct 4, 2026
1 check passed

Uh oh!

There was an error while loading. Please reload this page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@mr-pmillz @initstring
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.