Jump to content

Audrick

Active Members
  • Content Count

    33
  • Joined

  • Last visited

  • Days Won

    2

1 Follower

About Audrick

  • Rank
    Hak5 Fan +

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I don't run Kali on a vps. I just VPN to my VPS and run it from my box. Is it better to have it in the cloud? I never really thought about it. I did google it and see that now VPS providers seem to have kali as an option. As I recall it wasn't available when I started using a VPS. Maybe I should be rethinking where I put my tools?
  2. I have never done this to a Windows VPS. So some of this may not help at all. When I setup my turtle I setup my port 22 as the ssh port that I connect to my vps on. Then I set the remote port 2222 and that is the shell port I I'll use to connect to from my vps. So from VPS I would ssh root@localhost -p 2222 -i ~/.ssh/rsa. But before I would do that I would check the connection from the turtle to the VPS by running the this command on the VPS. netstat -lt4 The L is listening T is tcp and the 4 ip 4. When I run it on my VPS I get a list of ports. When the turtle is connected I see 2222 in the list. This is the one that means that turtle connected. tcp 0 0 localhost:2222 0.0.0.0:* LISTEN If I don't see that in the list I know that I have dome something wrong on the first half. Turtle connection to the VPS. If I see that and can't connect then I am doing something wrong on the second half. Connecting back to the turtle. I don't have access to windows box right now to check for the same commands.
  3. Thanks for posting the pictures. It allows me to still be paranoid. On my turtle the Module Keymanager never says started. That module doesn't need to be running to have worked. The screen shot looks correct to my eyes. The Keymanager makes a public and private key pair. You will use the private key on your turtle and pub key on your VPS to connect. Then when you connect from your vps you will connect to your turtle you will type something like ssh root@localhost -p 2222 -I ~/.ssh/rsa and you will end up on your turtle. So if you exit the Turtle Gui and end up at a prompt. You should be able to type ssh you@xxx.xxx.xxx.135 -i ~/.ssh/rsa and connect to your server. That will confirm that your turtle pub key is in the ~/.ssh/authorized_keys on your vps. If it fails please type the same command but start with ssh -vvv you@.... any errors will tell us where its going wrong. Also you will need to change the ssh command with the proper user name and ip. I would also double check the name of the key. I used custom ones so I don't recall what the real name is. I hope that helps. Keep trying. It gets easier.
  4. Im not clear about your no response from shell. Using the command prompt are you able to ssh to your server using the cert the Turtle Key Manager made for you. It would look something like this "ssh me@myserver.com -i ~/.ssh/rsa" If that doesn't work you could put the -vvv after ssh and you would see a lot of info. It could help you find the error. I have noticed a lot of people mentioning trouble with the GUI in Turtle version 6.0 and up. I have mine working but I don't see the star next to it that I would expect. None the less its working. No I didn't download your zip file from the hacker website to look at your screen shots.
  5. That would be a great feature. Since I keep one in my bag it would great to be able to use it as a 3g modem while I wait to find someplace to deploy it. I hope they put a check box for this in the next turtle interface.
  6. I have found that it always works best if you start with dropping out of the Turtle and getting to a shell. Then you can ssh to the server using the cert you generated. If it doesn't work you can re run it with a -vvv in it to give you lots of details. After getting it working there I find the rest works.
  7. Audrick

    Total Newb

    I am not sure where the Ethernet cable goes? That being said when you ssh into your lanturtle can you ping your c2 server? ping -c4 192.168.1.7 or whatever IP you are using to connect to your c2 web page. That would tell you that your turtle is connected to your local network and has access to your c2 server. Hope that helps.
  8. The mistake I made with the factory reset the first time I did it was not using the LAN Turtle Recovery Firmware from the bottom of the download page. I also remember having trouble finding the rest button on 3G. Its no the opposite side from the pictures as they are all standard Lan Turtles. Once I got the correct firmware and followed the directions it all worked when for me each time. Hope that helps.
  9. Pale Emp1re There is a factory reset doc located at https://docs.hak5.org/hc/en-us/categories/360000979313-LAN-Turtle with the other docs. It is easy to reset. Just make sure you download the factory recovery firmware and not the the standard build. Also on my Turtle 3G the reset button was on the other side from the pictures in the manual but still worked as documented. Hope it helps.
  10. I installed 6.2 today. Then added the module Autossh with a few others. I configured autossh on my Lan Turtle 3G. I can ssh using the cert I generated at the prompt to my VPS but the autossh connection never seems to happen. I also notice that when I click on Stop in the interface it never shows that its stopped. Toggleing the Enable Disable shows correctly. So I disabled. Saved and rebooted. Logged back in and says Current Status: Started Boot Status Disabled. See Attached. I also tried enabling it and rebooting. Still no star next to it. Also when I check the ports on my VPS it shows my old turtle but not this one. I could roll back to 5. Was excited to try the new Cloud C2 version with my gear. Anyone know how to get this working?
  11. I think the docs they provide are helpful. https://docs.hak5.org/hc/en-us/categories/360000979313-LAN-Turtle I do think the guide is the same for the 3g and regular turtle. I have found a lot of uses for my 3g and ended up with a second. I think they are great. Also I have found that when I have a specific question, the people here seem very willing to help.
  12. When I use https on my C2 I get to it via https://c2.mysecretsite.com I don't use port 8080 I am running this command in roots crontab @ reboot /root/web/c2_community-linux-64 -hostname c2.mysecretsite.com -db /root/web/c2.db -https If that helps. A
  13. Okay I know you didn't ask and maybe I am the only old person that will be get the joke but shouldn't the device be called Lan Shark.
  14. Brilliant. Much better than my idea. I marked your post so I can run it on my new pi when it arrives.
  15. Maybe make that a script and put a wait 30 at the beginning so that the rest of the system is booted? When you run that command manually does it stay running?
×
×
  • Create New...