Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ClamAV does not automatically scan downloaded torrents #2010

Open
3 tasks
jenno-verdonck opened this issue Dec 8, 2024 · 4 comments
Open
3 tasks

ClamAV does not automatically scan downloaded torrents #2010

jenno-verdonck opened this issue Dec 8, 2024 · 4 comments

Comments

@jenno-verdonck
Copy link

jenno-verdonck commented Dec 8, 2024

I was migrating my torrent server to the new 18.0 version. I run my server on Proxmox in a container and store all my data on a separate drive. I then change all the fileserver paths and download path for Transmission. In doing so I tried to find how the clamAV program is configured. In doing so I noticed that clamAV is totally not configured to even scan the downloaded torrent files. The ClamAV OnAccessIncludePath is not set, so it doesn't watch that folder. The transmission script-torrent-done-filename parameter is also not set so this also doesn't trigger a scan by using a script. The directory structure of the /srv/storage folder also seems a bit weird as only the download folder is used while the folders that where probably used for the previous torrent server (rTorrent) are still there (incoming and quarantine). It seems that when the torrent server was changed from using rTorrent to Transmission that not everything was changed with it and some artifacts remain such as the unused folders and the not working ClamAV.


Summary of issues:

  • clamav scan of directory: OnAccessIncludePath (i.e. folder to watch) not configured; and/or
  • clamav scan of download - set transmission script-torrent-done-filename parameter to run clamav scan on completion
  • default /srv/storage directory tree has irrelevant and outdated paths
@JedMeister
Copy link
Member

Thanks so much for reporting this @jenno-verdonck.

From a quick glance it looks like you are absolutely right and there are a number of things that haven't been updated properly in updates/changes along the way.

I'll have a closer look ASAP.

@JedMeister
Copy link
Member

I hope you don't mind but I've added a summary of the separate issues you've noted & need to be addressed. That will make it easier to see what needs to be done at a glance. If I've missed anything, please feel free to update/edit the summary.

@JedMeister JedMeister added this to the 18.1 milestone Dec 8, 2024
@jenno-verdonck
Copy link
Author

Thank you for the quick response. The summery includes everything I think. One thing to note is that the first and second bullet are just 2 ways to achieve the same thing (aka making ClamAV working). The first method sets a folder to watch for ClamAV so that a scan is triggered when your server reads a file from that folder. The second method is a way of defining a script to run when a torrent is done. This way a torrent can call ClamAV for a scan perhaps.

@JedMeister
Copy link
Member

Thanks for the clarification. I've updated it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants