PDA

View Full Version : Warning: Latest Kasperky 2009 def update does not detect any malware


Technic
May 20th, 2008, 04:09 AM
FYI


Warning: Latest Kasperky 2009 def update does not detect any malware

database:2008-05-20 11:18:00 GMT+8

JasSolo
May 20th, 2008, 04:46 AM
Confirmed. It goes for both KIS and KAV. Be aware! Rollback your defs!


Cheers

JasSolo
May 20th, 2008, 05:53 AM
Well, it's back on track again :)


Cheers

Technic
May 20th, 2008, 06:15 AM
Millions of users were unprotected almost 12 hours. :blink: They (mod) even locked the thread concerning this very very serious vulnerability for further discussion. :thumbd:

Bunkhouse Buck
May 20th, 2008, 06:18 AM
-{ Quote: "Millions of users were unprotected almost 12 hours. :blink: They (mod) even locked the thread concerning this very very serious vulnerability for further discussion. :thumbd:" }-

Perhaps now they will have less Beta users and there are risks to Beta builds. :thumbd:

plantextract
May 20th, 2008, 06:23 AM
this only happened with kav 2009 which is not released yet (it's not released as it's not present on the kaspersky home page). i don't think millions of users use a unreleased software. in case of not released software. or if mllions use that then they are ignorant if they don't know that such things can happen. i mean we are talking about a brand new engine which can still be tested until it's released, so such things might occur.

trjam
May 20th, 2008, 06:28 AM
nobody makes decent software anymore, nobody.

Inspector Clouseau
May 20th, 2008, 06:32 AM
-{ Quote: "this only happened with kav 2009 which is not released yet (it's not released as it's not present on the kaspersky home page). i don't think millions of users use a unreleased software. in case of not released software. or if mllions use that then they are ignorant if they don't know that such things can happen. i mean we are talking about a brand new engine which can still be tested until it's released, so such things might occur." }-

Correct. And as for beta software: USE IT AT YOUR OWN RISK. Everyone says this. If you use something that has not been official released and is intended for beta testing you've to expect always some problems. I'm not saying that it's a guarantee for problems but you MIGHT have some. That's why it's called BETA to find exactly such problems BEFORE a product gets released. So there is most likely no big drama because i can't believe that MILLIONS (!) of users are using a BETA Version to protect their system. And even if they do: It's their own fault then.

Technic
May 20th, 2008, 06:38 AM
Just a side note: I understand some bugs etc in BETA products. This is TR. Never seen major BUG like this lol. And their response time was over 12 hours. This reminds me about PlaceboAV mentioned before. *puppy*


EDIT: how about updates for KIS/KAV 7.0? :shifty:

plantextract
May 20th, 2008, 06:41 AM
the program is TR (kis.en.msi) not the engine, the engine is indepentent of the version (356, 355,354,353... will show the same behaviour), and it can be tweaked until the 1st of june or whatever the release date is, personally if i'm talknig about unreleased software, i would preffer to see false detections and have a better detection when it's released then just sit around and gradually improve what could have already been improved after the release (and detect such problems at that time, after it's released)

Baz_kasp
May 20th, 2008, 06:41 AM
-{ Quote: "Just a side note: I understand some bugs etc in BETA products. This is TR. Never seen major BUG like this lol. And their response time was over 12 hours. This reminds me about PlaceboAV mentioned before. *puppy*" }-

Lets make this clearer...... If it isn't listed here: http://www.kaspersky.com/productupdates


Then it isn't released and there is no support for it. KL can pretty much blow it up before release if they wanted to, because they have not yet given it the "OK" for general consumption.


As far as I know only forum beta testers and those who wanted to have a peak at it before release are using it (and they know it isn't yet released)....for anyone else who downloaded it from warez/torrent sites as "final"....it is their own fault.

Technic
May 20th, 2008, 06:43 AM
-{ Quote: "Lets make this clearer...... If it isn't listed here: http://www.kaspersky.com/productupdates


Then it isn't released and there is no support for it.


As far as I know only forum beta testers and those who wanted to have a peak at it before release are using it (and they know it isn't yet released)....for anyone else who downloaded it from warez/torrent sites as "final"....it is their own fault." }-

This version has nothing to do with forums and beta testers ONLY. KIS/KAV 2009 is widely used, no need for warez sitez. :lurking:

Baz_kasp
May 20th, 2008, 06:54 AM
-{ Quote: "This version has nothing to do with forums and beta testers ONLY. KIS/KAV 2009 is widely used, no need for warez sitez. :lurking:" }-

I beg to disagree. There are no signs on the Kaspersky website saying "Version 2009 released, download it here"


The only place where it was originally announced that 2009 reached technical release was the beta forum. TR doesn't mean it is released.... it means the main development cycle has finished and no more new features will be added for the inital release....quality control/testing still carries on right up until the official release, which will be announced on the website and on the forum. (hopefully via the news agent too)


Any other version of KAV/KIS (e.g. 6.0,7.0) were not affected.....all normal users were still perfectly protected.

plantextract
May 20th, 2008, 06:56 AM
-{ Quote: "EDIT: how about updates for KIS/KAV 7.0?
" }-
what about them?

BlueZannetti
May 20th, 2008, 07:11 AM
-{ Quote: "The only place where it was originally announced that 2009 reached technical release was the beta forum. TR doesn't mean it is released.... it means the main development cycle has finished and no more new features will be added for the inital release....quality control/testing still carries on right up until the official release, which will be announced on the website and on the forum. (hopefully via the news agent too)" }-I have to agree.

Time for a reality check folks - a still unreleased product had some issues. Anyone who uses an unreleased product needs to understand that they are at the mercy of a fluid platform that can do anything up to and including blowing away your entire installation. Naturally, that includes glitches such as the one encountered here. If you can't deal with that eventuality on your own - and that includes understanding when these issues arise, being able to take immediate action yourself without appealing to the masses on a forum, debugging the situation and acting accordingly, and so on - then, frankly speaking, you need to understand that you're in over your head and should reassess how you're using these precommercial products.

Playing here is playing at the bleeding edge - be prepared to suffer cuts on a regular basis.

Blue

Technic
May 20th, 2008, 07:35 AM
I thought this is neutral forum for all vendors. No bashing at all. I am using KIS 2009 and I know what using beta means. :ouch:

DonKid
May 20th, 2008, 07:57 AM
-{ Quote: "what about them?" }-
Like said Baz, users from versions 6 and 7 are perfectly protected.
KL have updates starting with 15 minutes.

Technic
May 20th, 2008, 08:07 AM
-{ Quote: "Like said Baz, users from versions 6 and 7 are perfectly protected.
KL have updates starting with 15 minutes." }-

Great news! All are fixed soon. :argh:

ink
May 20th, 2008, 10:26 AM
I think for this version, this is not the first time, and this kind of issue has nothing to do with version, beta or not

rookieman
May 20th, 2008, 11:02 AM
I think if I done the wise thing i'd remove this and wait for the public release.It appears to be running fine here but I can't take the chance.:(

Edwin024
May 20th, 2008, 11:07 AM
Are you internetting in such a dangerous way?

rookieman
May 20th, 2008, 11:20 AM
Actually I don't dangerous surf at all.This is installed on my son's comp and he has the tendency to be one.

Edwin024
May 20th, 2008, 12:30 PM
It's not wise to but non-released versions on PC's where you know from that the user surfs dangerous... ;)

JerryM
May 20th, 2008, 12:43 PM
I have been using the TR 2009, and letting it update from whatever server it selects. I have not been using the Beta? server.

Did this update problem only impact those who are using the beta server, or did it also affect me also? If so I may just go back to 7.0.0.125, which is still on my desktop.

Thanks,
Jerry

kinwolf
May 20th, 2008, 01:48 PM
From the beta forum FAQ(bold are mine)

-{ Quote: "Welcome to the beta forum!

This section is dedicated towards testing the latest builds of KIS/KAV/WKS/FS Editions. If you need stability please use a release build of [7.0.0.125] or [7.0.1.325 -- MP1 Critical Fix] instead. In that case you will need to post your threads in "Protections For Home Users". Please realize that you are running the betas at your own peril. Crashes are possible and some features might be incomplete. If you are not prepared for those issues, please use a stable build." }-

Beta version should never be run on your main computer unless you accept the risk.

larryb52
May 20th, 2008, 06:31 PM
I'm very interested in this version & I tried the current release but it was only on my machine for 4 hours, I would leave it on as permanent solution. If it were RC that would be diferent but I think we're not quite there yet. I hold high hopes that it'll be soon...

dawgg
May 20th, 2008, 06:34 PM
-{ Quote: "They (mod) even locked the thread concerning this very very serious vulnerability for further discussion." }-
Whats to discuss after its been fixed and back to normal ;)
It'll just be useless posts after that point.

JasSolo
May 20th, 2008, 06:42 PM
-{ Quote: "Whats to discuss after its been fixed and back to normal ;)
It'll just be useless posts after that point." }-

:thumb: :thumb:
Couldn't agree more.


Cheers

TonyW
May 20th, 2008, 07:16 PM
-{ Quote: "If it were RC that would be diferent but I think we're not quite there yet." }-It has already passed the RC stage.

larryb52
May 20th, 2008, 07:27 PM
where can I get the RC?

TonyW
May 20th, 2008, 07:39 PM
I'm sure you've seen the thread on here about the technical release, that is, build 8.0.0.357. That is the version beyond RC stage.

Just an additional point, RC1 was build 8.0.0.324 and RC2 was build 8.0.0.346.

In case you've missed the thread, here it is:

http://www.wilderssecurity.com/showthread.php?t=207778

Edit: added additional info.

Baldrick
May 20th, 2008, 08:00 PM
-{ Quote: "where can I get the RC?" }-
Baz Kasp explained what the TR is here:

http://www.wilderssecurity.com/showpost.php?p=1245215&postcount=13

;D

Macstorm
May 20th, 2008, 08:16 PM
-{ Quote: "this only happened with kav 2009 which is not released yet (it's not released as it's not present on the kaspersky home page). i don't think millions of users use a unreleased software. in case of not released software. or if mllions use that then they are ignorant if they don't know that such things can happen. i mean we are talking about a brand new engine which can still be tested until it's released, so such things might occur." }-
You are correct :thumb:

Still, I can do nothing but give a good laugh at this topic ;D

fce
May 20th, 2008, 10:26 PM
how can i know if i'm already infected by malware?

geez!!! Beta or Official Release, its still "Kaspersky"....this kind of shitty shouldn't happen (12hours unprotected is toooo long)!

dawgg
May 21st, 2008, 03:32 AM
-{ Quote: "how can i know if i'm already infected by malware?

geez!!! Beta or Official Release, its still "Kaspersky"....this kind of shitty shouldn't happen (12hours unprotected is toooo long)!" }-
1) Its been fixed now, do a scan then you'll find out
2) If you're not prepared to get any incidents, use the official release version then. Its unreasonable to expect a unreleased version to be as stable a released... If you're not willing to accept the costs of using an unreleased version, don't use it. Simple.

Post #13 and #15 sum it all up.

Zombini
May 21st, 2008, 11:15 AM
-{ Quote: "1) Its been fixed now, do a scan then you'll find out
2) If you're not prepared to get any incidents, use the official release version then. Its unreasonable to expect a unreleased version to be as stable a released... If you're not willing to accept the costs of using an unreleased version, don't use it. Simple.

Post #13 and #15 sum it all up." }-

Unreleased version or not, this makes you wonder about their backend quality assurance process on the defs.. This new version is about 15 days from release and they have no excuse for screwing this up.

Baz_kasp
May 21st, 2008, 11:37 AM
-{ Quote: "Unreleased version or not, this makes you wonder about their backend quality assurance process on the defs.. This new version is about 15 days from release and they have no excuse for screwing this up." }-



It was fixed already... I do not see what there is to discuss ???

They can screw up whatever they like because it us Un-re-leased... if you are using an unreleased version and such stuff happens then there is only one person to blame. Guess who that is ;D

If you still havent understood, that this problem did not affect any released products then your comment about "backend quality assurance" is completely out of place....because the only defs that caused this error were unreleased defs for an unreleased product ;)

plantextract
May 21st, 2008, 12:04 PM
Does continuing this thread actually serve a porpouse. Everyody, including the resident norton fanboy shared thier thoughts. It is a beta product, it was fixed, kaspersky was bashed. I think everything that should have been said was said and continuing will only result in more bashing.

The Hammer
May 21st, 2008, 03:46 PM
-{ Quote: "Does continuing this thread actually serve a porpouse. Everyody, including the resident norton fanboy shared thier thoughts. It is a beta product, it was fixed, kaspersky was bashed. I think everything that should have been said was said and continuing will only result in more bashing." }-Agreed. No point in continuing, Time to move on.

lodore
May 21st, 2008, 03:50 PM
this thread should be closed to avoid anyone getting confused.

Bubba
May 21st, 2008, 06:11 PM
-{ Quote: "continuing will only result in more bashing." }-That's a good enough reason for terminating this thread, especially since the problem has now been resolved.

thread is now closed.

Bubba