-
-
Notifications
You must be signed in to change notification settings - Fork 444
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
Feature request: database connection #37
Comments
i ll meditate about this possibility .. therefore there are some workarounds to do what you want:
#/bin/bash
session_dir="`dirname $0`"
batch="$session_dir/batch.phpsploit"
for session in $session_dir/*.session; do
phpsploit -l "$session" -e "exploit; source $batch"
done
|
you must note that a TARGET doesn't necessarly represents a remote server. To clearify, if my remote server hosts victim.com, blog.victim.com and also xyz.org, i use to put one (or more) phpsploit backdoors in each of them, so i can set a lot of different phpsploit entry points, in different hostnames, making more difficult any log analysis. for more infos: phpsploit -e 'help set' |
I'll look into all that soon! Thanks! |
I don't plan to implement database, therefore your use case (and my answer) revealed an advanced use-case that should be documented for next release. |
I was thinking that it would be interesting if the script had a databse and when we register targets it store them in it. Then we can list the targets with an ID and then select a target by ID. We could also be able to send a command to all the targets.
The text was updated successfully, but these errors were encountered: