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
module import error #8
Comments
Not sure why that would be an issue, did you check out PTF from github? On a fresh install it works fine since we are doing a direct relative import from the src folder and core directory. Everything works fine from a fresh install - not sure what you would be experiencing there as traditional import is supported in both python 2.7 and 3. Changing import to from core import * wouldn't be a valid import as it doesn't know where core is located for the import. Not sure how or why that would work on your system... Closing this issue as I cannot reproduce on Ubuntu, Kali, or Debian test beds. root@kali: |
yes, i've clone the repo, into my dev dir, well,
and after change the interpreter into
|
Git pull the latest repo, this was fixed already. |
OK |
framework.py is a library - you should just be running ./ptf or python ptf. Not directly running the core modules independently. This is a hierarchy structure for coding. |
yeah, i know it. like errors bellow:
some users may not concern about it, how about they didn't use Kali? like Ubuntu/Debian, not all users log in to their system with root user defaulty. compared to Kali users, i think you need to like :
|
I would agree with you, having a root check is a great idea. Something I added into SET but didn't into here. Will add that now and appreciate it! |
and, like what Metasploit does, the ptf should be able to run some shell command, like ifconfig,whoami, etc, it would be nicer if you add this capability to the ptf |
hey there,
when i run the framework.py it says
instead using from
src.core import *
why don't you just usefrom core import *
?after change the import section into
from core import *
it's runs like what i thoughtThe text was updated successfully, but these errors were encountered: