You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally I get releases downloaded by radarr/sonarr that contain malware - usually .LNK files or .EXE files cleverly named and padded out with a gigabyte of random data to make it seem like it is a .MKV. Radarr and Sonarr end up downloading the entire torrent and then failing to import it, and then you have to go manually reject the release before it'll try another torrent.
A feature I think would be very helpful would be for Decluttarr to detect and delete those downloads. This way as soon as a torrent starts downloading that contains malicious files inside of it, Decluttarr could delete the download, instruct Radarr/Sonarr to blacklist the release, and then Radarr/Sonarr could immediately move along and try another release.
I could see this being implemented with an environment variable like REMOVE_MALWARE, with some regex on the filenames to detect if they aren't actually proper movie files inside of the torrent.
There are other workarounds for this problem such as configuring a file exclusion in QBitTorrent but IMHO this isn't a complete solution because there is no feedback loop back to Radarr / Sonarr that would tell them to blacklist that release. It seems to me like Decluttarr is an appropriate place for that kind of "rejection" of a bad torrent to happen.
The text was updated successfully, but these errors were encountered:
Occasionally I get releases downloaded by radarr/sonarr that contain malware - usually .LNK files or .EXE files cleverly named and padded out with a gigabyte of random data to make it seem like it is a .MKV. Radarr and Sonarr end up downloading the entire torrent and then failing to import it, and then you have to go manually reject the release before it'll try another torrent.
A feature I think would be very helpful would be for Decluttarr to detect and delete those downloads. This way as soon as a torrent starts downloading that contains malicious files inside of it, Decluttarr could delete the download, instruct Radarr/Sonarr to blacklist the release, and then Radarr/Sonarr could immediately move along and try another release.
I could see this being implemented with an environment variable like REMOVE_MALWARE, with some regex on the filenames to detect if they aren't actually proper movie files inside of the torrent.
There are other workarounds for this problem such as configuring a file exclusion in QBitTorrent but IMHO this isn't a complete solution because there is no feedback loop back to Radarr / Sonarr that would tell them to blacklist that release. It seems to me like Decluttarr is an appropriate place for that kind of "rejection" of a bad torrent to happen.
The text was updated successfully, but these errors were encountered: