otinstaller · Frameworks
Install pywerview on Linux in one command
pywerview is a Python port of PowerView for enumerating Active Directory from Linux: users, groups, computers, shares, and sessions, over LDAP and SMB with domain credentials you hold.
pywerview in three lines
pipx install otinstaller
ot install pywerview
ot run pywerview -- d:example.comRuns the-useless-one/pywerview (GPL-3.0, ★ 1.1k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What pywerview is for
- AD enumeration during an authorised internal assessment.
- Mapping group membership without a Windows host.
Typed inputs for pywerview
otinstaller translates these prefixes into pywerview's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- d:
- domain ·
ot run pywerview -- d:example.com - u:
- username ·
ot run pywerview -- u:jane_doe
Run every installed tool that takes the same input at once: ot run --all d:example.com
Where the results go
Every run lands under ./results/pywerview/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff pywerview <target>, and pull indicators out with ot extract.
Before you run it
- Needs domain credentials and network access to a domain controller. This is internal network tooling, not open-source intelligence in the public sense.
Update, remove, inspect
ot info pywerview # inputs, flags, keys
ot example pywerview # sample output
ot update pywerview # move to the next tested version
ot remove pywerview # delete its virtualenvFull reference for this tool: docs for pywerview.
Pairs with
FAQ
pywerview with otinstaller, answered
How do I install pywerview on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install pywerview. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.
Which inputs does pywerview take through otinstaller?
d: (domain), u: (username). otinstaller maps each prefix to pywerview's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otinstaller save pywerview results?
Under ./results/pywerview/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff pywerview <target> to compare the last two.
Does pywerview need an API key or a login?
Yes. Needs domain credentials and network access to a domain controller. This is internal network tooling, not open-source intelligence in the public sense. Keys and tokens live in ~/.otinstaller/.env with permissions 600, and ot keys check verifies them.
Can I run pywerview together with other tools?
Yes. ot run --all d:example.com runs every installed tool that accepts domain input, in parallel, including pywerview. Save the combination as a playbook to repeat it.