Clamav
2045
Comment:
|
2172
|
Deletions are marked like this. | Additions are marked like this. |
Line 21: | Line 21: |
* ["Asommer"] tested '''p3scan''' and it works fine. It simply uses the '''clamscan''' utility and doesn't make use of the API directly so I think it will work with any version of clamav. | * ["Asommer"] tested '''p3scan''' and it works fine. It simply uses the '''clamscan''' utility and doesn't make use of the API directly so I think it will work with any version of clamav. As long as your ''scanner = /usr/bin/clamscan -i'' statement in the p3scan.conf file uses correct clamscan arguments, anyway. |
Eventually there will be content here about how we are going to test/support clamav and it's rdepends in released Ubuntu versions. In the mean time, join the ubuntu-clamav team.
If you are interested in building/testing stuff leave a note here about what you use. We'll get it more organized later.
ScottKitterman - clamsmtp with Postfix, klamav, and I will test clamtk, but don't regularly use it.
["Asommer"] - I use it with clamav-milter and sendmail to scan messages on an internal mail server.
["Leonel"] - I Work with clamav and clamsmtp. Tested clamav 0.90.3 ( from [http://www.kitterman.com/clamav ] with clamsmtp all worked fine.
Steps for Clamav Backport
Step one is for ScottKitterman to get a draft package for a clamav 0.90.3 backport to Dapper out for people to use. The draft source package can be found at [http://www.kitterman.com/clamav my domain]. The i386 binaries are posted. Others please build for other archs and add links to where to get them.
- Step two is to test different packages that use clamav against this package and see which work and which don't (note please say who you are if you test stuff).
["Asommer"] tested mediawiki and it seems to work fine. I'm not sure why it's listed as a dependency?
["Asommer"] tested p3scan and it works fine. It simply uses the clamscan utility and doesn't make use of the API directly so I think it will work with any version of clamav. As long as your scanner = /usr/bin/clamscan -i statement in the p3scan.conf file uses correct clamscan arguments, anyway.
- Step three is to prepare backports of the packages that don't work.
- Step four is massive backport of all of the needed updates at the same time so nothing (promise) breaks.
- Step five: Move to Edgy, rinse, repeat.
- In the meantime, people running Feisty can check the rdpends and make sure nothing got missed during Feisty development.
- (I know clamtk did and I've already asked for a backport).
- And just to keep in interesting, clamav 0.91 is at rc2 and will enable a bunch of anti-phishing stuff, so stand by for more fun.
MOTU/Clamav (last edited 2012-07-14 06:34:56 by static-72-81-252-21)