Re: [clamav-users] update report

2018-07-05 Thread Micah Snyder
Sorry for the delayed response, all:

The issue facing those without IPv6 compatible hardware or networks came to 
light earlier in the CloudFlare mirror-transition.  A ticket that both alerted 
us to the issue and provided a fix was prvoided in a bug courtesy of Guilherme 
Benkenstein:
https://bugzilla.clamav.net/show_bug.cgi?id=12119

As stated in the final comment, I have added the patch to our development 
branch for v0.101 and the upcoming v0.100.1 patch release.

0.101:
https://github.com/Cisco-Talos/clamav-devel/commit/f4861c670167a7a109340c1f8579a55205acbd8a

0.100.1:
https://github.com/Cisco-Talos/clamav-devel/commit/9fd6d90afab40b5e3e3fe456d337eecce670fa50

The 0.100.1 patch release is in testing and will be published very soon.  My 
apologies to those who have been frustrated by IPv4-IPv6 related connection 
issues.  With any luck, this patch release will resolve things.

Regards,
Micah


On Jul 2, 2018, at 1:56 PM, Joel Esler mailto:jesler at 
cisco.com>> wrote:
> On Jul 2, 2018, at 1:56 PM, Gene Heskett  shentel.net> wrote:
> 
> but even on my setups which have this for years freshclam repetaly
> produces ipv6 crap-messages which is simpyl wrong
> 
> If thats the case, and I'll find out by this time tomorrow, then I can't
> help but agree, its a bug. Not a showstopper, but one to be swatted in
> the next upgrade for us folks out here in the ipv4 only puckerbrush.
> 
> 
> It's definitely on our radar.  Micah may want to comment further.
> 
> --
> Joel Esler
> Sr. Manager
> Open Source, Design, Web, and Education
> Talos Group
> http://www.talosintelligence.com
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-03 Thread Reindl Harald


Am 02.07.2018 um 19:38 schrieb Benny Pedersen:
> Gene Heskett skrev den 2018-07-02 19:20:
>> On Monday 02 July 2018 13:12:12 Gene Heskett wrote:
>> However, a network restart did not get rid of the ipv6 stuff in the
>> ifconfig lo report. ?  /etc/network/interfaces is also clean of any
>> ipv6 stuffs. ?
>>
> 
> if all else fails
> 
> check /etc/gai.conf
> change that conf to prefer ipv4 first

yeah distro specific crap besides that it does not help in case of
freshclam at all to disable ivp6 entirely

[root@srv-rhsoft:~]$ cat /etc/gai.conf
cat: /etc/gai.conf: No such file or directory

[root@srv-rhsoft:~]$ cat sysctl.conf | grep ipv6 | grep disable
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1

