January 16th, 2004, 11:27 PM
PM8228, I think he might be talking about that nasty thing called "identity theft" i've been to a few isp's and they've asked for stuff all i.d. and unless they trace it through your phoneline which would take forever if you were dialing through several carriers and only had short logins i'm not too sure how traceable it would be...
January 17th, 2004, 01:20 AM
You are pretty close, there is an identity, but it is not yours it would check out as well. All very illegal, so I do not want to go into details but it can be done with varying degrees of complexity.
January 17th, 2004, 02:00 AM
unless they started video recording people walking into isp shops or outlawing prepaid internet they're gonna continue to have a problem
January 17th, 2004, 02:06 AM
hmm what would be more anonymous in terms of services e.g. dialup vs. adsl/cable.....i'm starting to think dialup due to the fact you don't have one set ip address and you can use prepaid.....
January 17th, 2004, 04:41 AM
But the ISP still knows what phone niumber you're dialling from.
January 17th, 2004, 07:22 AM
January 17th, 2004, 08:05 AM
A good script might help, like the watered down version of looksharpe? In essence, what you need to understand is that the user that does the flooding, may be spoofing their IP to begin with, hence
for now, extremely difficult to trace. The flooding you speak of, could be accomplished through the use of sub-seven trojan or other trojan viri to turn computers into what is called "Zombie" computers. These machines, or indeed, with War Scripts, make use of Socket connections to irc these then flood channels with line upon line of gunk. Causing some to lag, others to disconnect etc etc, if load is big enough, even cause an irc "split" if irc servers are clustered and cannot handle the bandwidth or resource demands, old irc.msn.com comes to mind here.......
To let you know though..... RFC 2267 and RFC 2827 are 2 important ISP standards, in my opinion, that need to be enforced more stringently. These 2 RFC's make provision for the non-egress of non-isp sourced IPs. That means that if User dials up, uses DSL or Cable and is supposed to have IP 184.108.40.206, yet displays IP 220.127.116.11. The ISP should stop all connectivity from that computer as it could be Spoofing an IP for intent to use maliciously. So sometime soon, with the enforcement of these RFCs. A new kind of work-around will surely abound.
RFC 2267 <---- RFC link
RFC 2287 <---- RFC Link
(please could someone do me a favour, if possible. If anyone has read any of my other posts, please let me know if my use of English is improving. I am working hard on it to become more articulate and fluent. Thanks a million).
HO$H Pagamisa. Pro Amour Ludi....
January 17th, 2004, 08:18 AM
If I may be so bold. there are ways to stop a telephone number from being registered on an ISP machine. I know that for a fact, a certain 2 character and 3 digit combonation stops the number from being sent as part of carrier signal in my country. Since our telephone company, (we only have one here) uses American (the best), AT&T equipment and SUN boxes, would it not be logical that this may happen also elsewhere in the world?! It would therefor make it difficult from even an isp point of view to give logs in that instance.......
The ISP would trace back to the diverted phone and that would have a call trace put on it. Given the duration of a useful net session it would not be long before I got a knock on my door?
Work-arounds do exist, but as stated in the previous post by Nihil, If they out to get you, they will eventually catch you......
HO$H Pagamisa. Pro Amour Ludi....