sweeper707 Posted October 4, 2018 Share Posted October 4, 2018 This is probably common knowledge for most people here but thought it could be useful Apply for a license from HAK5 C2 Get a Public IP such as (64.15.17.23) for your server Get a public domain and point the dns record such as "cave.domain.com" to the IP 64.15.17.23 Allow the DNS propagation to take plus I usually wait around 24 hours as Let's Encrypt DNS seems to be delayed a bit Ensure your servers firewall inbound rules allow "http (80) and https (443)" Launch the C2 Servers on your box such as: ./c2_community_linux64 -hostname "cave.domain.com" -https Take note of the setup token. This will be used to validate the setup. This will start the server and generate the configuration details and let's encrypt certificate within the database. Go to https://cave.domain.com Apply the setup token and the license key to the setup wizard and follow the steps. Notes: If you stop the server and relaunch it the "setup token" will not re-appear so be sure to write this down. It is required during setup. If you can't remember the setup token, stop the C2 Server and delete the c2.db file and start from step #6. You can copy the device.config into the respected device's /etc/ folder , once rebooting the device it should re-connect to your C2 Cloud Network. Link to comment Share on other sites More sharing options...
FloridaTech Posted October 4, 2018 Share Posted October 4, 2018 I might want to add .. if you tail the c2.db file the token is in plain text in the file .. Link to comment Share on other sites More sharing options...
aethernaut Posted October 6, 2018 Share Posted October 6, 2018 Do you also have to open up port 2022 on the firewall? I was guessing that that was how the devices phoned home. Link to comment Share on other sites More sharing options...
sweeper707 Posted October 8, 2018 Author Share Posted October 8, 2018 I believe that is only needed for SSH Terminal. Link to comment Share on other sites More sharing options...
Darren Kitchen Posted October 8, 2018 Share Posted October 8, 2018 5 hours ago, sweeper707 said: I believe that is only needed for SSH Terminal. Correct. Rather than need a separate port for each device, all devices SSH back to C2 over 2022 by default. This can be configured with the -sshport argument. Link to comment Share on other sites More sharing options...
Cole Posted April 13, 2019 Share Posted April 13, 2019 On 10/8/2018 at 4:47 PM, Darren Kitchen said: Correct. Rather than need a separate port for each device, all devices SSH back to C2 over 2022 by default. This can be configured with the -sshport argument. Once the device SSH’s back into C2, what would be the best way to create a reverse tunnel and access the pineapple GIU interface from another computer? Link to comment Share on other sites More sharing options...
Danny Reed Posted November 2, 2019 Share Posted November 2, 2019 Anyone have this setup and working on a EC2 Instance from AWS ? Link to comment Share on other sites More sharing options...
s0u1sb4n3 Posted January 24, 2020 Share Posted January 24, 2020 How would I set this up on basic hosting plan from domain.com Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.