[root@srv-rhsoft:~]$ ifconfig lo
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
loop  txqueuelen 1000  (Local Loopback)
RX packets 3019819  bytes 2513735808 (2.3 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 3019819  bytes 2513735808 (2.3 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-03 Thread Reindl Harald



Am 02.07.2018 um 19:20 schrieb Gene Heskett:
>> And since that stuff did exist in my /etc/hosts file, I just stuck a #
>> in front of all those, just for S of course. Watching log too. But
>> its seems like an every other update run, and since I am not a
>> paying/supporting customer, I only run it 2x daily. So the next run
>> will be just about 0:50 local time.
> 
> However, a network restart did not get rid of the ipv6 stuff in the 
> ifconfig lo report. ?  /etc/network/interfaces is also clean of any 
> ipv6 stuffs. ?

sysctl.conf:
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1

sysctl -p

ifconfig no longer shows any ipv6 stuff
it's that easy

but even on my setups which have this for years freshclam repetaly
produces ipv6 crap-messages which is simpyl wrong
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-02 Thread Joel Esler (jesler)


On Jul 2, 2018, at 1:56 PM, Gene Heskett 
mailto:ghesk...@shentel.net>> wrote:

but even on my setups which have this for years freshclam repetaly
produces ipv6 crap-messages which is simpyl wrong

If thats the case, and I'll find out by this time tomorrow, then I can't
help but agree, its a bug. Not a showstopper, but one to be swatted in
the next upgrade for us folks out here in the ipv4 only puckerbrush.


It's definitely on our radar.  Micah may want to comment further.

--
Joel Esler
Sr. Manager
Open Source, Design, Web, and Education
Talos Group
http://www.talosintelligence.com
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-02 Thread Gene Heskett
On Monday 02 July 2018 13:23:24 Reindl Harald wrote:

> Am 02.07.2018 um 19:20 schrieb Gene Heskett:
> >> And since that stuff did exist in my /etc/hosts file, I just stuck
> >> a # in front of all those, just for S of course. Watching log
> >> too. But its seems like an every other update run, and since I am
> >> not a paying/supporting customer, I only run it 2x daily. So the
> >> next run will be just about 0:50 local time.
> >
> > However, a network restart did not get rid of the ipv6 stuff in the
> > ifconfig lo report. ?  /etc/network/interfaces is also clean of
> > any ipv6 stuffs. ?
>
> sysctl.conf:
> net.ipv6.conf.all.disable_ipv6=1
> net.ipv6.conf.default.disable_ipv6=1
>
> sysctl -p
>
> ifconfig no longer shows any ipv6 stuff
> it's that easy

no its not, unless you know how. But lo no longer shows any ipv6 stuffs.

> but even on my setups which have this for years freshclam repetaly
> produces ipv6 crap-messages which is simpyl wrong

If thats the case, and I'll find out by this time tomorrow, then I can't 
help but agree, its a bug. Not a showstopper, but one to be swatted in 
the next upgrade for us folks out here in the ipv4 only puckerbrush.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-02 Thread Benny Pedersen

Gene Heskett skrev den 2018-07-02 19:20:

On Monday 02 July 2018 13:12:12 Gene Heskett wrote:
However, a network restart did not get rid of the ipv6 stuff in the
ifconfig lo report. ?  /etc/network/interfaces is also clean of any
ipv6 stuffs. ?



if all else fails

check /etc/gai.conf

change that conf to prefer ipv4 first
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-02 Thread Gene Heskett
On Monday 02 July 2018 13:12:12 Gene Heskett wrote:

> On Sunday 01 July 2018 07:05:52 Reindl Harald wrote:
> > Am 01.07.2018 um 08:17 schrieb Gary R. Schmidt:
> > > On 01/07/2018 10:22, Gene Heskett wrote:
> > >> I'm still logging this about every other freshclam run:
> > >>
> > >> Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4
> > >> errno=101: Network is unreachable
> > >> Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
> > >> db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
> > >>
> > >> And I've rm'd mirrors.dat several times.
> > >
> > > Do you have an IPv6 network connection to the outside world?
> > >
> > > That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.
> > >
> > > I noticed the same thing was happening with my freshclam, had a
> > > look at the configure options, reconfigured with "--disable-ipv6",
> > > rebuilt and reinstalled
> >
> > build from source is not an option for most users and trying ipv6 on
> > a obvious ipv4-only machine where even the loopback device don#t
> > have a ipv6 address is a bug - it's that easy
>
> And since that stuff did exist in my /etc/hosts file, I just stuck a #
> in front of all those, just for S of course. Watching log too. But
> its seems like an every other update run, and since I am not a
> paying/supporting customer, I only run it 2x daily. So the next run
> will be just about 0:50 local time.

However, a network restart did not get rid of the ipv6 stuff in the 
ifconfig lo report. ?  /etc/network/interfaces is also clean of any 
ipv6 stuffs. ?


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-02 Thread Gene Heskett
On Sunday 01 July 2018 07:05:52 Reindl Harald wrote:

> Am 01.07.2018 um 08:17 schrieb Gary R. Schmidt:
> > On 01/07/2018 10:22, Gene Heskett wrote:
> >> I'm still logging this about every other freshclam run:
> >>
> >> Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4
> >> errno=101: Network is unreachable
> >> Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
> >> db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
> >>
> >> And I've rm'd mirrors.dat several times.
> >
> > Do you have an IPv6 network connection to the outside world?
> >
> > That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.
> >
> > I noticed the same thing was happening with my freshclam, had a look
> > at the configure options, reconfigured with "--disable-ipv6",
> > rebuilt and reinstalled
>
> build from source is not an option for most users and trying ipv6 on a
> obvious ipv4-only machine where even the loopback device don#t have a
> ipv6 address is a bug - it's that easy

And since that stuff did exist in my /etc/hosts file, I just stuck a # in 
front of all those, just for S of course. Watching log too. But its 
seems like an every other update run, and since I am not a 
paying/supporting customer, I only run it 2x daily. So the next run will 
be just about 0:50 local time.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-02 Thread Reindl Harald



Am 01.07.2018 um 14:22 schrieb Gary R. Schmidt:
> On 01/07/2018 21:05, Reindl Harald wrote:
>>
>> Am 01.07.2018 um 08:17 schrieb Gary R. Schmidt:
>>> On 01/07/2018 10:22, Gene Heskett wrote:
 I'm still logging this about every other freshclam run:

 Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4
 errno=101:
 Network is unreachable
 Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
 db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)

 And I've rm'd mirrors.dat several times.

>>> Do you have an IPv6 network connection to the outside world?
>>>
>>> That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.
>>>
>>> I noticed the same thing was happening with my freshclam, had a look at
>>> the configure options, reconfigured with "--disable-ipv6", rebuilt and
>>> reinstalled
>> build from source is not an option for most users and trying ipv6 on a
>> obvious ipv4-only machine where even the loopback device don#t have a
>> ipv6 address is a bug - it's that easy
>>
> Do any machines *not* have IPv6 stacks installed these days?
> 
> They may not have IPv6 connectivity to the outside world, but all my
> Solaris, Linux, and Windows boxes have IPv6 stacks installed by default

do you see any ipv6 address here? the stack is disabled and even in that
cases freshclam comes with ipv6 error messages

[root@srv-rhsoft:~]$ ifconfig lo
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
loop  txqueuelen 1000  (Lokale Schleife)
RX packets 2498838  bytes 2390706748 (2.2 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2498838  bytes 2390706748 (2.2 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@srv-rhsoft:~]$ cat sysctl.conf | grep ipv6
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.all.accept_redirects=0
net.ipv6.conf.all.accept_source_route=0
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.default.accept_redirects=0
net.ipv6.conf.default.accept_source_route=0


___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-02 Thread Reindl Harald



Am 01.07.2018 um 08:17 schrieb Gary R. Schmidt:
> On 01/07/2018 10:22, Gene Heskett wrote:
>> I'm still logging this about every other freshclam run:
>>
>> Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4 errno=101:
>> Network is unreachable
>> Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
>> db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
>>
>> And I've rm'd mirrors.dat several times.
>>
> Do you have an IPv6 network connection to the outside world?
> 
> That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.
> 
> I noticed the same thing was happening with my freshclam, had a look at
> the configure options, reconfigured with "--disable-ipv6", rebuilt and
> reinstalled

build from source is not an option for most users and trying ipv6 on a
obvious ipv4-only machine where even the loopback device don#t have a
ipv6 address is a bug - it's that easy
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gene Heskett
On Sunday 01 July 2018 10:20:59 Gary R. Schmidt wrote:

> On 01/07/2018 23:00, Gene Heskett wrote:
> > On Sunday 01 July 2018 08:22:03 Gary R. Schmidt wrote:
>
> [SNIP]
>
> >> Now, testing for IPv6 connectivity might turn a temporary failure
> >> into a permanent one, which is not good,
> >
> > Needs an explanation. Udev is the only thing that will turn a temp
> > failure permanent, until you edit the rule at least.
>
> I meant testing inside freshclam and turning a temporary IPv6 failure
> into a permanent one.

Ahh, now I get it Gary, permanent until the next update perhaps might be 
a decent idea at that. T'would cut down on the log noise. ;-)
>
>   Cheers,
>   GaryB-)
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Joel Esler (jesler)
Gentlemen, we’ve descended into a “who is better” contest.   I suggest we stop. 
 

Sent from my iPhone

> On Jul 1, 2018, at 10:43, Gary R. Schmidt  wrote:
> 
>> On 02/07/2018 00:35, Reindl Harald wrote:
>> 
>>> Am 01.07.2018 um 16:33 schrieb Gary R. Schmidt:
>>> On 01/07/2018 22:37, Reindl Harald wrote:
>>> [SNIP]
>>> 
 do you see any ipv6 address here? the stack is disabled and even in that
 cases freshclam comes with ipv6 error messages
 
>>> Do you know the difference between running an IPv6 stack and doing a
>>> name lookup for an  record?
>> surely - but where is the point to do so on a ipv4-only setup?
>> 
>> hint: i am for sure the wrong person for such silly questions given what
>> i maintain and develop over the last 15 years
>> 
> Ah, you're new.
> 
> 
> 15 years isn't that long, there's stuff I wrote more than twice that long ago 
> still in use.
> 
> 
> And yes, doing a lookup for an  record is silly in an IPv4-only 
> environment, but if the code is compiled to be IPv6 capable then that is what 
> it probably should do.
> 
> 
> Cheers,
> 
> GaryB-)
> 
> 
> P.S. Irrelevant claims of infinite experience don't impress anyone.
> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/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
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt

On 02/07/2018 00:35, Reindl Harald wrote:


Am 01.07.2018 um 16:33 schrieb Gary R. Schmidt:

On 01/07/2018 22:37, Reindl Harald wrote:
[SNIP]


do you see any ipv6 address here? the stack is disabled and even in that
cases freshclam comes with ipv6 error messages


Do you know the difference between running an IPv6 stack and doing a
name lookup for an  record?

surely - but where is the point to do so on a ipv4-only setup?

hint: i am for sure the wrong person for such silly questions given what
i maintain and develop over the last 15 years


Ah, you're new.


15 years isn't that long, there's stuff I wrote more than twice that 
long ago still in use.



And yes, doing a lookup for an  record is silly in an IPv4-only 
environment, but if the code is compiled to be IPv6 capable then that is 
what it probably should do.



    Cheers,

        Gary    B-)


P.S. Irrelevant claims of infinite experience don't impress anyone.

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt

On 01/07/2018 22:37, Reindl Harald wrote:
[SNIP]

> do you see any ipv6 address here? the stack is disabled and even in that
> cases freshclam comes with ipv6 error messages
>
Do you know the difference between running an IPv6 stack and doing a 
name lookup for an  record?


    Cheers,
        Gary    B-)

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt

On 01/07/2018 23:00, Gene Heskett wrote:

