Jim Preston wrote:
Over here, if I step out into traffic and get hit it is my fault.
But suppose you walk out across a crossing where the "WALK" is lit
(green man over here) and the traffic has a red light - but someone
screams through ignoring the red light and gets you ?
That is a better
Dan wrote:
Yes, some updates can be problematic. But in this case, surely,
there were updates during the year that worked just fine. In most
cases, tho, I'm thinking the people complaining slacked off
completely - unlike you, they didn't even bother to test the
releases.
And cf todays thr
On Sun, Apr 18, 2010 at 09:50:09AM +0100, Simon Hobson said:
> Dan wrote:
>
> >Yes, some updates can be problematic. But in this case, surely,
> >there were updates during the year that worked just fine. In most
> >cases, tho, I'm thinking the people complaining slacked off
> >completely - unlik
> In response to your example, that was a DOS attack and is illegal.
> Microsoft updates have causes systems including servers to fail and
> crash, should you be petitioning to have Microsoft prosecuted under
> this law?
It happens.
Anyway, the fact is that you keep comparing two different thing.
Hi everyone,
I didn't know about the update, and it has been such a mess.
It's okay, now. Emails in/out going.
The thing is: what about the thousands of emails still in the
/var/spool/qscan/working/new and /var/spool/qscan/tmp directories?
Is there a way to reinject all of them as new emails?
_be
I don't want to stay quiet anymore though :)
I see people posting as systems administrators who are acting more like
consultants in disguise. Fairly consistently they're the ones saying they've
been wronged, being abusive, threatening physical harm, and appear to have no
love or passion for the
Stephen Gran wrote:
You seem to be massively missing the point. In a short while, there
will be signatures in the database that will have the same effect for
older versions of clamd, because they will trigger the same bug. Which
way would you prefer clamd to die - with a helpful error message,
OK. That clearyfied most of it.
I had to uninstall from YaST both clamav and database in order to manage an
update with none-RC. The rpm-update from console would only receive a newer RC
(from 18 to 19) and not the appearently newer none-RC clamav.
And a console rpm-erase would not properly work
On Sun, Apr 18, 2010 at 10:59, _beb_ wrote:
> Hi everyone,
> I didn't know about the update, and it has been such a mess.
> It's okay, now. Emails in/out going.
> The thing is: what about the thousands of emails still in the
> /var/spool/qscan/working/new and /var/spool/qscan/tmp directories?
> I
On Sun, 18 Apr 2010 10:37:19 +0100
Stephen Gran wrote:
> On Sun, Apr 18, 2010 at 09:50:09AM +0100, Simon Hobson said:
> > Dan wrote:
> >
> > >Yes, some updates can be problematic. But in this case, surely,
> > >there were updates during the year that worked just fine. In most
> > >cases, tho,
> Giampaolo, you're one of us. You may have a dissenting opinion, but
> otherwise you're level headed and logical and seem to have some passion
> for your job. So, you're cool in my book.
Thank you, Cody, for your good words: I needed some... :)
Giampaolo
On Sun, 18 Apr 2010, Simon Hobson wrote:
> And you can cut the crap about "well you should have configured your
> system to not stop when ClamAV stopped" - that's rubbish because it's
> already been made perfectly clear right at the start of one of these
> threads that the project team consider
Thanks. That did help. Now I'm getting a problem starting the daemon. The
error that I am getting is:
[r...@neidorff ~]# /etc/init.d/clamd start
Starting Clam AV daemon: ERROR: Missing argument for option at line 33
ERROR: Can't open/parse the config file /usr/local/etc/clamd.conf
Giampaolo Tomassoni wrote:
In response to your example, that was a DOS attack and is illegal.
Microsoft updates have causes systems including servers to fail and
crash, should you be petitioning to have Microsoft prosecuted under
this law?
It happens.
Anyway, the fact is that you keep com
> Giampaolo Tomassoni wrote:
> >> In response to your example, that was a DOS attack and is illegal.
> >> Microsoft updates have causes systems including servers to fail and
> >> crash, should you be petitioning to have Microsoft prosecuted under
> >> this law?
> >>
> >
> > It happens.
> >
> > Anyw
Si St wrote:
OK. That clearyfied most of it.
I had to uninstall from YaST both clamav and database in order to manage an
update with none-RC. The rpm-update from console would only receive a newer RC
(from 18 to 19) and not the appearently newer none-RC clamav.
And a console rpm-erase would no
neidorff wrote:
Thanks. That did help. Now I'm getting a problem starting the daemon. The
error that I am getting is:
[r...@neidorff ~]# /etc/init.d/clamd start
Starting Clam AV daemon: ERROR: Missing argument for option at line 33
ERROR: Can't open/parse the config file /usr/local/etc/clamd.
On Apr 18, 2010, at 7:14 AM, neidorff wrote:
> Thanks. That did help. Now I'm getting a problem starting the daemon. The
> error that I am getting is:
>
> [r...@neidorff ~]# /etc/init.d/clamd start
> Starting Clam AV daemon: ERROR: Missing argument for option at line 33
> ERROR: Can't open/pars
Chuck Swiger wrote:
On Apr 18, 2010, at 7:14 AM, neidorff wrote:
Thanks. That did help. Now I'm getting a problem starting the daemon. The
error that I am getting is:
[r...@neidorff ~]# /etc/init.d/clamd start
Starting Clam AV daemon: ERROR: Missing argument for option at line 33
ERROR: C
I am aware of the force-option in rpm, but I did not want to use it before as a
last resort. I also usually download manually the new clamav packages and
install them from console, and it usually works fine except in the case of this
RC without the force-argument. But that is over now as I stick
Si St wrote:
I am aware of the force-option in rpm, but I did not want to use it before as a
last resort. I also usually download manually the new clamav packages and
install them from console, and it usually works fine except in the case of this
RC without the force-argument. But that is over
___
Mandriva Linux Security Advisory MDVSA-2010:082
http://www.mandriva.com/security/
___
Package : clamav
Date: April 18, 2010
Hello all,
I just compiled and installed a fresh version of clamav (0.96) from
source on an Ubuntu box (8.10).
Compiling and installing went well. I also ran the unit tests and they
all passed. But I then did a full scan of the machine and got lots and
lots of warnings like this:
LibCla
On 4/18/10, Jim Preston wrote:
>
> Chuck Swiger wrote:
>
>> On Apr 18, 2010, at 7:14 AM, neidorff wrote:
>>
>>
>>> Thanks. That did help. Now I'm getting a problem starting the daemon.
>>> The
>>> error that I am getting is:
>>>
>>> [r...@neidorff ~]# /etc/init.d/clamd start
>>> Starting Clam A
On 2010-04-18 22:39, Hauke Duden wrote:
> Hello all,
>
> I just compiled and installed a fresh version of clamav (0.96) from
> source on an Ubuntu box (8.10).
>
> Compiling and installing went well. I also ran the unit tests and they
> all passed. But I then did a full scan of the machine and got
On Apr 18, 2010, at 10:56 AM, lists wrote:
___
Mandriva Linux Security Advisory
MDVSA-2010:082
http://www.mandriva.com/security/
___
On Apr 18, 2010, at 12:46 PM, neidorff wrote:
On 4/18/10, Jim Preston wrote:
Chuck Swiger wrote:
On Apr 18, 2010, at 7:14 AM, neidorff wrote:
Thanks. That did help. Now I'm getting a problem starting the
daemon.
The
error that I am getting is:
[r...@neidorff ~]# /etc/init.d/clamd st
> Shame you haven't talked to to others - like havp for example - before
> doing this.
The announcement to EOL the old releases was made at the start of
october last year. If people using clam as an integral part of their
software don't read announcements, what fault is that of the clam
developers
> 1) If it aint broke, don't fix it. It works, has worked reliably for
> several years, and was working fine yesterday. It's uptime is
And now it's broken. So you have to fix it. Life on the edge is scary
for some sysadmins, eh?
> currently 405 days, and then the last downtime was to physically
On 4/18/10 1:27 PM, Spiro Harvey wrote:
Shame you haven't talked to to others - like havp for example - before
doing this.
The announcement to EOL the old releases was made at the start of
october last year. If people using clam as an integral part of their
software don't read announcements, wh
Sh
They've simmered down, I don't need the issue stirred up again
Spiro Harvey wrote:
Shame you haven't talked to to others - like havp for example - before
doing this.
The announcement to EOL the old releases was made at the start of
october last year. If people using clam as an int
>>
>> # /usr/sbin/clamd
>> LibClamAV Error: cli_cvdload: Corrupted CVD header
>> LibClamAV Error: Can't load /usr/local/share/clamav/daily.cvd:
>> Malformed database
>> ERROR: Malformed database
>> Closing the main socket.
>
> Did you get this resolved? Sending this off-list on purpose as it would
On Apr 18, 2010, at 1:40 PM, Ken Campney wrote:
Sh
They've simmered down, I don't need the issue stirred up again
Spiro Harvey wrote:
Shame you haven't talked to to others - like havp for example -
before
doing this.
The announcement to EOL the old releases was made at the start of
o
On 18 Apr 2010, at 21:47, Török Edwin wrote:
On 2010-04-18 22:39, Hauke Duden wrote:
Compiling and installing went well. I also ran the unit tests and
they
all passed. But I then did a full scan of the machine and got lots
and
lots of warnings like this:
LibClamAV Warning: pread fail: page
yup, that's me, though in all honesty the comment was supposed to read
"They've simmered down, I don't "think the issue needs stirring up again"
Proof reading is a wonderful thing when not practiced in moderation :\
And you run the risk of being called the "most arrogant and ignorant
person
On Apr 18, 2010, at 2:39 PM, Ken Campney wrote:
yup, that's me, though in all honesty the comment was supposed to
read "They've simmered down, I don't "think the issue needs stirring
up again"
Proof reading is a wonderful thing when not practiced in moderation :\
And you run the risk of
On 4/18/2010 5:16 PM, Hauke Duden wrote:
I did what you asked me to do and it seems that the problem is not in
clamav. The files in question are marked as having a size of 4096, but
when I open them I only get a few bytes of data. The strange thing is
that they are all in /sys. Some in /sys/modu
On 18 Apr 2010, at 23:49, Chris Meadors wrote:
On 4/18/2010 5:16 PM, Hauke Duden wrote:
I did what you asked me to do and it seems that the problem is not in
clamav. The files in question are marked as having a size of 4096,
but
when I open them I only get a few bytes of data. The strange t
On 4/18/10 3:11 PM, Hauke Duden wrote:
OK. Sorry for the confusion.
Shouldn't this be in the FAQ (or was I just too blind to find it?)? I'd
hate to think that I am the only one making this mistake.
ClamAV is an antivirus tool. It is reasonable to expect it will be used on file
systems wher
Christopher X. Candreva wrote:
> And you can cut the crap about "well you should have configured your
system to not stop when ClamAV stopped" - that's rubbish because it's
already been made perfectly clear right at the start of one of these
threads that the project team consider any configu
Spiro Harvey wrote:
So for 405 days you've done no kernel patches? Awesome. I bet that
server's a bunch of remote exploits waiting to happen (if they haven't
already).
Using massive uptimes to prove how cool your server is actually just
shows that you're not doing the right maintenance.
Or it
Cody Konior wrote:
I don't know Simon, though I can't help but see his attitude and
comments as a reflection of some other consultants / systems
administrators whom I intensely dislike.
Then I think you have got the wrong impression of what I do and how I do it.
If it's any consolation thoug
On 19 Apr 2010, at 00:22, Dennis Peterson wrote:
On 4/18/10 3:11 PM, Hauke Duden wrote:
OK. Sorry for the confusion.
Shouldn't this be in the FAQ (or was I just too blind to find it?)?
I'd
hate to think that I am the only one making this mistake.
ClamAV is an antivirus tool. It is reas
> So ClamAV as a package won't silently 'not work' for the safety of
> users - and this has been the justification for their approach to
> this issue. But at the very same time they are recommending a setup
> which will silently not scan mail if there's a problem with ClamAV.
I guess it depends
Dear people,
I have seen a couple of threads related to a version upgrade of clamav. I was
running clamav v0.94 and suddenly experienced a harddisk that started filling
up with clamav folders with names like /tmp/clamav-63f56fc3114e9716 . This
caused my mail server (and websites) to stop working
lists wrote:
> Multiple vulnerabilities has been found and corrected in clamav:
Guys,
just a bit of generic (i.e. not specific to the above) background about
such evasion advisories.
How it works aka how to get fame and glory with no effort (nor skills):
1. Pick up eicar.com and pack it up with
I asked this question last week, but haven't got any replies. I'm re-posting it
because a) it will give everyone a break from the 0.94 EOL tweet wars :-) and
b) I'll try to provide more info.
Any help would be much appreciated, as obviously I want to run 0.96!
System is running Mac OS X 10.4.1
Quoting Giampaolo Tomassoni :
In 6 months there were many clamav updates. I would have put the
Signature updates, yes, but not code updates. To make any changes,
you need code updates, not signature updates.
But then, we've about beat this horse to death...
--
Eric Rostetter
The Department
Quoting Stephan von Krawczynski :
And really, the whole idea of eol'ing GPL software is really violating the
moral ground. And that is what makes people upset.
Almost every GPL software does a EOL system. Unless you mean EOL via kill-bit
then this statement doesn't make sense... EOL is a nor
49 matches
Mail list logo
