We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
系统环境: Linux fob 5.15.113-1-MANJARO #1 SMP PREEMPT Wed May 24 20:32:47 UTC 2023 x86_64 GNU/Linux OpenJDK 64-Bit Server VM (build 17.0.7+7, mixed mode)
使用形如 genCrossC2.Linux 172.16.109.1 3306 .beacon_keys null Linux-bind x64 /tmp/tcp.elf 的命令生成的文件,实际bind的端口仍然是4444而不是3306。
genCrossC2.Linux 172.16.109.1 3306 .beacon_keys null Linux-bind x64 /tmp/tcp.elf
执行生成的https beacon文件上线后,在beacon内执行connect ip,CS在console中会显示profile中配置的set tcp_port "3306",但实际上beacon仍是通过4444连接目标IP。
The text was updated successfully, but these errors were encountered:
现linux-bind在配置端口时,通过参数来设定./tcp.elf 8080。后续将更改为生成时进行配置,及修复其稳定性
./tcp.elf 8080
Sorry, something went wrong.
No branches or pull requests
系统环境:
Linux fob 5.15.113-1-MANJARO #1 SMP PREEMPT Wed May 24 20:32:47 UTC 2023 x86_64 GNU/Linux
OpenJDK 64-Bit Server VM (build 17.0.7+7, mixed mode)
使用形如
genCrossC2.Linux 172.16.109.1 3306 .beacon_keys null Linux-bind x64 /tmp/tcp.elf
的命令生成的文件,实际bind的端口仍然是4444而不是3306。执行生成的https beacon文件上线后,在beacon内执行connect ip,CS在console中会显示profile中配置的set tcp_port "3306",但实际上beacon仍是通过4444连接目标IP。
The text was updated successfully, but these errors were encountered: