[Bug 523540] Review Request: opentracker - BitTorrent Tracker

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=523540

--- Comment #47 from Simon Wesp <cassmodiah at fedoraproject.org> 2010-04-02 06:22:07 EDT ---
(In reply to comment #46)
> FWIW, I took the RPM that Simon kindly prepared and rebuilt it against a RHEL5
> variant (CERN Scientific Linux 5), with the CVS snapshot from 2010-03-25.
> 
> The tracker works as expected (and at least the ipv4 x86_64 binary I built does
> not suffer from the bug reported in Comment 44).
> 
> There is however an issue with the access list file (white list), enabled with
> the Makefile option "-DWANT_ACCESSLIST_WHITE". When opentracker is started, it
> states:
> 
> Warning: Can't open accesslist file: /foo/bar (but will try to create it later,
> if necessary and possible).
Does opentracker start? It has to start, this is just a warning 
You have to modify the configfile to add a whitelist or use the sysconfigfile.
Both are in /etc/ packaged.

> The error occurs although /foo/bar exists, contains valid torrent hashes, and
> is readable by the opentracker user. This is preventing any torrent to be
> handled by the tracker in case "-DWANT_ACCESSLIST_WHITE" is used.
Whitelist is a feature which is a wish of Matt Domsch to dominate and control
and restrict the freedom of the users. This feature is just enabled, but not
used by default.
/foo/bar is just a fake! Just edit one of the conffiles to use the
whitelist-feature!

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.