On Sunday 01 July 2018 08:22:03 Gary R. Schmidt wrote:

[SNIP]


Now, testing for IPv6 connectivity might turn a temporary failure into
a permanent one, which is not good,


Needs an explanation. Udev is the only thing that will turn a temp
failure permanent, until you edit the rule at least.

I meant testing inside freshclam and turning a temporary IPv6 failure 
into a permanent one.


Cheers,
GaryB-)
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gene Heskett
On Sunday 01 July 2018 08:22:03 Gary R. Schmidt wrote:

> On 01/07/2018 21:05, Reindl Harald wrote:
> > Am 01.07.2018 um 08:17 schrieb Gary R. Schmidt:
> >> On 01/07/2018 10:22, Gene Heskett wrote:
> >>> I'm still logging this about every other freshclam run:
> >>>
> >>> Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4
> >>> errno=101: Network is unreachable
> >>> Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
> >>> db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
> >>>
> >>> And I've rm'd mirrors.dat several times.
> >>
> >> Do you have an IPv6 network connection to the outside world?
> >>
> >> That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.
> >>
> >> I noticed the same thing was happening with my freshclam, had a
> >> look at the configure options, reconfigured with "--disable-ipv6",
> >> rebuilt and reinstalled
> >
> > build from source is not an option for most users and trying ipv6 on
> > a obvious ipv4-only machine where even the loopback device don#t
> > have a ipv6 address is a bug - it's that easy
>
> Do any machines *not* have IPv6 stacks installed these days?
>
> They may not have IPv6 connectivity to the outside world, but all my
> Solaris, Linux, and Windows boxes have IPv6 stacks installed by
> default.
>
> So testing for an IPv6 loopback would still say "go for it."
>
> Now, testing for IPv6 connectivity might turn a temporary failure into
> a permanent one, which is not good,

