Jump to content

chrizree

Dedicated Members
  • Posts

    804
  • Joined

  • Last visited

  • Days Won

    69

Posts posted by chrizree

  1. With the autossh module stopped in the Turtle "text based GUI", try running the following directly from the terminal on the Turtle (change user@address to something relevant for your setup and ports as well, if not "default")
    autossh -M 20000 -i /root/.ssh/id_rsa -R 2222:localhost:22 user@address -p 22 -N -T
     
    If that works (it should), change the following line in /etc/turtle/modules/autossh from:
    uci set autossh.@autossh[0].ssh="-i /root/.ssh/id_rsa -N -T -R "$autossh_remoteport":localhost:"$autossh_localport" "$autossh_host" -p "$autossh_port" "
     to:
    uci set autossh.@autossh[0].ssh="-i /root/.ssh/id_rsa -R "$autossh_remoteport":localhost:"$autossh_localport" "$autossh_host" -p "$autossh_port" -N -T"
     
    Furthermore... to get the module itself working, change the lines in the "configure" function of the autossh module from:
        autossh_host=$(uci show autossh.@autossh[0].ssh | awk '{print $7}' | sed "s/'//g")
        autossh_port=$(uci show autossh.@autossh[0].ssh | awk '{print $9}' | sed "s/'//g")
        autossh_remoteport=$(uci show autossh.@autossh[0].ssh | awk '{print $6}' | sed 's/:/ /g' | awk '{print $1}')
        autossh_localport=$(uci show autossh.@autossh[0].ssh | awk '{print $6}' | sed 's/:/ /g' | awk '{print $3}')
     to:
        autossh_host=$(uci show autossh.@autossh[0].ssh | awk '{print $5}' | sed "s/'//g")
        autossh_port=$(uci show autossh.@autossh[0].ssh | awk '{print $7}' | sed "s/'//g")
        autossh_remoteport=$(uci show autossh.@autossh[0].ssh | awk '{print $4}' | sed 's/:/ /g' | awk '{print $1}')
        autossh_localport=$(uci show autossh.@autossh[0].ssh | awk '{print $4}' | sed 's/:/ /g' | awk '{print $3}')
     
    Also change the line in the "start" function of the autossh module from:
    autossh_host=$(uci show autossh.@autossh[0].ssh | awk '{print $7}' | sed 's/@/ /g' | awk '{print $2}')
    to:
    autossh_host=$(uci show autossh.@autossh[0].ssh | awk '{print $5}' | sed 's/@/ /g' | awk '{print $2}')

    Done!

    • Like 1
  2. I think you have mixed something up and made settings that isn't needed (or shouldn't be there). 2222 has nothing to do with the local sshd on the vps. Just skip any settings for the local sshd on the vps and see it from the Turtle perspective.

    • Like 1
  3. Remember that most of the Mk1 payloads available are years old and the landscape is constantly changing and evolving. It's a cat and mouse game and if the payloads aren't updated (or new ones are created based on recent vulnerabilities or functionality), they most likely turn obsolete.

    • Upvote 2
  4. The only mistake I can spot is the fact that ppl get their traffic sniffed without them allowing it to happen. Other than that... there is no mistake. The module works as intended. The question to ask is: "How many ppl are using web services in 2021 that is based only on http?" My answer is, "not many" and probably the reason why nothing gets caught in the net.

  5. As Rkiver suggested, there's a Bunny section of the forums that should be used, so I guess this thread should be moved.

    Anyway, there are some bits and pieces that could render possible problems in the original code (i.e. the first post, which seems based on the "official" nmapper payload and then adjusted). For starters how nmap is spelled, with a capital "N" that will throw a "Nmap: command not found".

    Regarding the latest submitted code suggestion; what is <yOur IP> supposed to be replaced with? The victim is in most situations a "black box" when it comes to knowledge about device details, such as the IP address. I would rather stick to the original idea of using GET TARGET_IP instead of having to know the "victim" IP before I write the payload. I also need to elevate my knowledge about SYNC. It seems to be a part of the Ducky language that I haven't seen before. I get if "sync" is used so that the information is saved to disk in a proper way, but SYNC and sync isn't the same thing and SYNC must therefore refer to something else that I don't know about but happily would get more info on.

    • Upvote 1
  6. When is this going to be solved? It's almost to the day one year ago that this thread was created (with a following promise to solve it), but I still get the Hak5 repo error when running opkg update on the Shark. Perhaps the Shark is out of development so that the Hak5 repo is of no relevance any longer.

×
×
  • Create New...