On Jul 19, 2011, at 12:11, Toplak Daniel wrote:
> My approach via the mod_clamav output filter blocks the content be delivered
> to the client and breaks the checkout/update with a http status 500 and a
> information in the http status line.
I'm still curious: does this really work? For an "sv
On Tue, Jul 19, 2011 at 8:06 AM, Toplak Daniel wrote:
> I want to implement a server side scanning for malicious content in both
> ways: when commits arrive and when checkouts updates are send to the client.
>
> The first way is running fine via a pre-commit hook which extracts the
> content fro
etreff: Re: Content scanning during checkout/update
On Jul 19, 2011, at 07:06, Toplak Daniel wrote:
> I want to implement a server side scanning for malicious content in both
> ways: when commits arrive and when checkouts updates are send to the client.
> The first way is running fine vi
On Jul 19, 2011, at 07:06, Toplak Daniel wrote:
> I want to implement a server side scanning for malicious content in both
> ways: when commits arrive and when checkouts updates are send to the client.
> The first way is running fine via a pre-commit hook which extracts the
> content from the t
Hi,
I want to implement a server side scanning for malicious content in both ways:
when commits arrive and when checkouts updates are send to the client.
The first way is running fine via a pre-commit hook which extracts the content
from the transaction and scan the content with clamav.
My prob
