show ip of downloaders/uploaders

Archived discussion about features (predating the use of Bugzilla as a bug and feature tracker)

Moderator: Moderators

Locked
jeffx
Posts: 1
Joined: 2003-02-09 07:45

show ip of downloaders/uploaders

Post by jeffx » 2003-02-09 08:06

Add a feature where it shows the ip of the one who are downloading from you and the ip of the person you're downloading from. This way, it is much more easier to block any abusers.

Gadget
Posts: 62
Joined: 2003-01-11 06:24
Location: Finland
Contact:

Post by Gadget » 2003-02-09 08:33

Yeah, right. Maybe a ddos attack option would be nice in dc++ too?

volkris
Posts: 121
Joined: 2003-02-02 18:07
Contact:

Post by volkris » 2003-02-09 09:40

Gadget wrote:Yeah, right. Maybe a ddos attack option would be nice in dc++ too?
Right, like a person launching a ddos attack wouldn't know the command netstat.

Well then again...

Locutus
Posts: 21
Joined: 2003-01-05 15:25

Post by Locutus » 2003-02-09 09:53

Very bad idea....
Web-Programmer - Application Developer

volkris
Posts: 121
Joined: 2003-02-02 18:07
Contact:

Post by volkris » 2003-02-09 10:18

Locutus wrote:Very bad idea....
Could you please expound upon that motion?

RobbeZ
Posts: 17
Joined: 2003-01-07 00:09

Post by RobbeZ » 2003-02-09 10:18

I wouldn't do this, cause it wouldn't be very healthy :twisted:
Codito Ergo Sum

Locutus
Posts: 21
Joined: 2003-01-05 15:25

Post by Locutus » 2003-02-09 11:10

volkris wrote:
Locutus wrote:Very bad idea....
Could you please expound upon that motion?
People want as much Privacy as possible.... I know that in denmark lots of organisations are using IPs to claim money from people sharing illegal mp3s and movies... I see no reason for making it easier to track people down

You couldn't use the IP anyway for blocking, since no blocking system is avaliable for DC++....
Web-Programmer - Application Developer

volkris
Posts: 121
Joined: 2003-02-02 18:07
Contact:

Post by volkris » 2003-02-09 11:49

Locutus wrote: People want as much Privacy as possible.... I know that in denmark lots of organisations are using IPs to claim money from people sharing illegal mp3s and movies... I see no reason for making it easier to track people down

You couldn't use the IP anyway for blocking, since no blocking system is avaliable for DC++....
Any organization that has the ability to claim money from people sharing illegal mp3s will have plenty of incentive to look up the ip address from typing "netstat -n" into a command window. Go ahead, try it. Not displaying the ip address is not going to make it significantly harder for these people.

As for blocking, I can block people by ip at my computer's firewall. Simple.

Locutus
Posts: 21
Joined: 2003-01-05 15:25

Post by Locutus » 2003-02-09 12:10

I see no reason for making it easier


Anyway, why don't YOU just type netstat -n
Web-Programmer - Application Developer

volkris
Posts: 121
Joined: 2003-02-02 18:07
Contact:

Post by volkris » 2003-02-09 12:39

Locutus wrote:I see no reason for making it easier
You miss the point.
Implementing such a feature doesn't make it any easier for the people you're talking about, the feature only makes it easier for normal users.

It's like saying you're not going to release a telephone with voice encryption because you don't want to make it easier for the military to keep secrets. Guess what? The military has their own damn voice encrypted telephones, only the general public is hurt by your refusal to release it. These groups tracking down illegal mp3s have their own damn ways to get your ip address that are much better than copying each one down from the display inside of DC++.
Anyway, why don't YOU just type netstat -n
I did to make sure Windows had it. Since I'm firewalled I don't suppose there's any major harm in showing you the output from when I run it:

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:4403 127.0.0.1:4404 ESTABLISHED
TCP 127.0.0.1:4404 127.0.0.1:4403 ESTABLISHED
TCP 128.194.39.115:3016 64.12.28.198:5190 ESTABLISHED
TCP 128.194.39.115:3021 64.12.27.91:5190 ESTABLISHED
TCP 128.194.39.115:3069 128.194.62.48:80 ESTABLISHED
TCP 128.194.39.115:3144 64.12.174.121:80 TIME_WAIT
TCP 128.194.39.115:3145 64.12.174.121:80 TIME_WAIT
TCP 128.194.39.115:3148 152.163.208.185:80 TIME_WAIT
TCP 128.194.39.115:3149 152.163.208.185:80 TIME_WAIT
TCP 128.194.39.115:3152 64.12.174.121:80 TIME_WAIT
TCP 128.194.39.115:3153 64.12.174.121:80 TIME_WAIT
TCP 128.194.39.115:3156 152.163.208.57:80 TIME_WAIT
TCP 128.194.39.115:3157 152.163.208.57:80 TIME_WAIT
TCP 128.194.39.115:3837 128.194.62.39:993 CLOSE_WAIT
TCP 128.194.39.115:3965 128.194.20.215:411 ESTABLISHED
TCP 128.194.39.115:3970 165.91.216.169:411 ESTABLISHED
TCP 192.168.0.1:4302 128.194.62.39:139 ESTABLISHED

kender
Posts: 3
Joined: 2003-02-11 18:08

Post by kender » 2003-02-11 19:03

I did to make sure Windows had it. Since I'm firewalled I don't suppose
there's any major harm.
[...]
128.194.39.115:3970
Giving out your ip address isn't the best of ideas ;)
What's that A&M University? :?

volkris
Posts: 121
Joined: 2003-02-02 18:07
Contact:

Post by volkris » 2003-02-12 03:49

kender wrote: Giving out your ip address isn't the best of ideas ;)
What's that A&M University? :?
I'm completely aware of the dangers of giving out my IP address. I simply trust in the security on my box :)

My box normally lives at volkstar.dyndns.org. Anyone who wants to can look up the ip of that address. Security through obscurity is not security.

Locked