hacker.org

Can some will tell me,
How should i ping of death.

You mean, how to use ping of death? Well... POD is pinging computer with malformed packets. Standard packet size (maximal) is 65,535 bytes. The trick was so, that most systems couldn't handle larger packets, so packets of 65,536 could crash the system (it could cause buffer overflow). But the modern systems are fixed, and they probably won't crash because of this. But who knows...

But now a days Ping flood is used insted?

Right... but this isn't so fast. Only one PC can't flood a server with a pings...

O I see,
So Denial of service attack would be better?

Hell yeah!! And there're so many ways to perform that attack...

<<D.A.>> wrote:You mean, how to use ping of death? Well... POD is pinging computer with malformed packets. Standard packet size (maximal) is 65,535 bytes. The trick was so, that most systems couldn't handle larger packets, so packets of 65,536 could crash the system (it could cause buffer overflow). But the modern systems are fixed, and they probably won't crash because of this. But who knows...

what is ping of death?

A ping of death (abbreviated "POD") is a type of attack on a computer that involves sending a malformed or otherwise malicious ping to a computer. A ping is normally 64 bytes in size (or 84 bytes when IP header is considered); many computer systems cannot handle a ping larger than the maximum IP packet size, which is 65,535 bytes. Sending a ping of this size can crash the target computer.
Traditionally, this bug has been relatively easy to exploit. Generally, sending a 65,536 byte ping packet is illegal according to networking protocol, but a packet of such a size can be sent if it is fragmented; when the target computer reassembles the packet, a buffer overflow can occur, which often causes a system crash.
This exploit has affected a wide variety of systems, including Unix, Linux, Mac, Windows, printers, and routers. However, most systems since 1997-1998 have been fixed, so this bug is mostly historical.
In recent years, a different kind of ping attack has become wide-spread - ping flooding simply floods the victim with so much ping traffic that normal traffic fails to reach the system (a basic denial-of-service attack).

<<D.A.>> wrote:A ping of death (abbreviated "POD") is a type of attack on a computer that involves sending a malformed or otherwise malicious ping to a computer. A ping is normally 64 bytes in size (or 84 bytes when IP header is considered); many computer systems cannot handle a ping larger than the maximum IP packet size, which is 65,535 bytes. Sending a ping of this size can crash the target computer.
Traditionally, this bug has been relatively easy to exploit. Generally, sending a 65,536 byte ping packet is illegal according to networking protocol, but a packet of such a size can be sent if it is fragmented; when the target computer reassembles the packet, a buffer overflow can occur, which often causes a system crash.
This exploit has affected a wide variety of systems, including Unix, Linux, Mac, Windows, printers, and routers. However, most systems since 1997-1998 have been fixed, so this bug is mostly historical.
In recent years, a different kind of ping attack has become wide-spread - ping flooding simply floods the victim with so much ping traffic that normal traffic fails to reach the system (a basic denial-of-service attack).

how can i send to the target ping over 65,535?

in linux you just can enter "ping -s 65536"... -s defines the size of a packet. But the problem is that usually it's not allowed by the system, so I guess you gotta find some cracked ping program.

<<D.A.>> wrote:in linux you just can enter "ping -s 65536"... -s defines the size of a packet. But the problem is that usually it's not allowed by the system, so I guess you gotta find some cracked ping program.

do you know any good?

nah... didn't had a practice.

<<D.A.>> wrote:nah... didn't had a practice.

well never mind i will find it my self

aright... but keep in mind that most of sustems got that exploit fixed...

<<D.A.>> wrote:aright... but keep in mind that most of sustems got that exploit fixed...

ok thx for the advice