sliver VS sslstrip

IDK if you are too young to remember the fallout from Snowden, but the Kremlin threw out entire rooms computers and for a time used actual typewriters. Because those computers had, more or less, twingate connectors on them. That's a bit of a rich example, but you're essentially installing what sliver calls an implant, what meterpreter calls a payload, and what Cobalt Strike calls a beacon. It's cool if you want to, but there's no need when you can just open a port with the same technology a Fortune 50 does.

What they said. Also, if you want a free alternative to cobalt: https://github.com/BishopFox/sliver

Sliver is neat, https://github.com/BishopFox/sliver

Armitage is precursor to CS but they diverged a long time ago. I ran up the armitage that comes with Kali these days, it has issues and bugs that would prevent it being useful. Sliver is probably the most usable FOSS C2. https://github.com/BishopFox/sliver

I’m a huge fan of Sliver, super powerful and well written/maintained with a lot of care and attention paid to tradecraft. I’m a big fan of the features like the built-in support for DNS canaries to detect blue team analysis. Only downside is that the documentation may be a little lacking.

- https://github.com/BishopFox/sliver/wiki/DNS-C2

For the additional more advanced steps I used sliver as a c2. Sliver is an excellent tool for the job and unlike some other tools, it's FOSS! You can easily replace sliver with your tool of choice, however.

Another option might be to try something like sslstrip to strip off the TLS layer so you can point your tools at the stripped-off/non-TLS endpoint. Probably non-trivial to get this old code working on any system though, let alone a Jetson: https://github.com/moxie0/sslstrip

sslstrip - Demonstration of the HTTPS stripping attacks.

Yeah. And for anyone unaware, this technique, SSL stripping, was made well-known (and arguably pioneered?) by Moxie Marlinspike of Signal with his tool sslstrip back in 2011: https://github.com/moxie0/sslstrip. I believe that's what he was most famous for before Signal.

Once the connection has been intercepted, the attacker can use a tool such as sslstrip to disable all HTTPS redirects and change https:// links to unencrypted http://.

E' possibile, per quanto molto meno facile. https://github.com/moxie0/sslstrip per esempio. Ci sono anche altre tecniche che si basano sulla manipolazione delle richieste di DNS e cose simili. Sicuramente molto piu' facile da notare e ordini di grandezza piu' complesso di HTTP, che è assolutamente triviale.