Archive | Contact | Privacy
25th March 2007
Nerd 2.0

SFT Loader with FritzBox sniff!

Who knows the "SFT Loader" not just when it comes to not quite legal downloads, this tool is highly regarded.

"The task of the SFT Loader is primarily there to prohibit the direct link of download sources elsewhere (known as Linkstealing)," it says on the homepage of the developer .

Protection through encryption and sniffer detection

The approach that the developers have chosen (the encryption of links), but has a big disadvantage, because there are still all unencrypted data sent over the network.

So far what I thought, just because the tool has a built-in sniffer detection, all mainstream sniffer detects that one of the "SFT Loader" but can confidently entrust its links.

FritzBox shows FTP files and directories

One method to circumvent this whole local Schutmaßnahmen is, of course, a step into the network. So far we still need a second PC, because you as a gateway between the Internet and had to ask to read the network traffic.

But this time is over now, there have been such routers are the functions implemented. So it might appear as the AVM Fritz box, where you can be in the web interface a recording of all data that is passed over the Fritz, download.

Of course, there, even when downloading the data via SFT file (*. sft), and one can now handle it on your mood.

Warning on foreign networks

From this one can only learn that you can not be too careful. So far the FritzBox can such a recording is not stored locally, not far away, this time at today's price decline to be more.

In the future, one must carefully observe even more aware of what it sends its data to the network.

Welcome encryption!

Body-Snatch

This insight should be small, neither a solicitation to delete (which I own in any way Eighth / cheap), but a glimpse of what all is possible with today's technology and what you should be prepared: PS.

19th June 2006
Nerd 2.0

Image for the new Telnet FritzBox 2030 / SL

Now I'm browsing through the ip-phone-forum found a new image for the Fritz, which temporarily Telnet enabled. So much fun with it.

Download Telnet image , the threat is ! here! to find.

Mfg BODY-Snatch

12th April 2006
Nerd 2.0

By way of postscript to FritzBox

As for specific pages I often times need a new IP, but it's very leaves, each time rebooting the router I have my times in the infinite vastness of the Internet on a search made for a tool that does this.

After a long search I then came across this tool which is neither the need nor FritzDSL Telnet software.

There must be only "transmit status information about UPnP" enabled and the box of 'fritz.box' be reached.

Already you can simply run the "reconnect.exe" and got a new connection to the Internet.

Download Reconnect.zip

Mfg BODY-Snatch

PS: Some virus-scanner recognize the "nc.exe" as NetCat which is true, yes, but in this context is no danger. So you can safely ignore this message.

Second February 2006
Nerd 2.0

DLink 360-T: router, HTTP server and DHCP in a

From current events, I would now like to summarize again all about the DLink 360-T.

The data for the telnet login, user "root" and password "admin". You should change this but as soon as possible via the web interface.

Modem as a router

  1. Ye logged into a web interface of the modem and provides a data connection with the pppoe connection. Then give one your connection and removes the Hacken at "On Demand" (not going to the modem).
  2. Now on Status-> Connection status and dial.
  3. Now you log onto via telnet and give
    route default netmask 0.0.0.0 dev ppp0
    one.
  4. Now you should always take the easy as the gateway IP of the DSL modem and the DNS server of your provider.

Port shares one can now easily perform using "iptables". Our example shows the eMule ports:

TCP | 4661
TCP | 4662
UDP | 4665
UDP | 4672
Zielrechner bei mir war 192.168.1.2
iptables -t nat -A PREROUTING -j DNAT -p tcp -s 0/0 –-dport 4661 –-to-destination 192.168.1.2 -i ppp0
iptables -t nat -A PREROUTING -j DNAT -p tcp -s 0/0 –-dport 4662 –-to-destination 192.168.1.2 -i ppp0
iptables -t nat -A PREROUTING -j DNAT -p udp -s 0/0 –-dport 4665 –-to-destination 192.168.1.2 -i ppp0
iptables -t nat -A PREROUTING -j DNAT -p udp -s 0/0 –-dport 4672 –-to-destination 192.168.1.2 -i ppp0

DHCP server

  1. Ye logged via telnet to the modem
  2. Go to the directory / var / tmp and have here is the file where all records relating to udhcpd.conf the DHCP server are made.
  3. To change the configuration it just puts one udhcpd.conf from the network and then brings them to you via wget on the modem.

Here is my example:
start 192.168.0.3
end 192.168.0.254
inflease_time 604800
interface br0
opt router 192.168.0.1
opt dns 192.168.0.1
opt subnet 255.255.255.0
opt lease 3600
conflict_time 60
lease_file /var/tmp/udhcpd.leases

