IV International Conference of Unix at Uninet
  • Presentación
  • Registro
  • Programa
  • Comité Organizador
  • Lista de registrados
  • Equipo de traductores
Talk

inglesconf4

MaydayAnswer usually is "I have an antivirus, so no problem"
MaydayAntivirus is becoming a problem rather than a solution
MaydayViruses are something more seious than users think
MaydayMany users can't understand someone can run a program in their machine from outside
Maydayand they're quiet thinking they have a firewall and an antivirus
Maydaybut the problem is the software
Maydaywrongly desined
Maydaysome years ago somebody thiught about mixing data and programs
Maydayand nowadays is still confuse
Maydaynow it's difficult going back
Maydaywe can see how there is an whole in an explrer or an email program
Maydaythe user thinks he is safe with having an antivirus
Maydaybut what happens if the virus comes in before updating the antivirus?
Maydaysince th first appearence up to when antivirus makers realise about it, there is a time space
MaydayDuring this time aniviruses won't detect anything
Maydaywhat happens if propagation strategy sucess?
Maydaye.g. we can see what happened with Sobig.F
MaydayIt beated som records in infected files until it sbecame inactive because of expiring date
Maydaythe problem is the hours we need to clean up everything
Maydaylet's go back to the example of clinical history's stealing
Maydayif we want to design a trojan it's easy  to locate clinical histories finfding the key
Maydaywhat would antivirus do then?
Maydaynothing at all
Maydayviruses are not a game
Maydaythe're becoming something serious
LadyMooNA short time ago a Trojan propagated, examine web pages that client looks, and if he locates a keyword like "bank", etc.. he load a registry of keyboard to send it to a site.
LadyMooNThats an attempt to steal data of bank accounts. In adititon, the trojan installed a proxy at the victim´s computer; then a transfer order made by the authors of the trojan, will appear in bank logs with the IP of the victim
LadyMooNThat´s real, and ins´t a lie.
LadyMooNWe aren´t talking about kids playing to look who is going to infect more computers, or searching zombies to launch DoS attacks to a client in a lan game. We are talking of something extremely serious.
LadyMooNA short time, I have seen like around 1100 computers, all with broad band in different countries (in Togo, also!), send simultaneously thousands and thousands of spam against a email server.
LadyMooNObviously, this 1100 computers have been attacked of some form, and its probably that it was automatic; they were too many to have been attack "hand by hand".
LadyMooNThe really worrisome thing of all facts is that its propably that we will suffer more and more attacks more destructive and better coordinated.
Maydayand if we think that one of the most dangerous arms to infect is mail
Maydayand by April 2004 more than 70% will be spam
Maydaythe problem seems to be quite big
Maydaybut it doesn' seem tha solution being as good as the problem needs
MaydayIn fact there have been important failures in FreeBSD or Linux, for example
MaydayAnd there also have been in Unix "owner" systems like Solaris, aIX, and so.
LadyMooNThe big difference between this systems (open source or not) is that Windows is the design.
LadyMooNAfter all, Linux and BSDs inherit the tradition of an O.S, although was design at first moment without security (Unix) it has demonstrated be think inside his limitations.
LadyMooNAnd Unix admin is better equipped than Windows admin to confront posible problems. We have to remember a thing: paranormal events DOESNT EXISTS in Unix.
MaydayIf I start this program and it doesn't want to?
horacioSome file is missing, or anything else. There is nothing hide.
horacioWhat windows administrators do? Reboot the machine or reinstall everything
horacioIt doesn't matters if it's free or not.
horacioIf they release freely windows code, situation doesn't change at all.
horacioSpoking about free software, some people think it's better because ther are more people involved developing it.
horacioAnd this is not right, I think.
horacioEg. how experienced are those peoples?
horacioPart of Microsoft problem rigth now is one result of software engenieering, mi opinion.
horacioLets say that the worst payed employed, the most inexpert developer
horaciocan make a mistake and turn it on a "buffer overflow".
horacioAnd that is a lot difficult to prevent, or detect.
horacioFree software work, for example, peoples who work on critical areas are best prepared.
horacioTher isn't too much division between "architects" and "workers",
horaciothe same people who design a virtual memory system is who write most part of the code.
horacioand based on his experience, is more probable that he pay attention on critical parts.
horacioBut the number of people working on code is not the answer, indeed quality is.
horacioThat's means, is more important a good design documentation.
horacioSource code has too much detail. And this may turn into an inconvenient.
clskForetunetly, projects like FreeBSD, the linux kernel, etc, are coordinated by a good team of people that also include security in the firs place of their priority list.
clskMyth 2: The unix systems suffer alot because they are used less.
clskThis is something that only someone that doesn't even know what an operating system is would accept. It is possible (i suppose that everyone present here knows) to design an operating system with a good security level. Of course all of them can have some problems, bu there's an important difference between them.
clskAnd lets not forget that the first known buffer overflow was explited in unix systems in november 1988. At that time, until NT came out, the internet was run by unix systems. Even today the windows systems do little serious things. What objective is sexier for the intruder? for example, that a Juniper router (they use FreeBsd) moving gigabits of traffic in a main station?
clskEven if there are less unix systems in number, the majority of mail and the traffic is moved by unix systems. Thus unix is not a so minority objective. Also, knowning that there code is available (and that design information) of many unix versions, and of most of the important tools, it should be eassier to promot an "Armaggedonix". However, this has not happened.
clskWhat's the explanation?
clskFeistel says that Microsoft has many enemies and it is clear that the attacks go in their way. To some point I think this is true, but it is not true that the intruders are attacks the easier systems, and the only difference between Unix and Windows is not the existance of users with restricted permissions. Obviously, this is not important.
clskI remember a discussion in 1989 in a channel dedicated to virus in Fidonet. At this time I dedicated my time to get into OS/2, becayse the people in IBM had made an operating system mono-user but multitask, that was going to allow to write enormous viruses in BASIC, with executables in many hundreds of KB, and the users were not going to know about this. It was going to make the job easier for virus authors.
clskI remember that i defended the existance of a mechanism that would ask (for example) for a password to the user before installing something. And, of course, everyone considered this unconfortable. Todays, the windows user should periodically execute a program that gets rid of unwanted "spyware" that has been installed like by art of magic, without his/her intervention. How is this possible?
clskSomething more than permissions is required, but of course it's an important part. And that's exactly what Mac OS X does.
clskFor example: not so long ago (i have a Mac) i downloaded a free video editor from Avid.
clskWhen i installed it, the software asked me for an administrator password.
clskSomething that surprised me alot, because this was an user program, and Mac OS X has everything that is needed to access to dispositives like fireware, video, etc...
clskWhat did it want it for? To change some system drivers (among them the Fireware one!!) for its own versions. This could've been a disaster with other programs, and i didn't give it the password. I aborted the installation and deleted the program
clskDoes it sound like hell to someone the DLLs in windows? It's not about being confortable, it's about the true security problems. Through the question channel someone is asking me if  i believe that OpenBSD is more secure than linux
clskFor this answer: It's crazy what most of the distributions (of linux) are doing.
clskThere's no clear distinction between what the operating system is and the additional programs. The "make" or the "diff" have the same treatment as Quake, for example.
clskAnd this is a big mistake. Confusion is one of the worst enemy of security.
clskThis is what in 1995 made me get rid of Linux and decide myself for for FreeBSD, for example. And i don't regret this at all.
clskso anyways... my intention is to foment a debate. If os wants to, we can open the moderation of the channel and we can discuss these points this together
clskOverall it is interesting to talk about these myths. Security inherits from free software, and that system like unix or Mac OS X are less targetted because of being the minority
clskThis is, of course, together with the increasing problem of virus security and worms in the preventable worsening
clskMake games, gentlemen
clsk<Arador>  what differences are there between make and make and how does freebsd run these differences
clskMake is part of the operating system, an undividable unity. Quake is an additional packet.
clskhttp://cvsweb.freebsd.org
clsk<Armadillo> Is there a document of the kernel design?
clskOr techniques of engineering of the software have not been used?
clsk<pepita> borja: i came in in the middle of the talk, but why do you think that there i going to be a "predicted worsening"?
clskI  think that there is going to be a worsening because there are people that are making business with the failures of security
clskThanks for attending this talk and i hope you have a good morning/afternoon/night

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net!

Email UsMás información


© 2003 - www.uninet.edu - Contact Organizing Comittee - Valid XHTML - Valid CSS - Design by Raul Pérez Justicia