[OpenIndiana-discuss] Availability of c-icap with clamav support?

[Andrej Javoršek]

Hello!
After installation, setup, initial testing with c-icap-client I came to an
issue I don't know how to solve.
It seems that default response of c-icap 0.2.2 has changed from
c-icap 060708rc, days in (vscan) incompatibile ways!

After enabling vscan on OI I'm getting errors:
Nov 21 12:50:57 v7 vscand: [ID 586775 daemon.error] ICAP protocol error -
unsupported scan result: Bad Request

Also files are inaccessible (that is probably normal with that type of
error).

After googling/testing/reading vscan code (that one was specialy unplesant)
 :) I came to the conclusion that basic response of c-icap has changed from:

- Working old c-icap:
#./c_icap-0.2.2/utils/c-icap-client -f rotor_position_detect-01.pdf -s
"avscan" -d 9 -i XXX.XXX.XXX.XXX | head
ICAP server:XXX.XXX.XXX.XXX, ip:XXX.XXX.XXX.XXI, port:1344

Allocate a new entity of type 1
Allocate a new entity of type 3
Preview response was with status: 204
No modification needed (Allow 204 response)
Done

- into not working new:
#./c_icap-0.2.2/utils/c-icap-client -f rotor_position_detect-01.pdf -s
"avscan" -d 9 | head
ICAP server:localhost, ip:127.0.0.1, port:1344

Allocate a new entity of type 1
Allocate a new entity of type 3
Preview response was with status: 100
Response was with status:204
No modification needed (Allow 204 response)
Done

So with old 060708rc version there is only one response "Preview" that is
normali 204, but in new 0.2.2 version the "Preview" response is 100 and
only after that comes 204 response (thus vscand "ICAP protocol error -
unsupported scan result: Bad Request"!??).
I have tried to modify directives in virus_scan.conf into
"virus_scan.Allow204Responces off" but could not get desiered behaviour.

Best Regards
Andrej




On Tue, Oct 30, 2012 at 10:26 PM, Milan Jurik <milan.jurik at xylab.cz> wrote:

> Hi Andrej,
>
> On út, 2012-10-30 at 21:51 +0100, Andrej Javoršek wrote:
> > I can try to do that, but I'm missing up-to-date instructions how to
> > build/prepare SFE package since instructions from wiki (
> > http://wiki.openindiana.org/oi/Building+SFE+Packages) are  more than a
> year
> > and half old and are referring to (now unavailable) patched version of
> > SunStudio.
> >
>
> c-icap-modules should contain clamav support, I updated packages in the
> repo now. I stopped to use it some time ago because I had stability
> issues with vscan support in ZFS from its beginning. No idea about the
> current quality.
>
> Yes, wiki page is not updated, e.g. because I have no time to do that
> and oi-cbe needs updates. You do not need the old Studio version, you
> can go and download the latest from Oracle. Probably some tweaks are
> needed in the script on wiki but, sorry, I have no time for updating it,
> somebody else should go through that.
>
> Best regards,
>
> Milan
>
> > Best Regards
> > Andrej
> >
> > On Tue, Oct 30, 2012 at 1:42 PM, Jim Klimov <jimklimov at cos.ru> wrote:
> >
> > > 2012-10-30 16:03, Andrej Javoršek пишет:
> > >
> > >  Hello,
> > >> couple of years back I builded zfs vscan solution using this manual:
> > >> http://www.c0t0d0s0.org/**uploads/vscanclamav.pdf<
> http://www.c0t0d0s0.org/uploads/vscanclamav.pdf>
> > >> While this server still works I decided to update/refresh/rebuild -it
> with
> > >> newer versions of components.
> > >> On today (modern) version of OI I can find both packages already
> included
> > >> (in sfe) but it seems that c-icap is missing support for clamav?!
> > >>
> > >> Are there any other packages or workarounds to enable that support
> since I
> > >> would like to avoid self-build/self-suport of those components.
> > >>
> > >
> > >
> > > I think, the best solution would be to do the self-build once more
> > > based on the SFE recipes, adding the options you need, and when you
> > > are satisfied with the result - integrate the recipe changes along
> > > with rationale for the changes upstream to SFE (I think you'd need
> > > to mail Milan Jurik for more details).
> > >
> > > HTH,
> > > //Jim Klimov
> > >
> > > ______________________________**_________________
> > > OpenIndiana-discuss mailing list
> > > OpenIndiana-discuss@**openindiana.org<
> OpenIndiana-discuss at openindiana.org>
> > > http://openindiana.org/**mailman/listinfo/openindiana-**discuss<
> http://openindiana.org/mailman/listinfo/openindiana-discuss>
> > >
> > _______________________________________________
> > OpenIndiana-discuss mailing list
> > OpenIndiana-discuss at openindiana.org
> > http://openindiana.org/mailman/listinfo/openindiana-discuss
>
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>