Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Security

Archive Formats Kill Antivirus Products 115

nemiloc sends us to the F-Secure blog for breaking news about widespread vulnerabilities in programs that process archive files: "The Secure Programming Group at Oulu University has created a collection of malformed archive files. These archive files break and crash products from at least 40 vendors — including several antivirus vendors... including us." Here is test material from OUSPG and a joint advisory from Finnish and English security organizations. It isn't news that security products can have have security vulnerabilities. What makes this advisory important is that antivirus software is a perfect target. It is run in critical places with high privileges and auto-updates to keep versions coherent.
This discussion has been archived. No new comments can be posted.

Archive Formats Kill Antivirus Products

Comments Filter:
  • by SpaceLifeForm ( 228190 ) on Tuesday March 18, 2008 @02:10PM (#22785684)
    Is probably more secure.

    I don't need to mention names, you know.
  • by JeanBaptiste ( 537955 ) on Tuesday March 18, 2008 @02:14PM (#22785756)
    Cool. I need to run MS SQL server, it's the only one that my company's workflow software will run on. Also our enterprise app is all written in ASP. We also have lots of Exchange users. It would probably take years and years to convert all these things over to something else, probably with downtime and data loss.

    Your 'solution' may work for some, but probably not for most, and for the rest of us, thats what these articles are posted for!
     
  • by TheRaven64 ( 641858 ) on Tuesday March 18, 2008 @02:21PM (#22785866) Journal
    That's okay, the money has already been allocated, because you factored in the cost of migrating away from the platform as part of the TCO. You did include migration costs in your TCO calculations when purchasing the workflow software and Exchange, right?
  • Re:Proofread? (Score:5, Insightful)

    by gnasher719 ( 869701 ) on Tuesday March 18, 2008 @02:28PM (#22785990)

    While two negatives make a positive, two positives do not make a negative.
    Yeah, right.
  • by Ed Avis ( 5917 ) <ed@membled.com> on Tuesday March 18, 2008 @02:43PM (#22786174) Homepage

    I need to run MS SQL server, it's the only one that my company's workflow software will run on.
    Have you investigated porting to Sybase? It's pretty similar.

    Also our enterprise app is all written in ASP.
    Have you looked at Chili!Soft ASP? Or if you're using ASP.NET, Mono?

    We also have lots of Exchange users.
    Gotta admit, this is harder to migrate from once all your data is locked up in those binary PST files.

    But you have a point that many people, yourself included, are stuck with Windows. It wouldn't be easy to migrate. Much more convenient to buy some crappy virus scanner and keep the plates spinning.
  • Re:Old Problem (Score:3, Insightful)

    by Xtravar ( 725372 ) on Tuesday March 18, 2008 @03:18PM (#22786638) Homepage Journal

    Do you want it fast or do you want it correct?
    Do I want it fast 99.99999999% of the time with a 0.00000001% chance of incident, or do I want it slow 100% of the time with a 0% chance of incident?

    If correcting the repercussions of the incident takes less time than the total time lost by doing things the correct way, then I will take the fast way, please.
  • by jimicus ( 737525 ) on Tuesday March 18, 2008 @03:36PM (#22786906)
    Three (two?) words: Vendor lock-in.

    Unless your employer is prepared to pay for code to be written specifically for every little business requirement that no half-decent Free solution exists for, I defy you to avoid vendor lock-in. Commercial applications with fully documented data schemas are more or less non-existent.

    Email solutions are easy. They've been done to death. So have office applications - wordprocessors, spreadsheets, that kind of stuff.

    Groupware is harder, but not impossible. It becomes much harder, however, if "seamless Outlook or similarly featureful client app integration" is a requirement.

    Accounting solutions aren't easy either - they're boring to write and have to account for every nations' tax legislation in their localisation - and they need to be updated rapidly if that legislation changes. Neither is payroll for much the same reason. Even if the app vendor hasn't tied their app to a specific database (unlikely), they'll have the most horrendous schema with zero documentation.

    As soon as you get into the realm of particularly specialist software for a given market, forget it. The goal of business is to make money for the investors, not a bunch of unknown software developers, so if something off the shelf can be purchased for a quarter of what it'll cost for something to be custom written, guess what will happen. Vendor lockin is a bridge that shall be crossed when it is reached.
  • Re:Old Problem (Score:3, Insightful)

    by DRAGONWEEZEL ( 125809 ) on Tuesday March 18, 2008 @03:37PM (#22786922) Homepage
    You just did "Cost benefit analysis" or sometimes called Risk Analysis.

    That is the same thing that says, do I leave an unsecured wireless AP, or a lightly secured WEP AP that shows I did at least due dilligence?

    For personal Machines, I'd take the fast way, for shure, assuming data is backed up regularly.

    For corporate machines,(in general,Caveat emptor, and risk assesment would need to be performed on a per machine basis.) I wouldn't trust an icecubes chance in hell (hey, what if Satan has a freezer?), it'd be slow and working 100% or not implemented. (again, for the most part)

    The thing is, Great amount of work can be lost (or Stolen) in just a days time. Also, most people don't save (or backup) incrementally throughout the day, they save at the end of the day and if they are really good, sometimes at lunch too.

    Hell, I am a computer nerd, and I only back up quarterly. (in addition to saving most "true work" to the network drives)
  • by orclevegam ( 940336 ) on Tuesday March 18, 2008 @03:44PM (#22787002) Journal

    Did anyone read TFA and realize that of the programs that were known to be vulnerable, the majority were various brands of Linux?
    Actually Linux isn't vulnerable, but some of the common utilities are. Upgrading bzip2 and tar to the latest versions should fix any vulnerabilities. Also hit hard it seems was Symantec with the common library all their utilities use for handling compressed files being compromised, and hence virtually all of their products across the board.
  • by IllForgetMyNickSoonA ( 748496 ) on Tuesday March 18, 2008 @03:53PM (#22787118)
    This is a usual argument, I know. However, each time I read it, I can't help but to ask myself "whose fault is it?" The answer is obvious, isn't it?

    It's unfair to pretend non-MS solutions are somehow expensive because it's so hard to break free from MS once you allowed yourself to get hooked into their proprietary world. You could just as well have developed your enterprise apps in something other than ASP, haven't you?

    OK, I know I'm probably barking up the wrong tree here - probably it's not *your* fault after all. But I guess you know what I'm trying to point out.
  • by Ed Avis ( 5917 ) <ed@membled.com> on Wednesday March 19, 2008 @07:10AM (#22793660) Homepage

    I'm sorry, but *any* system that stores email in a binary database is simply lame.
    This is a bit daft; in the end everything is stored in a binary database when it goes to disk. If you trust an database system for storing financial records at your bank, why shouldn't it store your mail? Do you think that Gmail really uses maildirs with one file per message, and good old find+grep for searching?

BLISS is ignorance.

Working...