mldonkey-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-users] feature requests: disconnect client after full chunk; c


From: devein
Subject: [Mldonkey-users] feature requests: disconnect client after full chunk; change client md4 every 24h
Date: Thu, 20 Feb 2003 17:34:17 +0100

1. disconnect client after full chunk uploaded
uploading big amounts to one client has an effect in worse spreading of
files.

      Network C Client Name IP Address C.B DL UL Filename
      Donkey I bsuqqg 00.223.139.246 nML 0 47.4M asdreReactor.avi
      Donkey D szregw 00.220.15.4 nML 0 43.1M ShareReactor.avi
      Donkey D dzgngs 00.110.28.176 nML 0 32.1M ShareReactor.avi
      Donkey D seef 000.115.133.133 nML 360.3k 27.0M ShareReactor.avi
      Donkey D fkixbw 00.34.44.148 nML 0 26.0M ShareReactor.avi
      Donkey D Kravjek391 000.250.11.27 nML 0 25.3M ShareReactor.avi
      Donkey I tomala-mac 000.244.113.170 nEM 0 16.5M ODBC].(Osloskop).avi


2.  change client md4 every 24h
 there is a possibility of md4 spoofing, (an emule mod spoofing md4 has been
released, also there is a emule utility for seeing source stats,their md4,
rating etc -  "MetMedic"  - http://www.crackman.soft-ware.de/ ).
mldonkey cvs currently uses emule md4 , so it is also vulnerable.
IMHO the best fix  is to randomise client-md4 every start/every 24h. it wont
profit from emule credits, but it wont be touched by emule credit system
insecurities and emule credits system will totally not work for  mldonkey
clients.
i think it is not breaking edonkey protocol.

so,what you think?

devein






reply via email to

[Prev in Thread] Current Thread [Next in Thread]