Jump to content

C2 https port change


Recommended Posts

On 6/28/2020 at 6:46 PM, Void-Byte said:

Hi Syn,

I'd recommend sticking with the default port number of 443. Obfuscation is not considered to be a valid form of cybersecurity or defense. You should attempt instead to use other means of hardening.


I know obfuscation isn't secure, along with everyone else in InfoSec. I think you misunderstood my post. It's about increasing the chance of the device being able to phone back home to the C2 server for SSH. I'd rather just use the ssh console in the C2 server since it's a feature, so why not use it? Most organizations aren't going to allow tcp/2022 outbound, so making the outbound SSH connection from say a lan-turtle that's on-prem using tcp/2022 to the C2 server has a very high likelihood of being blocked. If I can change the ssh listen port on the C2 server to say 443, I'm going to have a much higher chance of it being permitted out, and I can't do that if I can't change the ssl port for the web service.

And before anyone else mentions it, I know that if the org has a layer 7 firewall like a palo, it won't work because it'll identify traffic as ssh instead of ssl going out on 443.

Link to comment
Share on other sites

  • 1 year later...
1 hour ago, Jtyle6 said:


Please don't necropost.

Why not?  Previously unanswered question with zero other posts on this forum about it. My reply can help others who are searching for the same thing.   It would be a different story if the question was resolved, but as with so many other posts here, they're left without true resolution. 

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...