-
Notifications
You must be signed in to change notification settings - Fork 15
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
attacker.com not reachable #1
Comments
Hi, unfortunately there are still a couple of glitches when building from scratch, but we are working on it and will keep you updated. Thanks for reporting! |
thank you for your response |
I had the same issue. In my case, it was related to the certificate files shared folder. |
The last stage of the attack is failing " in "d" (RETR payload.html") command, any hints? Sat Jun 26 23:20:25 2021 [pid 27] FTP command: Client "172.21.0.1", "CONTENT-LENGTH: 631" I got these errors in mitmproxy as well: |
I can reproduce intermittent failures of mitmproxy which causes a hang. Restarting mitmproxy and trying again lead to success for me after a couple of attempts, but it is very unreliable. Not all data is forwarded and then the FTP server does not see the RETR request, which then means the passive port can not be found. We will investigate further. |
hey there
there's a problem when I try to reach attacker.com. it gives me a connection refused error
there's also another problem related to the prior state, when I try to run the LOGS script
says error: no container found for vsftp_1
actually vsftp container doesn't remain up, and when I check the "docker ps" output, there's is no vsftp
it runs, but It disappears
please let me know what to do
thanks
The text was updated successfully, but these errors were encountered: