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

run_proxy Connection always corrupted #264

Closed
13 tasks
luckseal opened this issue Oct 8, 2023 · 1 comment
Closed
13 tasks

run_proxy Connection always corrupted #264

luckseal opened this issue Oct 8, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@luckseal
Copy link

luckseal commented Oct 8, 2023

Describe the bug

use run_proxy module

Connection always corrupted

To Reproduce

Steps to reproduce the behavior:

emm3r0r - 192.168.1.241
target-1 - 192.168.1.61 192.168.2.102
target-2 - 192.168.2.101

use target-1 run_proxy , connect to the proxy and ssh to 192.168.2.101

xxx@MacBook-Pro-5 ~ % proxychains4 ssh root@192.168.2.101
[proxychains] config file found: /usr/local/etc/proxychains.conf
[proxychains] preloading /usr/local/lib/libproxychains4.dylib
[proxychains] DLL init: proxychains-ng 4.16
[proxychains] Strict chain  ...  192.168.1.241:6666  ...  192.168.2.101:22  ...  OK
root@192.168.2.101's password:
Last login: Sun Oct  8 05:26:40 2023 from 192.168.2.102
[root@localhost ~]# pwd
/root
[root@localhost ~]# whBad packet length 1726738805.
ssh_dispatch_run_fatal: Connection to 192.168.1.241 port 6666: Connection corrupted

C2 Transport

  • [✅] Direct connection
  • CDN proxy
  • Shadowsocks
  • Shadowsocks + KCP
  • TOR
  • Other proxies
  • None of the above (Please specify blow)

Agent

OS

  • [✅] Linux
  • Windows

CPU architecture

  • [✅] amd64
  • 386
  • arm
  • arm64
  • mips
  • mips64
  • riscv64
@luckseal luckseal added the bug Something isn't working label Oct 8, 2023
@jm33-m0
Copy link
Owner

jm33-m0 commented Oct 9, 2023

For this scenario I suggest use port_fwd for now as it's more reliable. I will start working on the proxy soon.

jm33-m0 added a commit that referenced this issue Oct 11, 2023
This way long-live connections such as SSH sessions will be kept alive as long as possible.
Short-live ones such as `curl google.com` will be managed by the OS, meaning they will stay open for about a minute or so.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants