Mailing List Archive

Hi there,

On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:

> Hello, I am running into a bug/error when adding an ExcludePath to my clamd.conf
> I am running Ubuntu 20.04.2, with clamav 0.103.1(from source)
> When I add the line: ExlucudePath .*\.sys$, the following issues occur when
> running the command "clamdscan -m --fdpass /path/to/mounted/filesystem
> *Note: This error occurs only when using the -m parameter in combination
> with --fdpass against a Mounted filesystem other than the main harddrive*
>
> Running it against my home directory
> [image: image.png]
> Running it against a mounted filesystem with data in it
> [image: image.png]
> I tested this on over 50 different mounted filesystem, and the same error
> occurs.
>
> Is there any fix to this?

You are using the asterisk charater in your command lines incorrectly.
You need to quote it (and any other 'special' characters you use in a
command), or (in the case of a path) quote the entire path. Otherwise
the shell will expand the asterisk which will result in a command very
unlike the one you intended. See the 'man' page for the bash shell:

man bash

But, even with incorrect command lines, there should not be segfaults.

Check the ClamAV bugzilla, and if you don't find anything which seems
to describe your issue please either open a new report yourself or reply
here and someone will be able to open one:

https://bugzilla.clamav.net/buglist.cgi?component=clamd&product=ClamAV

--

73,
Ged.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

I changed the ExcludePath to:
.*\.sys$

The error still occurs. I do a ticket created for an identical issue.
It looks like there is a patch to fix the problem, but I’m not sure how to
apply said patch

On Thu, Mar 4, 2021 at 11:21 AM G.W. Haywood via clamav-users <
clamav-users@lists.clamav.net> wrote:

> Hi there,
>
> On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:
>
> > Hello, I am running into a bug/error when adding an ExcludePath to my
> clamd.conf
> > I am running Ubuntu 20.04.2, with clamav 0.103.1(from source)
> > When I add the line: ExlucudePath .*\.sys$, the following issues occur
> when
> > running the command "clamdscan -m --fdpass /path/to/mounted/filesystem
> > *Note: This error occurs only when using the -m parameter in combination
> > with --fdpass against a Mounted filesystem other than the main harddrive*
> >
> > Running it against my home directory
> > [image: image.png]
> > Running it against a mounted filesystem with data in it
> > [image: image.png]
> > I tested this on over 50 different mounted filesystem, and the same error
> > occurs.
> >
> > Is there any fix to this?
>
> You are using the asterisk charater in your command lines incorrectly.
> You need to quote it (and any other 'special' characters you use in a
> command), or (in the case of a path) quote the entire path. Otherwise
> the shell will expand the asterisk which will result in a command very
> unlike the one you intended. See the 'man' page for the bash shell:
>
> man bash
>
> But, even with incorrect command lines, there should not be segfaults.
>
> Check the ClamAV bugzilla, and if you don't find anything which seems
> to describe your issue please either open a new report yourself or reply
> here and someone will be able to open one:
>
> https://bugzilla.clamav.net/buglist.cgi?component=clamd&product=ClamAV
>
> --
>
> 73,
> Ged.
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>

Hi there,

On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:
> On Thu, Mar 4, 2021 at 11:21 AM G.W. Haywood via clamav-users wrote:
>
>> You are using the asterisk charater in your command lines incorrectly.
>> You need to quote it (and any other 'special' characters you use in a
>> command), or (in the case of a path) quote the entire path. Otherwise
>> the shell will expand the asterisk ...
>
> I changed the ExcludePath to:
> .*\.sys$
>
> The error still occurs. I do a ticket created for an identical issue.
> It looks like there is a patch to fix the problem, but I’m not sure how to
> apply said patch

The asterisks in your command lines, not in your configuration file.

--

73,
Ged.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Oh I see, sorry. I’ve always been using that to recursively scan. If I
remove the asterisk completely will it still do the same thing?

On Thu, Mar 4, 2021 at 12:40 PM G.W. Haywood via clamav-users <
clamav-users@lists.clamav.net> wrote:

> Hi there,
>
> On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:
> > On Thu, Mar 4, 2021 at 11:21 AM G.W. Haywood via clamav-users wrote:
> >
> >> You are using the asterisk charater in your command lines incorrectly.
> >> You need to quote it (and any other 'special' characters you use in a
> >> command), or (in the case of a path) quote the entire path. Otherwise
> >> the shell will expand the asterisk ...
> >
> > I changed the ExcludePath to:
> > .*\.sys$
> >
> > The error still occurs. I do a ticket created for an identical issue.
> > It looks like there is a patch to fix the problem, but I’m not sure how
> to
> > apply said patch
>
> The asterisks in your command lines, not in your configuration file.
>
> --
>
> 73,
> Ged.
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>

Hi Michael,

It looks to me like you've stumbled across this issue: https://bugzilla.clamav.net/show_bug.cgi?id=12676

I have a fix on the way. The attached patch works, though I am still tidying up some additional error handling cleanup work per peer review.

Regards,
Micah

> -----Original Message-----
> From: clamav-users <clamav-users-bounces@lists.clamav.net> On Behalf Of
> G.W. Haywood via clamav-users
> Sent: Thursday, March 4, 2021 8:20 AM
> To: Michael Kyriacou via clamav-users <clamav-users@lists.clamav.net>
> Cc: G.W. Haywood <clamav@jubileegroup.co.uk>
> Subject: Re: [clamav-users] ExcludePath Segmentation Fault Errorr
>
> Hi there,
>
> On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:
>
> > Hello, I am running into a bug/error when adding an ExcludePath to my
> > clamd.conf I am running Ubuntu 20.04.2, with clamav 0.103.1(from
> > source) When I add the line: ExlucudePath .*\.sys$, the following
> > issues occur when running the command "clamdscan -m --fdpass
> > /path/to/mounted/filesystem
> > *Note: This error occurs only when using the -m parameter in
> > combination with --fdpass against a Mounted filesystem other than the
> > main harddrive*
> >
> > Running it against my home directory
> > [image: image.png]
> > Running it against a mounted filesystem with data in it
> > [image: image.png]
> > I tested this on over 50 different mounted filesystem, and the same
> > error occurs.
> >
> > Is there any fix to this?
>
> You are using the asterisk charater in your command lines incorrectly.
> You need to quote it (and any other 'special' characters you use in a command),
> or (in the case of a path) quote the entire path. Otherwise the shell will expand
> the asterisk which will result in a command very unlike the one you intended.
> See the 'man' page for the bash shell:
>
> man bash
>
> But, even with incorrect command lines, there should not be segfaults.
>
> Check the ClamAV bugzilla, and if you don't find anything which seems to
> describe your issue please either open a new report yourself or reply here and
> someone will be able to open one:
>
> https://bugzilla.clamav.net/buglist.cgi?component=clamd&product=ClamAV
>
> --
>
> 73,
> Ged.
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

How can I apply this patch?

On Sat, Mar 6, 2021 at 5:03 PM Micah Snyder (micasnyd) via clamav-users <
clamav-users@lists.clamav.net> wrote:

> Hi Michael,
>
> It looks to me like you've stumbled across this issue:
> https://bugzilla.clamav.net/show_bug.cgi?id=12676
>
> I have a fix on the way. The attached patch works, though I am still
> tidying up some additional error handling cleanup work per peer review.
>
> Regards,
> Micah
>
> > -----Original Message-----
> > From: clamav-users <clamav-users-bounces@lists.clamav.net> On Behalf Of
> > G.W. Haywood via clamav-users
> > Sent: Thursday, March 4, 2021 8:20 AM
> > To: Michael Kyriacou via clamav-users <clamav-users@lists.clamav.net>
> > Cc: G.W. Haywood <clamav@jubileegroup.co.uk>
> > Subject: Re: [clamav-users] ExcludePath Segmentation Fault Errorr
> >
> > Hi there,
> >
> > On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:
> >
> > > Hello, I am running into a bug/error when adding an ExcludePath to my
> > > clamd.conf I am running Ubuntu 20.04.2, with clamav 0.103.1(from
> > > source) When I add the line: ExlucudePath .*\.sys$, the following
> > > issues occur when running the command "clamdscan -m --fdpass
> > > /path/to/mounted/filesystem
> > > *Note: This error occurs only when using the -m parameter in
> > > combination with --fdpass against a Mounted filesystem other than the
> > > main harddrive*
> > >
> > > Running it against my home directory
> > > [image: image.png]
> > > Running it against a mounted filesystem with data in it
> > > [image: image.png]
> > > I tested this on over 50 different mounted filesystem, and the same
> > > error occurs.
> > >
> > > Is there any fix to this?
> >
> > You are using the asterisk charater in your command lines incorrectly.
> > You need to quote it (and any other 'special' characters you use in a
> command),
> > or (in the case of a path) quote the entire path. Otherwise the shell
> will expand
> > the asterisk which will result in a command very unlike the one you
> intended.
> > See the 'man' page for the bash shell:
> >
> > man bash
> >
> > But, even with incorrect command lines, there should not be segfaults.
> >
> > Check the ClamAV bugzilla, and if you don't find anything which seems to
> > describe your issue please either open a new report yourself or reply
> here and
> > someone will be able to open one:
> >
> > https://bugzilla.clamav.net/buglist.cgi?component=clamd&product=ClamAV
> >
> > --
> >
> > 73,
> > Ged.
> >
> > _______________________________________________
> >
> > clamav-users mailing list
> > clamav-users@lists.clamav.net
> > https://lists.clamav.net/mailman/listinfo/clamav-users
> >
> >
> > Help us build a comprehensive ClamAV guide:
> > https://github.com/vrtadmin/clamav-faq
> >
> > http://www.clamav.net/contact.html#ml
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>

