Back

Bucket Antivirus Support

  • 0
  • Self Hosted
  • Storage
Zhynem
24 Sep, 2024, 06:18

I've been tinkering with self hosted appwrite for the past few days, and tonight I went down the rabbit hole of the antivirus scanning. It seemed like just changing the docker-compose image to use clamav/clamav:1.3.2-71 (amd64 only) allowed it to work.

When I tried uploading a normal file it went through, and when I tried uploading the eicar.txt test file I can see in the clamav logs it properly flagged it and the upload was blocked with a 403 response. However, when I switched from local based storage to s3 storage it seems like even though Antivirus is enabled on the Appwrite bucket, it skips the step and allows the "bad" file through.

It seems like there hasn't been much done as the last clamav related post was from 2023, and in https://appwrite.io/docs/products/storage/buckets it makes no mention of antivirus settings at all so my question are, is this a feature that's going to be deprecated? Would I be better off having a custom virus scan flow sits in front of any uploads? Or is it just something that is very much on the back burner?

Thanks!

TL;DR
Developers tinkering with self-hosted Appwrite noticed that changing the Docker image to `clamav/clamav:1.3.2-71` allowed antivirus scanning to work. Uploading normal files worked fine, but switching to S3 storage caused the antivirus to skip scanning, even though it was enabled. It seems like the feature may be on the back burner, with limited recent updates on ClamAV. Considering a custom virus scan flow might be a more reliable solution for now.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more