Jump to content

denartha

Active Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by denartha

  1. Just for giggles, try a different computer.

    By some sort of Karma my girlfriend woke up and I asked her for her laptop password.

    I tried, easily 14 times on my beloved Lenovo x220 running fedora to complete the unbricking process and it didnt work. My girlfriends crappy consumer-grade laptop running Windows 8 completed the unbricking process first time around.

    Good News: My Lan Turtle is back.

    Bad News: The world no-longer makes sense.

    Well, tbh, the world never made a lot of sense, but now it makes less. Barry, thank you!

  2. In the dmesg output I posted above they're were some USB errors, when plugged into a different port, the output of dmesg reads:

    [28802.157429] usb 2-1.2: new high-speed USB device number 10 using ehci-pci
    [28802.244972] usb 2-1.2: New USB device found, idVendor=0bda, idProduct=8152
    [28802.244982] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [28802.244987] usb 2-1.2: Product: USB 10/100 LAN
    [28802.244992] usb 2-1.2: Manufacturer: Realtek
    [28802.244995] usb 2-1.2: SerialNumber: 00E04C36083D
    [28802.321536] usb 2-1.2: reset high-speed USB device number 10 using ehci-pci
    [28802.463845] r8152 2-1.2:1.0 eth0: v1.04.0 (2014/01/15)
    [28802.536993] systemd-udevd[16336]: renamed network interface eth0 to enp0s29u1u2
    [28802.557818] IPv6: ADDRCONF(NETDEV_UP): enp0s29u1u2: link is not ready
    [28804.160882] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s29u1u2: link becomes ready
    

    Just to clarify, it still isn't working.

  3. In the dmesg output I posted above they're were some USB errors, when plugged into a different port, the output of dmesg reads:

    [28802.157429] usb 2-1.2: new high-speed USB device number 10 using ehci-pci
    [28802.244972] usb 2-1.2: New USB device found, idVendor=0bda, idProduct=8152
    [28802.244982] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [28802.244987] usb 2-1.2: Product: USB 10/100 LAN
    [28802.244992] usb 2-1.2: Manufacturer: Realtek
    [28802.244995] usb 2-1.2: SerialNumber: 00E04C36083D
    [28802.321536] usb 2-1.2: reset high-speed USB device number 10 using ehci-pci
    [28802.463845] r8152 2-1.2:1.0 eth0: v1.04.0 (2014/01/15)
    [28802.536993] systemd-udevd[16336]: renamed network interface eth0 to enp0s29u1u2
    [28802.557818] IPv6: ADDRCONF(NETDEV_UP): enp0s29u1u2: link is not ready
    [28804.160882] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s29u1u2: link becomes ready
    
  4. ... I started the update process and the PuTTY session dropped. I waited about 5 minutes and didn't see any activity from the amber light. I figured it may have been a fluke install and just let it go while I was going about my business. I came back an hour later and still no amber. I tried to SSH back in but no good. I pulled the device out of the USB and it sure enough it wouldn't boot back up or respond to SSH connections.

    Pretty much the exact same thing happened to me. After the upgrade I didnt get the amber light. I gave it a while, not an hour but 20 minutes anyway. Now when I plug it into my laptop, I get a steady green light and the amber comes on for about a second and then goes off.

    The device is recognised in dmesg.

    [27683.714098] usb 3-1: New USB device found, idVendor=0bda, idProduct=8152
    [27683.714106] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [27683.714110] usb 3-1: Product: USB 10/100 LAN
    [27683.714114] usb 3-1: Manufacturer: Realtek
    [27683.714117] usb 3-1: SerialNumber: 00E04C36083D
    [27683.821966] usb 3-1: reset high-speed USB device number 15 using xhci_hcd
    [27683.822044] xhci_hcd 0000:0e:00.0: Setup ERROR: setup context command for slot 1.
    [27683.974449] usb 3-1: reset high-speed USB device number 15 using xhci_hcd
    [27683.974500] xhci_hcd 0000:0e:00.0: Setup ERROR: setup context command for slot 1.
    [27684.127777] usb 3-1: reset high-speed USB device number 15 using xhci_hcd
    [27684.142708] xhci_hcd 0000:0e:00.0: xHCI xhci_drop_endpoint called with disabled ep ed061a80
    [27684.142717] xhci_hcd 0000:0e:00.0: xHCI xhci_drop_endpoint called with disabled ep ed061aac
    [27684.142720] xhci_hcd 0000:0e:00.0: xHCI xhci_drop_endpoint called with disabled ep ed061ad8
    [27684.247812] r8152 3-1:1.0 eth0: v1.04.0 (2014/01/15)
    [27684.319136] systemd-udevd[15723]: renamed network interface eth0 to enp14s0u1
    
    

    I don't get an IP although I can see the DHCP requests.

    I have assigned the IP 192.168.1.2 to the interface but I cannot ping or access the web interface.

    I have tried the unbricking method(dozens of times now actually) and either I am doing something wrong or something is wrong with my device.

    The instructions I followed are from the wiki, thus:

    
    1. Download the latest factory image from https://downloads.lanturtle.com/turtle-2-factory.bin
    2. Carefully open the LAN Turtle case by removing the two screws underneath the sticker on the bottom
    3. While holding the button on the bottom of the LAN Turtle, plug the device into a computer
    4. After 3 seconds let go of the button and wait an additional 30 seconds to receive an IP address from the LAN Turtle
    5. If you do not receive an IP address in the 192.168.x range from the LAN Turtle within a minute, statically assign the LAN Turtle's interface to 192.168.1.2 (netmask 255.255.255.0)
    6. Browse to the LAN Turtle firmware recovery web interface at http://192.168.1.1
    7. Follow the on screen prompts to upload and flash the factory image downloaded in step 1
    8. When the flash is complete the LAN Turtle will reboot and will be accessible again from 172.16.84.1 with the default username root and password sh3llz
    
    

    I'm kind of stumped. Any one have any suggestions?

  5. For the most part you can only get root from an FTP server if the FTP server is running as root. If the FTP server is not running as root, then it can't grant you root privileges.

    Why dont you find all files that are owned by root and look for ways of exploiting them?

    Best of luck with it. I just finished a Pen Test where part of my job was a similar task, unpriv shell and my job was to get root on RHEL. Didn't get root in the timeframe I had. Sad panda.

  6. Obviously, nowadays cracking WEP is trivial, and recently I ran into luck, I got the right ARP packet and was able to replay it and within minutes I had about 45,000 initialisation vectors, and got the key instantly, but it can happen, on a quiet network, that you are sniffing for a long time before you get the right packet.

    The basic concept of the Pineapple, or the Jassager software it runs is, Client(phone, laptop, etc) says to Pineapple, "Are you my preferred network?", the Pineapple replies "Sure am!", the client says "Ok here is my WEP key, am I authenticated?", and the pineapple says, "You sure are!", and the handshake is over with the client connected.

    Is there a way to capture the WEP key the client supplies? If so, it could be a very nice way of gathering all the WEP keys around you, quickly and easily.

    Thanks!

×
×
  • Create New...