
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!
Recommended threads
- Invalid credentials after migration
Hi everyone! After migrating our self-hosted Appwrite 1.3.1 to another server (staging, so a different domain), we are now getting 'Invalid credentials' when ...
- implement caching
It it possible to cache response for few minutes? I dont want to create function or implement a whole reverse server just to cache it in somewhere ?
- I am getting a 401 unauthorized response...
I have a Next.js application that stores user PDFs. I'm able to save them normally, but when trying to access the files using getFileView, I get a 401 Unauthori...
