Jump to content

Search the Community

Showing results for tags 'autossh'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • Hak5 Gear
    • Hak5 Cloud C²
    • WiFi Pineapple Mark VII
    • USB Rubber Ducky
    • Bash Bunny
    • Key Croc
    • Packet Squirrel
    • Shark Jack
    • Signal Owl
    • LAN Turtle
    • Screen Crab
    • Plunder Bug
  • O.MG (Mischief Gadgets)
    • O.MG Cable
    • O.MG DemonSeed EDU
  • WiFi Pineapple (previous generations)
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapples Mark I, II, III
  • Hak5 Shows
  • Community
    • Forums and Wiki
    • #Hak5
  • Projects
    • SDR - Software Defined Radio
    • Community Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Enter a five letter word.

Found 14 results

  1. Hello everybody I started up my LAN turtle for the first time today and have encountered many problems, this being the biggest. I was following Darrens tutorial for AutoSSH when this error popped up after pressing "copy_key" on the Key Manager module. "There was an error retrieving the key fingerprints." I saw a post similar to this but the solution presented did not work for me. https://forums.hak5.org/topic/37070-keymanager/ Im using the same cloud hosting service that Darren is using and its running Ubuntu 16. There are no problems PuTTY'ing into
  2. Hello all. I have been watching the LAN Turtle 104 - Persistent Shell Access with AutoSSH video at https://www.youtube.com/watch?v=uIdvvrDrRj0 and at 5:15 it shows three fields for the setup, they are User@host, Remote Port & Local port. On my Turtle, which is probably a newer version of firmware than the one in the video, there is a fourth field simply named Port. As I understand it the Turtles local port is 22. It connects to the host via port 2222. Therefore on the host if you SSH to port 2222 it connects to the Turtle on it's port 22 through the 2222 tunnel. So you need
  3. Good day guys, I received my lan turtle a few weeks ago. It's been working great. I've had it setup to digitalocean box with Autossh Today I wanted to switch it over to my home office and have it autossh to a VM I'm probably missing something very basic. I've looked over the video Darren as done at for prescient shell and autossh Ok setup working backward. Kali Light (VM) - XenServer - Untangle router/firewall - Modem - Outside I have Untangle port forwarding to XXXX to Kali light to port 22 I'm able to make a SSH connection
  4. Hi, great little toy, though having some issues with sshfs. I managed to get autossh and sshfs to connect to a linux box i have on the net over tcp:443 without a hassle. Great posts from the forum and good videos. Thanks... autossh works as advertised, and starts on boot, within 60 seconds of connecting i am able to ssh in. However, i cannot seem to get sshfs to start on boot, and instead have to ssh in, use the turtle menu to start it or exit to the cli and type start sshfs. both autossh and sshfs exist in /etc/turtle/autostart_modules as symlinks to their respective /et
  5. Hi, I have a problem with setting up autossh over ptunnel. Ptunnel working on xxx.xxx.xxx.xxx ptunnel host, local port 8000, dst. host yyy.yyy.yyy.yyy and dst. port 22. With ssh bar@localhost -p 8000 log's in to the yyy.yyy.yyy.yyy server. It is good. When I use autossh with bar@yyy.yyy.yyy.yyy, remote port 2222 and local port 22 I can connect back to lanturtle from yyy.yyy.yyy.yyy. So this config good too. But how to configure autossh, to go trough ptunnel? The documentation of ptunnel seems promising, but I have no luck to configure it: With this an autoSSH session t
  6. I've been having some trouble with my router lately. I'm trying to get everything set up for autossh. If I'm logged in to my router and try to connect to my device, I get this error: (192.168.1.176 is the Nano) However, if I'm on my Nano and try connecting to my router, it works perfectly. So it's like a one way connection. Both devices have all the proper keys added, so no passwords are needed. My router is using SSH-2.0 Dropbear 2014.63, and the pineapple of course uses SSH-2.0 OpenSSH 6.8. The firmware of the router is DD-WRT-v24 sp2 std P.S. I posted the question here as I don't
  7. Hello, I recently received my Lanturtle, I set up autossh following Darren's video... When my lanturtle is connected to my computer I manage to ssh as root into localhost (ssh root@localhost -p 2222), however when I plug my lanturtle into a USB power source and connect it to my lan I cannot seem to ssh into it using the same technique. (ssh root@localhost -p 2222) Instead I get the error: ssh_exchange_identification: read: Connection reset by peer. Please Help! Thank you
  8. Frontend for autossh. In development Released - View/edit autossh configs - start/stop/enable/disable - create ssh key pairs - adds remote server to known_hosts https://github.com/audibleblink/autossh
  9. 2qik4u

    KeyManager

    Hi Guys Just unpacked my new Lan Turtle, all updated and patched with no problems... (thank you so much Hak5 team) Now setting up my AutoSSH for remote management and access to the target LAN The problem I am having is once the key pair are generated I try to copy the key to the host ssh server and receive an error "There was an error retrieving the key fingerprint" I am not sure if it's me (very much a newb) or if I have missed something, my cloud server is running Ubuntu 14.* LTS and is fully updated and patched. I have no problems SSH'ing to the server via putty or accessing the turtle
  10. Hi I have enabled succesfully autossh in my markV, but something is happening that it's causing my device to reboot, this just happens if I'm connected to ssh remotely. I've checked the memory or cpu to see if the device is overloaded, but everything seems normal, what could be the cause?
  11. I've submitted some autossh feature requests including this one to support multiple port forwards and alternate SSH server ports. I know Seb has a lot on his plate before getting to these, so I was messing around and cloned AutoSSH, adding an "Advanced Settings" feature (mostly copy/pasting). Obviously, I can continue to modify the /etc/config/autossh file manually, but I wondered if this idea would get any traction, as it's so simple to implement. Basically, I just modified includes/content/setup.php to add the following: $args = exec("uci show autossh.@autossh[0].ssh | cut -f2- -d'='");
  12. So after a week of everything I could possibly try I've come to the forums to discuss my Autossh Relay connection problem. I'm trying to reproduce Daren's relay server and Chriswat's tutorial and manage the gui remotely. Contents: MkV Virtual Ubuntu Server LTS 12.04 External Box Ubuntu Server LTS 12.04 Windows Putty Ubuntu 13.10 Virtual Phone Hotspot for External IP for MkV Ports: VM Ubuntu Server -p 7000 External Box Ubuntu Server -p 50456 MkV 1471:localhost:1471 First I have a Ubuntu Server 12.04 LTS box setup at work as a file server but it also has openssh-server installed. T
  13. Hello All, I'm trying to get my MkV to start airmon/airodump and ssh to my relay server. The airmon portion seems to be working swimmingly. The SSH/and HTTP proxy through my relay do not seem to be initiating however. Below is the line I have added to the configuration for dip 010. ifconfig wlan1 up; airmon-ng start wlan1; airodump-ng --write /sd/airodump.pcap --output-format pcap mon0; option ssh '-i /etc/dropbear/id_rsa -N -T -R 9434:localhost:1471 root@666.666.666.666'; option ssh '-i /etc/dropbear/id_rsa -N -T -R 999:localhost:22 root@666.666.666.666' Any ideas why it is not auto-con
  14. I'm having some issues that began immediately after performing a factory reset. My issues pertain primarily to connectivity, client mode, and AutoSSH. Connectivity issues: 1) I cannot connect to my Pineapple AP when I use my Alfa AWUS036NHA (ar9271) USB network adapter with Kali Linux; however, I am able to connect with my Netgear (rtl8187) USB network adapter with Kali Linux. I'm also able to connect with my MacBook Pro, MacBook, and iMac's built-in network adapters. Only when trying to connect with my Alfa, I receive the error- "Unable to obtain an IP address." I've rebooted Kali, reboote
×
×
  • Create New...