At 11:18 AM 6/28/2004, Obantec Support wrote:
Hi Matt
I did not patch it on the off chance it was now fixed.
That's really quite strange, because 2.40 does include the taint patch.
Check the Agent.pm to make sure it's really the same as the one in the 2.40
tarball
Your paths may differ, but this
Xargs can help you get around the command line limit. It is a utility which
is used specifically when piping a lot of arguments to a command.
> -Original Message-
> From: Billy Newsom [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 26, 2004 1:43 PM
> To: [EMAIL PROTECTED]
> Subject: Re:
Hi Matt
I did not patch it on the off chance it was now fixed.
Mark
- Original Message -
From: "Matt Kettler" <[EMAIL PROTECTED]>
To: "Obantec Support" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, June 28, 2004 4:07 PM
Subject: Re: [Razor-users] taint issue with razor 2.40 and
At 03:11 AM 6/28/2004, Obantec Support wrote:
Does the patch supplied with SA 2.63 which is for razor 2.36 work with razor
2.40 or is there another patch out there.
I am seeing taint errors.
2.40 shouldn't need the taint patch, as it already has it.
If you tried to apply the patch to 2.40, wipe out
On Mon, 2004-06-28 at 14:37, Sven Willenberger wrote:
> #!/bin/bash
> for i in /z/* ; do
> /path/to/razor-report -d -home=/root/.razor $i
> done
xargs is better:
find z -type f | xargs /path/to/razor-report -d -home=/root/.razor
Cheers,
Ketil Froyn
[EMAIL PROTECTED]
http://ketil.froyn.name/
On Sun, 2004-06-27 at 21:16 -0500, Billy Newsom wrote:
> So,
> If I put 100 RFC-822 messages in "/z", and I use these two commands:
> #razor-report -M -d -home=/root/.razor /z
> #razor-report-d -home=/root/.razor /z/*
>
> Of the above two commands, the first one submits just one report (this
Hi
Does the patch supplied with SA 2.63 which is for razor 2.36 work with razor
2.40 or is there another patch out there.
I am seeing taint errors.
Mark
--
Obantec Support
---
This SF.Net email sponsored by Black Hat Briefings & Training.
At
