dark_pyrro Posted February 7 Share Posted February 7 Did you make the changes to the module file that I previously linked? Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 7 Author Share Posted February 7 no because i can´t start the autossh so when i PS it doesn't appear Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 7 Share Posted February 7 You don't need to start the module to change it. You do that from the terminal/ssh session. It's file editing from CLI. Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 7 Author Share Posted February 7 autossh -M 20000 -i /root/.ssh/id_rsa -R 2222:localhost:22 user@address -p 22 -N -T in this command what i need to put in /id_rsa? i have the id_rsa but what i have to put to go get the key? Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 7 Share Posted February 7 You are misunderstanding the whole thing..... Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 7 Author Share Posted February 7 ca you explain me please? need help to try solve this Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 7 Author Share Posted February 7 i have just factory reset the Turtle. i connect and change the password. search for updates and update the turtle. when it finish the connection go off. when i try to start again the turtle i dont get a connection os ssh. Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 8 Share Posted February 8 In what way are you connected to the Turtle when you try to ssh into it? USB side or RJ45 side? What command are you using when trying to ssh into the Turtle? Is it possible to ping the Turtle (on 172.16.84.1) from the computer that the Turtle is connected to? What IP address does the computer (to which the Turtle is connected) get from the Turtle? Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 8 Author Share Posted February 8 hi. good mornig. when i try to connect the turtlw in my pc throw the command line show this: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the RSA key sent by the remote host is SHA256:6y111Pw2PPS4A+bgd+cq6+sVtpm0uWXJ0J3bfAU3y5k. Please contact your system administrator. Add correct host key in C:\\Users\\joaoa/.ssh/known_hosts to get rid of this message. Offending RSA key in C:\\Users\\joaoa/.ssh/known_hosts:5 Host key for 172.16.84.1 has changed and you have requested strict checking. Host key verification failed. i only can access by putty. with putty i can access. so, now the turtle is "brand new". is there any video or guide that i should follow to configure the autossh access? Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 8 Share Posted February 8 https://docs.hak5.org/lan-turtle/video-guides/persistent-shell-access-with-autossh Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 8 Author Share Posted February 8 do i use my vps public ip or my vps private ip? Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 8 Share Posted February 8 You have to ask yourself if the Turtle will be able to access your VPS using its private IP. What's the logic choice? Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 8 Author Share Posted February 8 the logic choice is use the public. thats what i been using and get no success. am i right? after all this attemptsi´m already confuse. 🙂 Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 8 Share Posted February 8 The public one is the correct answer. The Turtle has no chance to connect on the private one. That address isn't possible to use on the internet. It's internal for the Amazon services. Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 8 Author Share Posted February 8 i will follow the steps that are on the video and hope it works fine. i let you now. thanks. Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 8 Author Share Posted February 8 is there any configuration or something i need to check in my vps before i configure the turtle? Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 8 Share Posted February 8 Anything that relates to the Turtle being able to reach the VPS using ssh. I.e. the things that already has been mentioned in this thread; Lightsail firewall and OS firewall (if used). Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 8 Author Share Posted February 8 in the video when we create a par of keys and copy it appear on known_hosts this to things. The "ecda-sha2" and "ssh-rsa". when i do this exactly procees in my just appear the "ecdsa-sha2". i made everything exactly but it still dont work. i dont get a connection. 😞 Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 8 Share Posted February 8 Just configured the autossh module on one of my Turtles using my Lightsail VPS and I had no issues doing it. Not sure what you are doing. You have to be detailed (as in "step-by-step-detailed") in order to be able to troubleshoot at what point(s) you are doing something wrong. Quote Link to comment Share on other sites More sharing options...
Joao Almeida Posted February 12 Author Share Posted February 12 hello. i´m gonna create a new server and restart the turtle to begin everything and do everything again. Quote Link to comment Share on other sites More sharing options...
dark_pyrro Posted February 12 Share Posted February 12 It might solve things, but I doubt it will change much. What you most likely need to do is to know how the VPS (and Turtle) is set up and adjust according to that scenario. Also, take things step by step and troubleshoot anything that might fail. Just starting from scratch isn't always the solution, but I won't try to stop you from doing it. Most important is that you document what you do so that it's possible to follow the steps you take when setting it all up again (as I suggested in my previous post). Coming back and say "I started from scratch and it's still not working" won't be any good input if trying to help you reach your goal. It has to be detailed. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.