ports/92662: net-p2p/ctorrent port contains multiple problems

Jeffrey H. Johnson COE1704TKS at bellsouth.net
Wed Feb 1 03:20:04 UTC 2006


>Number:         92662
>Category:       ports
>Synopsis:       net-p2p/ctorrent port contains multiple problems
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 01 03:20:02 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Jeffrey H. Johnson
>Release:        FreeBSD 6.0-STABLE i386
>Organization:
>Environment:
System: FreeBSD offworld.cqasys.com 6.0-STABLE FreeBSD 6.0-STABLE #21: Wed Jan 18 22:35:45 EST 2006 root at offworld.cqasys.com:/usr/src/sys/i386/compile/OFFWORLD i386

>Description:

	The net-p2p/ctorrent has multiple issues that are unresolved, as it appears that
no work has been done on the ctorrent program in over 2 years.  These problems include
many bugs in the bandwidth limiting areas as well as many overflows that result in ctorrent
sending invalid data to trackers (-35805235 bytes) and also problems with files over 2GB
in size.  This has resulted in ctorrent being unusable for the majority of trackers on the
internet today.  Most of these trackers block "ctorrent".  Patching is an option and many
of these patches are available and could be collected, but is this worthwhile?

It is my opinion that ctorrent should be depreceated in favor of another client that is
based on ctorrent but maintained.  Many of these exist.  I would suggest ectorrent, which
is available from http://www.rahul.net/dholmes/ctorrent/ and has specific FreeBSD support.

I can easily submit a port for ectorrent if the ctorrent maintainer does not wish to.

Maintainer cc'd: flz at FreeBSD.org
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list