You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,13 @@ RS-Shell is reverse shell solution developped in Rust with client, implant and s
15
15
16
16
RS-Shell implements two modes: **TLS over TCP** and **HTTPS**.
17
17
18
-
* TLS over TCP mode is a standard reverse shell where the implant executed on the target machine will connect back to the TLS listener, running on the *attacker*'s machine
18
+
* TLS over TCP mode is a standard reverse shell where the implant executed on the target machine will connect back to the TLS listener, running on the operator's machine
19
19
* HTTPS mode works more like a C2 infratructure, with an HTTPS server, an implant, and a client:
20
20
* The HTTPS server is executed on a server accessible by both the implant and the client. It is based on the [Actix](https://actix.rs/) web framework with [Rustls](https://docs.rs/rustls/latest/rustls/)
21
21
* The implant is executed on the target machine and will request the server for "new tasks" every 2 seconds (by default, can be changed in the code for the moment)
22
-
* The client is executed on the *attacker* machine. It will also connect to the server via HTTPS, and will permit to send the commands to the implant
22
+
* The client is executed on the operator's machine. It will also connect to the server via HTTPS, and will permit to send the commands to the implant
23
23
24
-
Windows HTTPS implant is partially proxy aware thanks to the [Windows's WinINet library](https://learn.microsoft.com/fr-fr/windows/win32/wininet/about-wininet). This means that it is able to identify proxy configuration in the registry and automatically authenticate against it if necessary (if the proxy is not configured via the registry or a WPAD file, this will probably fail).
24
+
Windows HTTPS implant is partially proxy aware thanks to the [Windows's WinINet library](https://learn.microsoft.com/fr-fr/windows/win32/wininet/about-wininet). This means that it is able to identify proxy configuration in the registry and automatically authenticate against it if necessary (if the proxy is not configured via the registry or a WPAD file, this will probably fail, and you will have to indicate the proxy URL and the credentials manually in the implant code).
25
25
26
26
Client, implant and server are all cross-platform and work on Windows and Linux systems.
0 commit comments