own HTTP server

  1. Is it any wonder again simply log in via telnet.
  2. Now enter "ps" and "thttpd" services out looking to shoot and kill by.
  3. Now you create a new directory (mkdir "/ var / tmp / www /") and starts the server with
    /usr/sbin/thttpd -g -d /var/tmp/www -u root -p 80
    back.
  4. Now you can put it in / var / tmp / www / your HTML files.

To have a way to perform all changes automatically when you start to today, I found yet unfortunately.

Sample page on the modem: body-snatcher.ath.cx

Mfg BODY-Snatch

PS: If you did not understand something, only the and the by then still read and post here.

31st January 2006
Nerd 2.0

Fritz Box 2030 Telnet

Since there is already much zulesen to the Fritz boxes on the Internet regarding firmware modding, etc. I thought why did I not even try this time.

The first Problem was the Standert "starttelnet.image" image did not work. After a long search, much experimentation and frequent plug pulling on a post then I'm in the ip-phone-forum encountered. After much back and forth and then folded hats and I'm here now with my own small DNS server, but all times of the beginning.
How to start telnet on a FritzBox 2030

  1. The firmware may not be current 3/17/80, when the same is true can be continued with step 2.
    To get back to a previous firmware version, you must use the AVM Recover Tool. This one gets by you to contact the support of AVM. Now the update is to version .80, .73 still there in the LAN B port was defective because of an error. This version can be found right back at AVM .
  2. Now you play this file " enable_telnet.tar "as firmware image (unzip before) one. The box indicates an error "No error", the Internet is no longer responds and the Infoled flashes constantly. All this is normal.
  3. Her you can now login via telnet to the box. So after the restart but also Telnet remains active you must first take a TFTP server installed on a PC in your network, then you give the following command in the Fritzbox
    echo "mkdir / var / bin, / usr / bin / tftp-g-r-l bootup / usr / bin / bootup 192.168.0.2; chmod + x / usr / bin / bootup, / usr / bin / bootup &"> var / flash / debug.cfg
    192.168.0.2 stands for the address of the computer on which the TFTP server is running.
  4. Now it puts a file with the name "bootup" on the server. In it should show:
    / Usr / bin / tftp-g-r Linux / router / telnetd-l / usr / bin / telnetd 192.168.0.2;
    chmod + x / usr / bin / telnetd;
    / Usr / bin / telnetd-l / & sbin/ar7login
    (Applies to the IP the same as in item 3)
  5. So if everything done on the box and you just have to put on a Telnet Binary euern TFTP server. These are available here .

So it would be done and it runs first telnet to the box.

Next I want to take care of the change in the address range of the DHCP server to assign IP as the fit of .20 to not quite in my network.
DHCP address range change

  1. Ye logged via telnet to the box and executes the following command:
    / Usr / bin / tftp-p-r-l ar7.cfg / var/flash/ar7.cfg 192.168.0.2;
  2. Now you edited the now lying on your server ar7.cfg. You have to "brinterfaces {name =" lan "," = dhcpstart to 192.168.0.x, and dhcpend = 192.168.0.y; provide. Then the DHCP server assigns addresses from x to y, where x is greater than one course must be.
  3. Now it writes the file back to the Fritzbox via TFTP
    / Usr / bin / tftp-g-r-l ar7.cfg / var/flash/ar7.cfg 192.168.0.2;
  4. Now type in "reboot" on the one Firtzbox to restart them.

So would the DHCP server and personalized, we can turn the DNS.

DNS feed with its own name

  1. Option 1 is of course easy for all PC's "automatic IP" to enable, for whom this enough, you can make this connection.
  2. Since I do not want to use option 1 with any computer by me / I could have easily the entries in the DHCP server on the Fritzox faked. For this you need to return to the Fritzbox
    / Usr / bin / tftp-g-r multid.leases-l / var / flash / multid.leases 192.168.0.2;
    perform
  3. In the now present on the TFTP file server, the DHCP addresses are stored. Here you can enter as many more. All values ​​are in the form: "lease MAC IP NUMBER" NAME "01MAC" eg (lease 00:0 F: 3D: F0: 1D: C8 862 468 192.168.0.2 "Cube" 01000f3df01dc8)
  4. Jetz simply return the file with
    / Usr / bin / tftp-p-r-l multid.leases / var / flash / multid.leases 192.168.0.2;
    Write back and restart the Fritzbox with "reboot".

That would be everything I've done so with me. But watch the end when you upgrade to version 92 is the telnet function is lost. DNS and DHCP changes are retained.

Mfg BODY-Snatch