Originally Posted by
anon
I think no tracker frontend should include "default" scripts for security reasons. If the admin really cares about cheating, he'll code them, and a script coming installed with every frontend bundle should be easy to check and work around against.
Are you sure Gazelle has some? I flashed 10GB with the PMR at ScR - no problems.
yes by looking at the database structure of the modified XBTT that comes with Gazelle:
Code:
--
-- Table structure for table `cheater_log`
--
DROP TABLE IF EXISTS `cheater_log`;
CREATE TABLE `cheater_log` (
`ID` int(5) NOT NULL auto_increment,
`Client` varchar(8) default NULL,
`User` int(10) default NULL,
`TorrentID` int(10) default NULL,
`Test` int(2) default NULL,
`Time` timestamp NOT NULL default CURRENT_TIMESTAMP,
`Peers` text,
`GroupID` int(10) default NULL,
PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
and also these lines are in the modified XBTT :
if (i != file.peers.end())
{
connectable = i->second.listening;
if (i->second.peer_id == v.m_peer_id
&& v.m_downloaded >= i->second.downloaded
&& v.m_uploaded >= i->second.uploaded)
{
downloaded = m_config.m_freetorrent && file.freetorrent ? 0 : v.m_downloaded - i->second.downloaded;
uploaded = v.m_uploaded - i->second.uploaded;
timespent = time() - i->second.mtime;
if ((downloaded || uploaded) && timespent)
{
upspeed = uploaded / timespent;
downspeed = downloaded / timespent;
if (m_config.m_cheater && upspeed > m_config.m_cheater_speed)
{
try
{
Csql_query q(m_database,
"INSERT INTO xbt_cheat (uid, ipa, upspeed, uploaded, tstamp) VALUES (?, ?, ?, ?, ?)");
q.p(user->uid);
q.p(ntohl(v.m_ipa));
q.p(upspeed);
q.p(v.m_uploaded);
q.p(time());
q.execute();
now this code is referring to a config file :
which is the speed to see if the user or not:
Code:
m_cheater_speed = 26214400;
now as for ScR, either they could not compile [build] the modified XBTT and used the original XBTT or they disabled the anti-flash
Bookmarks