This fixes the scrape data issue that has long plagued this software (2012).
Filtering other data is fine, but scrape data ends up going to and from the
torrent client and the tracker anyway, and they don't like the custom filters.
This was confirmed by finding and going through the original PHPBTTracker
software code and comparing it with RivetTracker.
--- a/tracker.php
+++ b/tracker.php
@@ -71,13 +71,13 @@
if (isset($_GET["info_hash"]))
{
if (get_magic_quotes_gpc())
- $info_hash = stripslashes(trim(strip_tags($_GET["info_hash"])));
+ $info_hash = stripslashes($_GET["info_hash"]);
else
- $info_hash = trim(strip_tags($_GET["info_hash"]));
+ $info_hash = $_GET["info_hash"];
if (strlen($info_hash) == 20)
- $info_hash = filterChar(bin2hex($info_hash));
+ $info_hash = bin2hex($info_hash);
else if (strlen($info_hash) == 40)
- filterInt(verifyHash($info_hash)) or showError("Invalid info hash value.");
+ verifyHash($info_hash) or showError("Invalid info hash value.");
else
showError("Invalid info hash value.");
$usehash = true;