Clamav

Differences between revisions 30 and 31
Revision 30 as of 2007-07-12 03:38:09
Size: 5307
Editor: dsl-189-155-176-166
Comment:
Revision 31 as of 2007-07-12 04:27:24
Size: 5324
Editor: dsl-189-155-176-166
Comment:
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
      Edited debian/control adjusted dpkg-dev for '''dapper''' version 1.13.11 and removed the   source:Version for clamav-base and libclamav in all packages. Builded and installed fine. Tested with '''clamsmtp''' and '''clamassassin''' and all worked fine.
     Here is the diff for debian/control [http://paste.ubuntu-nl.org/29612/]
      Edited debian/control adjusted dpkg-dev for '''dapper''' version 1.13.11 and replaced the source:Version for clamav-base and libclamav to Source-Version in all packages. Builded and installed fine. Tested with '''clamsmtp''' and '''clamassassin''' and all worked fine.
     Here is the diff for debian/control [http://paste.ubuntu-nl.org/29616/]

Eventually there will be more 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 and get to work..

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 (nevermind, Leonel got to it first), klamav, and I will test clamtk, but don't regularly use it. Note that I'm now part of the ubuntu-backporters team that blesses backports, so the latency should go down.

["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.

    • ["Leonel"] tested clamassassin and according to [http://lists.jameslick.com/pipermail/clamassassin-announce/2007-February/000030.html] there are incompatibilities with clamav 0.90.X

    • ["Leonel"] Builded Gutsy clamassassin on dapper pbuilder installed on dapper and tested all worked fine

    • ["Leonel"] Asked for Backport Gutsy clamassassin to dapper [https://bugs.launchpad.net/dapper-backports/+bug/124938].

    • ["Leonel"] Tested dapper clamsmtp worked fine

    • ["Leonel"] Builded gutsy clamsmtpd on dapper pbuilder installed on dapper and tested all worked fine

    • ["Asommer"] tested mimedefang which worked after a few adjustments that can probably be added to the install process?

      • Added clamav user to the smmsp group. This is done because smmsp group owns /var/spool/MIMEDefang folder. ScottKitterman - This will have to be added to the mimedefang postinst then.

      • Created a symbolic link /var/spool/MIMEDefang/clamd.sock to /var/run/clamav/clamd.ctl. You can also change the LocalSocket entry in /etc/clamav/clamd.conf to use /var/spool/MIMEDefang/clamd.sock, but I'm not sure what other applications this could affect.

      • Edited /etc/mail/mimedefang-filter changed: my($code, $category, $action) = message_contains_virus();

        • to: my($code, $category, $action) = message_contains_virus_clamd();
    • ScottKitterman Tested klamav and it's built in facility to upgrade will only attempt to upgrade klamav to 0.38 (the last 0.8x compatible version) and then fail because it can't find it. It will (with the right build depencies installed (sudo apt-get build-dep clamav) build the current clamav for the user. klamav will then fail to work since it now has an incompatible clamav to work with. The current klamav will not build without a clamav 0.9x available, but should build on dapper-updates once that is backported. One little trick is that the current Klamav needs KDE 3.5.2 or better and we have 3.5.1 in Dapper. Backporting KDE will be fun, but I've already discussed it with the Kubuntu devs and it should be doable.

    • ["Leonel"] Tried to build [https://launchpad.net/ubuntu/+source/clamav/0.88.7-1ubuntu1] on Dapper and the package needs dpkg-dev >= 1.13.19 Dapper has 1.13.11 Build FAILED.

      • Edited debian/control adjusted dpkg-dev for dapper version 1.13.11 and replaced the source:Version for clamav-base and libclamav to Source-Version in all packages. Builded and installed fine. Tested with clamsmtp and clamassassin and all worked fine.

    • ["Leonel"] Builded [https://launchpad.net/ubuntu/+source/clamav/0.88.4-1ubuntu2.1] on Dapper. Builded and installed. Tested clamsmtp and clamassassin all worked fine.

  • 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 and approved a backport).
  • And just to keep in interesting, clamav 0.91 was just released and will enable a bunch of anti-phishing stuff, so stand by for more fun. I'll backport that to Feisty once we have it from Debian.

MOTU/Clamav (last edited 2012-07-14 06:34:56 by static-72-81-252-21)