#443 XDCC sends are recieved as malformed in 2.0.4

closed-out-of-date
nobody
None
5
2003-11-16
2003-11-05
No

Everytime I try to request a package from an xdcc bot X
- Chat recieves it as a malformed dcc request. It does
the same when trying to request it with either /msg or
/ctcp xdcc send #.

Here is an example of what happens:

>DH Jing< XDCC SEND #1
eps01.avi"), which is 233MB (resume supported)
--- Received a malformed DCC request from DH Jing.
--- Contents of packet: DCC SEND
[AA]_[US]_DNA_eps01.avi 2394150078 64 244785152
<-- Schiesty has quit (Remote host closed the connection)
>DH Loki< CTCP XDCC SEND #1
-DH Loki- *** Sending you pack #1 ("[AA-F] DN Angel 18
[69269f9e]"), which is 200MB (resume supported)
--- Received a malformed DCC request from DH Loki.
--- Contents of packet: DCC SEND
[aa-f]_DN_Angel_18_[69269f9e].avi 3507593227 60 209983488

This has been a reoccuring bug in Xchat since about
2.0.3 or 2.0.2.

Discussion

  • Peter Zelezny.

    Peter Zelezny. - 2003-11-06
    • status: open --> open-out-of-date
     
  • Peter Zelezny.

    Peter Zelezny. - 2003-11-06

    Logged In: YES
    user_id=5012

    The reason is that port "60" was denied by previous versions
    of xchat. Clients should not be offering DCC with those
    ports, but Windows really does what it likes regardless.
    2.0.5 allows you to receive DCC from ports below 1024.

     
  • Peter Zelezny.

    Peter Zelezny. - 2003-11-16
    • status: open-out-of-date --> closed-out-of-date
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks