Stephen Gran <[EMAIL PROTECTED]> writes:
>> > Some various solutions have been discussed with upstream, but it is
>> > up to upstream to implement one of them - I am not going to add the
>> > code complexity as a Debian specific patch.
>>
>> Excuse me? The dlopen() patch I provided in #484670 for
This one time, at band camp, Hilko Bengen said:
> Stephen Gran <[EMAIL PROTECTED]> writes:
>
> > I would love to, believe me. Unfortunately the main code base is GPL
> > and the unrar code is licensed incompatibly.
>
> It doesn't look as if fixing this licensing problem is a top priority
> on up
Stephen Gran <[EMAIL PROTECTED]> writes:
> I would love to, believe me. Unfortunately the main code base is GPL
> and the unrar code is licensed incompatibly.
It doesn't look as if fixing this licensing problem is a top priority
on upstream's list. Which is fine. They apparently operate in a
sli
> Unfortunately the main code base is GPL
> and the unrar code is licensed incompatibly.
So send clamav to contrib?
> Some various solutions have
> been discussed with upstream, but it is up to upstream to implement one
> of them
Till then the INFO-file (sid, lenny, packages.debian.org) contains a
This one time, at band camp, Olaf Schulz said:
> Can you find a new working solution to enable scanning of these
> infected rar files?
I would love to, believe me. Unfortunately the main code base is GPL
and the unrar code is licensed incompatibly. The problem is not, as
many people seem to beli
On Sun, Aug 10, 2008 at 10:11 PM, Olaf Schulz
<[EMAIL PROTECTED]> wrote:
> Can you find a new working solution to enable scanning of these infected rar
> files?
Until a solution to scan .rar files is found, why not reject any
message with such an attachment? I find it quite acceptable to accept
.z
I found some infected files similar to those mentioned in Carsten
Leonhardt's report. So I learnt about the issues with unrar and found
this bug report.
Forwarding this bug upstream resulted in removing support for external
unpackers: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1050#c7
> Could you submit the email to upstream as a failed scan? It sounds like
> a bug in the base64 parser.
Reported as https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1050
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
This one time, at band camp, Carsten Leonhardt said:
> The first example shows scanning a file which is an email containing a
> mime/base64 encoded rar-file which in turn contains a trojan. The
> second example shows scanning the rar-file directly, which works out
> ok:
Could you submit the email
Package: clamav
Version: 0.93~dfsg-volatile1
Severity: normal
The first example shows scanning a file which is an email containing a
mime/base64 encoded rar-file which in turn contains a trojan. The
second example shows scanning the rar-file directly, which works out
ok:
--- 1 ---
$ clamscan --u
10 matches
Mail list logo
