Quoting Gary MacKay <g...@edisoninfo.com>:
No one. Only very old installs, not all installs.
So who made who god to decide which servers get shutdown?
No servers were shutdown. And the creators of the software and providers
of the updates (same people) decided, which is their right as the creators
of the software and the providers of the updates. If you don't like it,
then don't use their updates and/or software. Your choice.
Nobody is stopping you from doing whatever you want to YOUR servers.
Since they can not provide the level of service they want to, and I want
to have, if the continue to support very old installs, then:
1) Either they no longer support very old installs, so they and I can
have what we want, or
2) They continue to support your demands to run the old software, in which
case YOU deprive ME of the features I want so you can run obsolete software.
So, yes, in a sense YOU are deciding what I can run on my server, unless
you are cut off. To that end, you were cut off...
The price I would pay is getting an infected server and having to
clean up the mess. None of mine are infected. Although I will say
this incident has probably shut down more servers than ANY VIRUS OUT
THERE YET!!!
Then you have a short memory... :) If you only think back about 5 years,
then you are right... But think back 10-15 years, and it is a different
story...
Symantics. By shutting down clamd daemon the mail server has been
rendered dead. Killed by the very program what was supposed to
prevent this.
No, wrong on both counts.
1) Your configuration caused it to be rendered dead.
2) The software is supposed to detect viruses, nothing more.
I am not disputing that I should have kept the servers up to date.
Again, my problem not anyone else's.
See above -- it is not only your problem. It is a problem for the
vendor, and it is a problem for those who want to see new features which
are not backwards compatible.
Microsoft makes lousy enough software, but what a mess if they
decided to issue a shutdown command on all the Windows NT servers in
the world?
Which isn't the correct analogy...
Microsoft put a new software in place to prevent piracy, which did exactly
that -- it shutdown non-pirated systems. They replaced it with another
version which shutdown fewer non-pirated systems... Then they finally replaced
it with another that only nags you, since they got a lot of complaints from
stopping people from using their new software they just bought on their
licensed hardware.
Microsoft has a kill-bit for activeX controlls, same thing. Amazon removed
books from the Kindle, same thing. Dealers put remote kill switches on
cars, same thing when abused or mistakes happen.
Now all of the above were accidental except the activeX kill-bit. The
clamav situation is different, it was on purpose. But it was announced
6 months in advance (not the case with the activeX kill-bits). You had 6
months notice to upgrade and you knew you were out of date... What's your
excuse?
This was not an accidental failure of hardware or software or
anything else. It was a willful choice to purposefully send out a
kill command. That is what I am angered about.
Why? Not like they didn't ask you to upgrade and keep current...
Not like they didn't announce this 6 months in advance... Not like
they didn't explain it, and ask for feedback... Why are you upset?
--
Eric Rostetter
The Department of Physics
The University of Texas at Austin
Go Longhorns!
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