Needs an explanation. Udev is the only thing that will turn a temp 
failure permanent, until you edit the rule at least.

> it would probably be better for 
> the IPv6 failure message to say "IPv6 connection failed, trying IPv4."
>
I couldn't agree more. Software error messages in general, suck, rarely 
telling the user what really happened.

I KNOW I have no ipv6 connectivity, and likely won't for the rest of my 
life since I've already used up 83 of my 3 score and 10.

Thats the choice I made when I married an old maid school teacher 29 
years ago this winter. We will both die in the town she was born in. 
County seat, pop about 5500. Small towns are the heart of this country, 
we've got good neighbors. Shopping locally is limited, but stuff I need 
as an aging nerd is less than an hour away, or can be had off the net.

Living someplace where I had to lock up like Fort Knox just to go have a 
cuppa with the next door neighbor is something I'd fix by moving 
someplace where door locks are optional, there, but seldom used. Here 
they often stand open while we go to the store for milk, whatever, and 
coffee.  Whats not to like?

>      Cheers,
>
>          Gary    B-)
>
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am So den  1. Jul 2018 um 13:22 schrieb Gary R. Schmidt:
> Do any machines *not* have IPv6 stacks installed these days?

Yes. If you don't have and/or need IPv6 connectivity, it is probably the
safest measurement to switch it off completely (by kernel option or
compiling the kernel without.)

So I believe, if someone know IPv6 and is security affine, and does not
have IPv6 or does not want to invest the trouble (at the moment) to
implement the safety measurements that is needed to do IPv6 the safe
way, he would switch it off.

Regards
   Klaus
- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAls4z+0ACgkQpnwKsYAZ
9qzyuwv+POnnCNh0/PAHbWgOZVL48JqDYpetJcsdIx8tWO84xFMQ/Pdq9+zeK819
/dyFrnRE2uN7nEDwxAINGEBf8pibFbJT6+z4QhzdInw4wkpviWgMv+c3+n4VIl6P
ro1vXGgksHRurZnBbsjUax7IxSL7qYJcaSHFmdujWWGVIFOlQfyqv7IdvyiptOab
ietWK6yGaKimZXXDPw2/jw8gxkBXxkAsdDl/KtSuSNQbScVa+dcbqCkZVwuFHA6j
vtB1JZc5Y9fAc4SLg34/2O5nHVsV+7bjHoPOO6SrHoKJtzHRcfTr/CxKVYW43JGH
vXS3P7jpV56mx01FEnUpkPe/82zzIn9A5U6DNEJHZK1POz39TOIadErqftiXHQia
58mms+HvauhmRPR7vmNr6RJFJ1vXSD+LJYJTIZOGXaZgSHGV6vIorGKsD1xaTtC3
vJJLevOvmxV+1rs9JEblPOn0zH72lbgv6HalwcGHpHgl9cK69LZKofj7Lkc1gTLM
I6cQPMb6
=s5AF
-END PGP SIGNATURE-
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt

On 01/07/2018 21:05, Reindl Harald wrote:


Am 01.07.2018 um 08:17 schrieb Gary R. Schmidt:

On 01/07/2018 10:22, Gene Heskett wrote:

I'm still logging this about every other freshclam run:

Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4 errno=101:
Network is unreachable
Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)

And I've rm'd mirrors.dat several times.


Do you have an IPv6 network connection to the outside world?

That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.

I noticed the same thing was happening with my freshclam, had a look at
the configure options, reconfigured with "--disable-ipv6", rebuilt and
reinstalled

build from source is not an option for most users and trying ipv6 on a
obvious ipv4-only machine where even the loopback device don#t have a
ipv6 address is a bug - it's that easy


Do any machines *not* have IPv6 stacks installed these days?

They may not have IPv6 connectivity to the outside world, but all my 
Solaris, Linux, and Windows boxes have IPv6 stacks installed by default.


So testing for an IPv6 loopback would still say "go for it."

Now, testing for IPv6 connectivity might turn a temporary failure into a 
permanent one, which is not good, it would probably be better for the 
IPv6 failure message to say "IPv6 connection failed, trying IPv4."



    Cheers,

        Gary    B-)

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gene Heskett
On Sunday 01 July 2018 02:17:41 Gary R. Schmidt wrote:

> On 01/07/2018 10:22, Gene Heskett wrote:
> > I'm still logging this about every other freshclam run:
> >
> > Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4
> > errno=101: Network is unreachable
> > Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
> > db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
> >
> > And I've rm'd mirrors.dat several times.
>
> Do you have an IPv6 network connection to the outside world?
>
No. And its generally disabled sitewide.  The nearest ipv6 is probably in 
Pittsburg PA or Charleston WV, both 100+ miles away. This is WV where 
such as ipv6 will take another 20 years to penetrate the last mile.

> That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.
>
> I noticed the same thing was happening with my freshclam, had a look
> at the configure options, reconfigured with "--disable-ipv6", rebuilt
> and reinstalled.
>
That really ought to have been a freshclam.conf controlled option, but 
not according to the man pages.

> No more noise.
>
IOW, its falling back to ipv4 and continueing on its merry way.

>   Cheers,
>   GaryB-)

Thanks for the clarification, Gary.
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt

On 01/07/2018 10:22, Gene Heskett wrote:

I'm still logging this about every other freshclam run:

Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4 errno=101:
Network is unreachable
Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)

And I've rm'd mirrors.dat several times.


Do you have an IPv6 network connection to the outside world?

That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.

I noticed the same thing was happening with my freshclam, had a look at 
the configure options, reconfigured with "--disable-ipv6", rebuilt and 
reinstalled.


No more noise.

Cheers,
GaryB-)
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-06-30 Thread Gene Heskett
On Saturday 30 June 2018 20:30:57 Joel Esler (jesler) wrote:

> Interesting.   Can you give us a -debug?
>
Is this something I can put in the crontab, Joel?  How?

> Sent from my iPhone
>
> > On Jun 30, 2018, at 20:22, Gene Heskett 
> > wrote:
> >
> > I'm still logging this about every other freshclam run:
> >
> > Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4
> > errno=101: Network is unreachable
> > Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
> > db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
> >
> > And I've rm'd mirrors.dat several times.
> > --
> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> > soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > Genes Web page 
> > ___
> > clamav-users mailing list
> > clamav-users@lists.clamav.net
> > http://lists.clamav.net/cgi-bin/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
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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


Re: [clamav-users] update report

2018-06-30 Thread Joel Esler (jesler)
Interesting.   Can you give us a -debug?

Sent from my iPhone

> On Jun 30, 2018, at 20:22, Gene Heskett  wrote:
> 
> I'm still logging this about every other freshclam run:
> 
> Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4 errno=101: 
> Network is unreachable
> Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host 
> db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
> 
> And I've rm'd mirrors.dat several times.
> -- 
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/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
http://lists.clamav.net/cgi-bin/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] update report

2018-06-30 Thread Gene Heskett
I'm still logging this about every other freshclam run:

Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4 errno=101: 
Network is unreachable
Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host 
db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)

And I've rm'd mirrors.dat several times.
-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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