https://www.thegeekstuff.com/2014/12/patch-command-examples/

Eero

On Sun 7. Mar 2021 at 0.20, Michael Kyriacou via clamav-users <
clamav-users@lists.clamav.net> wrote:

> How can I apply this patch?
>
> On Sat, Mar 6, 2021 at 5:03 PM Micah Snyder (micasnyd) via clamav-users <
> clamav-users@lists.clamav.net> wrote:
>
>> Hi Michael,
>>
>> It looks to me like you've stumbled across this issue:
>> https://bugzilla.clamav.net/show_bug.cgi?id=12676
>>
>> I have a fix on the way. The attached patch works, though I am still
>> tidying up some additional error handling cleanup work per peer review.
>>
>> Regards,
>> Micah
>>
>> > -----Original Message-----
>> > From: clamav-users <clamav-users-bounces@lists.clamav.net> On Behalf Of
>> > G.W. Haywood via clamav-users
>> > Sent: Thursday, March 4, 2021 8:20 AM
>> > To: Michael Kyriacou via clamav-users <clamav-users@lists.clamav.net>
>> > Cc: G.W. Haywood <clamav@jubileegroup.co.uk>
>> > Subject: Re: [clamav-users] ExcludePath Segmentation Fault Errorr
>> >
>> > Hi there,
>> >
>> > On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:
>> >
>> > > Hello, I am running into a bug/error when adding an ExcludePath to my
>> > > clamd.conf I am running Ubuntu 20.04.2, with clamav 0.103.1(from
>> > > source) When I add the line: ExlucudePath .*\.sys$, the following
>> > > issues occur when running the command "clamdscan -m --fdpass
>> > > /path/to/mounted/filesystem
>> > > *Note: This error occurs only when using the -m parameter in
>> > > combination with --fdpass against a Mounted filesystem other than the
>> > > main harddrive*
>> > >
>> > > Running it against my home directory
>> > > [image: image.png]
>> > > Running it against a mounted filesystem with data in it
>> > > [image: image.png]
>> > > I tested this on over 50 different mounted filesystem, and the same
>> > > error occurs.
>> > >
>> > > Is there any fix to this?
>> >
>> > You are using the asterisk charater in your command lines incorrectly.
>> > You need to quote it (and any other 'special' characters you use in a
>> command),
>> > or (in the case of a path) quote the entire path. Otherwise the shell
>> will expand
>> > the asterisk which will result in a command very unlike the one you
>> intended.
>> > See the 'man' page for the bash shell:
>> >
>> > man bash
>> >
>> > But, even with incorrect command lines, there should not be segfaults.
>> >
>> > Check the ClamAV bugzilla, and if you don't find anything which seems to
>> > describe your issue please either open a new report yourself or reply
>> here and
>> > someone will be able to open one:
>> >
>> > https://bugzilla.clamav.net/buglist.cgi?component=clamd&product=ClamAV
>> >
>> > --
>> >
>> > 73,
>> > Ged.
>> >
>> > _______________________________________________
>> >
>> > clamav-users mailing list
>> > clamav-users@lists.clamav.net
>> > https://lists.clamav.net/mailman/listinfo/clamav-users
>> >
>> >
>> > Help us build a comprehensive ClamAV guide:
>> > https://github.com/vrtadmin/clamav-faq
>> >
>> > http://www.clamav.net/contact.html#ml
>>
>> _______________________________________________
>>
>> clamav-users mailing list
>> clamav-users@lists.clamav.net
>> https://lists.clamav.net/mailman/listinfo/clamav-users
>>
>>
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>>
>> http://www.clamav.net/contact.html#ml
>>
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>