similar to: EPEL - Clamav update?

On 03/04/16 22:10, Ireneusz Piasecki wrote: > W dniu 03.04.2016 o 04:39, Rob Kampen pisze: >> EPEL maintainers? >> I note messages in the log about updated version 0.99.1 of CLAMAV >> being available since Mar 5th. >> for CentOS 6 no update is available yet. >> I used to use rpmforge for this package but that languished for months >> before updates became

W dniu 03.04.2016 o 04:39, Rob Kampen pisze: > EPEL maintainers? > I note messages in the log about updated version 0.99.1 of CLAMAV > being available since Mar 5th. > for CentOS 6 no update is available yet. > I used to use rpmforge for this package but that languished for months > before updates became available and eventually stopped altogether. > Is there something I can

EPEL maintainers? I note messages in the log about updated version 0.99.1 of CLAMAV being available since Mar 5th. for CentOS 6 no update is available yet. I used to use rpmforge for this package but that languished for months before updates became available and eventually stopped altogether. Is there something I can do to assist in getting this package updated? I have no idea if this is a

Hello, just curious; since March 3rd, 2016 everdays logwatch-mail shows this: Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.99 Recommended version: 0.99.1 on May 4th, 2016 I updated clamav by yum update clamav since then the daily logwatch-mail shows this: Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local

> Date: Saturday, May 14, 2016 16:20:41 -0700 > From: Alice Wonder <alice at domblogger.net> > > On 05/14/2016 01:22 PM, Walter H. wrote: >> Hello, >> >> just curious; >> since March 3rd, 2016 everdays logwatch-mail >> shows this: >> >> Last Status: >> WARNING: Your ClamAV installation is OUTDATED! >> WARNING:

On Sun, May 15, 2016 at 02:55:01AM +0000, Richard wrote: > > > Date: Saturday, May 14, 2016 16:20:41 -0700 > > From: Alice Wonder <alice at domblogger.net> > > > > On 05/14/2016 01:22 PM, Walter H. wrote: > >> Hello, > >> > >> just curious; > >> since March 3rd, 2016 everdays logwatch-mail > >> shows this: >

On 05/14/2016 01:22 PM, Walter H. wrote: > Hello, > > just curious; > since March 3rd, 2016 everdays logwatch-mail > shows this: > > Last Status: > WARNING: Your ClamAV installation is OUTDATED! > WARNING: Local version: 0.99 Recommended version: 0.99.1 > > > on May 4th, 2016 I updated clamav by > yum update clamav > since then the daily

Hello,     I'm sure it's a false positive but figured I post any way. My weekly full scan of my servers reported the following results. /root/samba-4.8.3/bin/default/source3/lib/netapi/examples/group/group_deluser.inst: Unix.Trojan.Vali-6606621-0 FOUND /root/samba-4.8.3/bin/default/source3/lib/netapi/examples/group/group_adduser.inst: Unix.Trojan.Vali-6606621-0 FOUND

On Sat, April 18, 2015 11:16, Jake Shipton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 16/04/15 16:01, James B. Byrne wrote: >> This morning I discovered this in my clamav report from one of our >> imap servers: >> >> /usr/share/nmap/scripts/irc-unrealircd-backdoor.nse: >> Unix.Trojan.MSShellcode-21 FOUND >> >> >> I

On Thu, Apr 16, 2015 at 10:01 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: > This morning I discovered this in my clamav report from one of our > imap servers: > > /usr/share/nmap/scripts/irc-unrealircd-backdoor.nse: > Unix.Trojan.MSShellcode-21 FOUND > > > I have looked at this script and it appears to be part of the nmap > distribution. It actually tests

On 17 May 2016 at 09:11, Rob Kampen <rkampen at kampensonline.com> wrote: > On 17/05/16 19:58, John Hodrien wrote: > >> On Tue, 17 May 2016, Rob Kampen wrote: >> >> No idea where to from here, so if there is anyone that has a working >>> systemd autostart VirtualBox setup on a headless CentOS 7 server - please >>> advise what you have done to get it

On 12/10/2016 12:28 PM, Akemi Yagi wrote: > On Sat, Dec 10, 2016 at 12:21 PM, Rob Kampen <rkampen at kampensonline.com> wrote: >> Hi List, >> >> I use the kmod-nvidia package on my CentOS workstations. >> >> Always this has "just worked". >> >> Doing a yum update this morning I now get this: >> >> >> 09:15:28 : ERROR:

--On Friday, October 09, 2020 6:29 PM +1300 Rob Kampen <rkampen at kampensonline.com> wrote: > If this reject is due to their spam filtering process, it is actually the > email author's problem - how they make up their sentences, key words etc. > and thus the problem will travel with them, to whatever email provider > they choose. > > Suggest they get educated in how

On 2020-10-09 14:16, Kenneth Porter wrote: > --On Friday, October 09, 2020 6:29 PM +1300 Rob Kampen > <rkampen at kampensonline.com> wrote: > >> If this reject is due to their spam filtering process, it is actually the >> email author's problem - how they make up their sentences, key words etc. >> and thus the problem will travel with them, to whatever email

If the decision was made around the 4.8 time period to not fix the problem, why in v6 is it still listed in the manual as being a valid option? On Mon, May 25, 2015 at 11:49 PM, Andrew Holway <andrew.holway at gmail.com> wrote: > To set selinux to permissive or disabled mode during a kickstart > installation, add the sed -i -e 's/\(^SELINUX=\).*$/\1permissive/' >

On 05/26/2015 01:36 AM, Andrew Holway wrote: > Which manual? > > This could actually be the root of the issue. > > https://bugs.centos.org/view.php?id=7910 > > > This is indeed the issue, and it is an upstream (Red Hat) bug .. but I am not sure they are going to fix it, or when: https://bugzilla.redhat.com/show_bug.cgi?id=1161682 If you add these packages to your

> On Dec 7, 2015, at 10:57 PM, Rob Kampen <rkampen at kampensonline.com> wrote: <snip> >> >> [base] >> name=CentOS-$releasever - Base >> #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra > finally something I can check for you > my 6.x machine does not have the trailing &infra=$infra

On Jan 8, 2016, at 10:03 PM, Rob Kampen <rkampen at kampensonline.com> wrote: > welcome to the real world of 2016, there are lots of bespoke systems providing real value and definitely not affordable to replace in the cut throat world of a local ISP. This is a sad truth, but it doesn?t mean that CentOS or EPEL should even *try* to support them. If you?re going to run an unsupported,

But I did not ask for a current version of Centos to support my usecase, did I? On January 9, 2016 1:04:33 PM EST, Jonathan Billings <billings at negate.org> wrote: >On Jan 8, 2016, at 10:03 PM, Rob Kampen <rkampen at kampensonline.com> >wrote: >> welcome to the real world of 2016, there are lots of bespoke systems >providing real value and definitely not affordable to

On Wed, Apr 27, 2016 at 1:10 AM, Rob Kampen <rkampen at kampensonline.com> wrote: > Sounds good, but how many domain MX servers have set up these fingerprint > keys - 1%, maybe 2%, so how do you code for that? I guess I'm thinking it > uses it if available. So even if you do post it on your DNS, how many > clients out there are using DANE on their set up? By the time it