|
Very good link. I've got couple of mails from some ppl disclosing his reality.
quote: |
>Proof of Mr.Ankit Fadia\'s stealing material
>-------------------------------------------
>
>This is to reply to the arguments in the comments which came after
>the post on neworder about this script kiddie\'s scam to get a
>book published. This discovery is being made by many people. Here
>are their findings.
>
>Here\'s the concrete proof. We now evaluate his article/tutorial
>shit on PING. Inorder to keep them seperate, my comments are
>given with // or /* (eg. //Fadia is a thief or /*hacking scams*/)
>
>Stolen from : W.Richard Stevens
>Book : TCP/IP Illustrated Vol 1 (The protocols)
>
>This is a bible reverred by network students everywhere. Let\'s
>now look at Chapter 7 - Ping Program - it\'s on Pg.85 in my
>Addison Wesley Longman publication.
>
>Let\'s take at the original chapter :
>
>7.1 Introduction
>----------------
>
>The name \"ping\" is taken from the sonar operation to locate objects.
>The Ping program was written by Mike Muuss and it tests whether
>another host is reachable. The program sends an ICMP echo request
>message to host, expecting an ICMP echo reply
>to be returned (Fig 6.3 lists all the ICMP message types)
>
>Normally if you can\'t Ping a host, you wont\' be able to telnet or ftp
>to that host. Conversely, if you can\'t telnet to a host, ping is often
>the starting point to determine what the problem is.
>
>Ping also measures the round trip time to the host, giving us
>some indication of how \"far away\" that host is.
>
>In this chapter we\'ll use ping as a diagnostic tool and to
>further explore ICMP. Ping also gives us an opportunity to
>examine the IP record route and timestamp options. Chapter 11
>of [Stevens 1990] provides the source code for the Ping program
>
>/* Now very interestingly the original book gives this stuff in
>italics to stand apart */
>
> Years ago we could make the unqualified statement that if
> we can\'t Ping a host, we can\'t Telnet or FTP to that host.
> with the increased awareness of security on the internet,
> routers that provide access control lists, and firewall
> gateways, unqualified statements like this are no longer
> true. Reachability of a given host may depend not only on
> reachability at the IP layer, but also on what protocol is
> being used, and the port numbers involved. Ping may show
> a host as being unreachable, yet we might be able to Telnet
> to port 29 (the mail server)
>
>/* Now let\'s take a look at Mr.Fadia\'s \"book\" or \"article\" or
>\"hacking truths\" (Truths ???).. Observe the same structuring
>and even a blatant tranformation of the original section
>into a \"Hacking Truth\" */ :
>
>Ping Un-Pinged
>
>By Ankit Fadia [email protected]
>
>Ping is an extremely popular diagnosis tool, which is commonly
>used to determine whether a remote host is alive, or not. This
>manual explores this popular TCP/IP diagnosis utility in detail.
>
>The word ping is actually taken from a scientific operation
>carried out to locate objects using sonar. That is exactly what
>ping does in networks, finding or determining whether a particular
>host is alive or not.
>
>Whenever one cannot make a connection to a particular port of a
>remote system, then ping is the starting point to determine
>whether the remote system that is being tried to open a connection
>with is connected to the Internet or not, or in other words whether
>it is alive or not. Similarly, when you use ping and determine that
>a remote system is not alive, then it would mean that you cannot make
>a connection to it.
>
>So, basically ping is used to determine whether a remote host is
>alive or not or whether it is connected to the Internet or not.
>
>*****************
>HACKING TRUTH: Although the implications of the results of ping
>can best be described as the above, they do not always hold true.
>Nowadays, with the increased usage of firewalls, router access lists
>and other access controls, it doesnt always mean that if you cannot
>ping a particular host, then you cannot telnet to a particular port
>on it.
>*****************
>
>/* The similarities does\'nt stop here,he\'s ripping of the entire
>series. He uses the same diagrams, same code, mixing,changing
>words here and there. We should strongly put this up and report
>it to the people responsible. It is evident that we are dealing
>with basically a dishonest fool who wishes to be famous by
>simply - stealing.
>
>W.Richard Stevens died on the yr he was appearing on Phrack,
>he\'s a true guru. Please don\'t allow such people to simply
>violate his name and work. We have to notify the people and
>expose this fadia guy for what he is.
>
>It\'s against my intelligence to buy Mr.Fadia\'s book but the
>people who have made this silly mistake, just check how the
>copyrights .. bibiliography etc is mentioned. He can be
>even put to task by the publishers of the orginal content
>
>If I could identify this source, I am sure many of you will
>be noticing things stolen from other places. Send this mail
>to as many people in the scene as possible.
>
>It\'s also reducing the reputation of all sites hosting his works. These included sites like neworder,blacksun and securitywriters. I am sending this mail to everyone of them.
|
|
|
|
09-09-2003 03:50 |
|
|