No, that’s just the hash, according to avast. If I could figure out in regular MD5 or SHA-1 numbers what the hash was, I could figure out which .torrent file is causing the flag and just delete it.
Yep, I saw that thread today, though I posted this… a couple days ago. He just deleted everything, I’m not interested in doing that. I want to find the exact torrent file causing the problem. If I had an MD5 hash, I could probably figure which file it is. But alas, this string makes no sense to me. I’ve tried looking up hexadecimal converters and ASCII converters… the hex converters want to convert to other forms like binary and the ASCII ones don’t match.
But there is no hashing from avast’s side - this simply is the URL the program is trying to connect to.
Whether the tail really is a hash (probably so, according to the previous part of the URL), it has absolutely nothing to do with avast! - you’d have to ask the uTorrent author I guess.