Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ModuleNotFoundError: No module named 'o365spray' #22

Open
Frogsecurity opened this issue Nov 2, 2023 · 2 comments
Open

ModuleNotFoundError: No module named 'o365spray' #22

Frogsecurity opened this issue Nov 2, 2023 · 2 comments

Comments

@Frogsecurity
Copy link

o365spray --validate --domain test.com --proxy-url https://127.0.0.1:8080

Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/home/kali/Desktop/tools/o365spray/o365spray/main.py", line 11, in
from o365spray import version
ModuleNotFoundError: No module named 'o365spray'

Issue after running the installation in the following way

git clone https://github.com/0xZDH/o365spray.git
cd o365spray
pip install -r requirements.txt

@0xZDH
Copy link
Owner

0xZDH commented Nov 19, 2023

Can you provide some more information here -- what version of the tool are you attempting to run?

Looking at your command, you appear to be invoking o365spray as if you installed it as a local package vs. your install command only installing the dependencies. Testing locally I am unable to reproduce.

Side note: The --proxy-url flag is explicitly for FireProx API usage - based on your proxy value, you will likely want to use the --proxy flag instead.

@tijldeneut
Copy link

Hi, I encountered the same issue. It has to do with installing o365spray using the setup script (e.g. python3 setup.py install) to have the o365spray command available everywhere.
It would run only when started from main o365spray folder.
The issue seems to be fixed by adding __init__.py files to each sub folder before installation, I've forked it and will perform a merge request, feel free to decline or ignore and implement other fixes as desired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants