![]() ![]() BEncode Editor doesn't make it that much simpler to change trackers than TorrentEditor. What the users do with it is not of my concern. I created BEncode Editor to allow users to edit BEncoded files, plain and simple. ![]() And anyway, how does BEncode Editor let you announce more quickly to trackers than just editing the torrent properties? You'd still be subject to the exact same issues.Īt any rate, "moral" issues are the last of my worries. That's no different from adding the torrent stopped (or just stopping the torrent for a while), and then changing the passkey. But we do have a option for resetting the passkey.ġ. ![]() This is because, hashing with a particular algorithm always yields a single result. I suppose the trackers must usually employ their own table to maintain the passkeys. Moreover "sha1" yields a 160 bit key, as opposed to 128 bit passkey(explained as above). I guess you should have confused with this. This value will almost certainly have to be escaped. Note that this is a substring of the metainfo file. The 20 byte sha1 hash of the bencoded form of the info value from the metainfo file. This means the key length is 32*4=128 bit, a lengthy one to discourage specification:( ) But i would like to clarify your answer some more.Private trackers(I personally checked four) usually use 32 character(but range from 0-9 and a-f, meaning they must be Hex). Brute-forcing the passkey is quite a costly task. This alerts the tracker to see two different passkeys within a very short interval of time from the same PC.Ģ.You are right. As soon as you change your passkey, the client contacts the tracker. And changing the tracker passkey using torrents properties dialog lands you into trouble.This is because your bittorrent client connects your tracker for update as soon as you open the client(Independent of your scheduler). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |