-
Notifications
You must be signed in to change notification settings - Fork 1.2k
More updates #29
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
More updates #29
Conversation
… the usage instead of just printing it. this way it's easily editable.
…ess, this way you can just add the options into the dict when you want to make more options (Stored under global), a few more minor updates
|
I would merge this, but i am currently working on the project from my side. Adding functionality and changing up a few things. I will be testing the changes i made in about an hour or so. After debug i will post my new version to the master branch. After i do so, please have a look at the main python file again, the changes are quite extensive and you may want to adjust your pull request accordingly. |
|
Alright sounds good. I’ll check it out when you’re done
… On Feb 5, 2018, at 2:27 PM, NullArray ***@***.***> wrote:
I would merge this, but i am currently working on the project from my side. Adding functionality and changing up a few things. I will be testing the changes i made in about an hour or so. After debug i will post my new version to the master branch. After i do so, please have a look at the main python file again, the changes are quite extensive and you may want to adjust your pull request accordingly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Sure thing. It's taking a little longer than i had anticipated. However i do intend to put it up as fast as possible. I am currently debugging. But i will keep this comment section updated and my twitter feed as well of course. I'll keep you posted, thank you once again for your contributions though. I think it's great there's a couple people working together on this project now. |
|
Take your time man. I think it’s a good tool that is getting a bad rep for no reason |
|
Thanks, and yeah i really should take my time. Since many people have expressed an interest in working together on this though i feel i owe it to you guys to give it my all. Unfortunately life gets in the way sometimes. But i would hate to disappoint. In any case, there is something i wanted to ask your opinion on @Ekultek. Do you think it would be helpful if i added a branch/directory with a sort of "Rolling" release. I Would post the code i have thus far, and it would be a bit like the dev version. The stable release will remain in the master branch but i could just post some updates as they happen from my end to the rolling dev branch/dir. Whether fully debugged or not. |
|
What a lot of people do is create release on Github and keep the master branch updated as the rolling releases. But since you said yours aren’t going to be 100% debugged id say creating another branch with “beta” releases would probably be a pretty good idea.
… On Feb 7, 2018, at 8:29 AM, NullArray ***@***.***> wrote:
Thanks, and yeah i really should take my time. Since many people have expressed an interest in working together on this though i feel i owe it to you guys to give it my all. Unfortunately life gets in the way sometimes. But i would hate to disappoint.
In any case, there is something i wanted to ask your opinion on @Ekultek. Do you think it would be helpful if i added a branch/directory with a sort of "Rolling" release. I Would post the code i have thus far, and it would be a bit like the dev version. The stable release will remain in the master branch but i could just post some updates as they happen from my end to the rolling dev branch/dir. Whether fully debugged or not.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
keeping the master as rolling and adding a experimental branch is a good way to go. |
|
Alright guys i have added a Find the main python file here https://github.com/NullArray/AutoSploit/blob/dev-beta/autosploit.py |
|
So do you want us to make our pull requests more towards dev-beta? |
|
I also have a minor update in the old style of the script that just adds the ability to load a custom host list. Check it out at this gist: https://gist.github.com/NullArray/f1fdeacb9aba75ccfe0babd9d31538c2 May have a bug or two as well. Just putting this stuff out there so we have something to work with. |
|
Yeah if you could make a pull to dev-beta that'd be great. Once we have a working version in dev-beta i will just move it on over to the master branch. |
|
closing this down then, reopen one soon |
etcfolder and movedmodules.txtalong with removed the huge print call for the usage. The usage is now also in a file labeled "usage" underetc.strip()call so there won't be any space between, example:1.5seconds each, the both now sit for 3 seconds, and removed some spacing in them, example:modules_pathand ausage_pathglobal variable that contains the path to both the usage file and the modules file