Slashdot Mirror


Linux 2.4.24 Release Fixes Root Vulnerability

diegocgteleline.es writes "Linux Kernel 2.4.24 has been released and is available on kernel.org. It seems there's a bug in the mremap(2) system call, where a local user can get root privileges.The new version has been released only with the most important bugs fixed - the rest of the changes have been postponed (those changes include the XFS filesystem)."

436 comments

  1. 2.4.x? by devphaeton · · Score: 5, Funny

    I thought that everyone jumped to the 2.6.0 by now?

    Oh wait, it's been 2 weeks already,
    TIME FOR A RECOMPILE!!

    --


    do() || do_not(); // try();
    1. Re:2.4.x? by Neon+Spiral+Injector · · Score: 4, Informative

      The bug has also been confirmed in 2.6.0-rc1. For those that have made the jump, a patch was just posted to the linux-kernel mailing list. I'm guessing -rc2 will follow soon.

    2. Re:2.4.x? by Neon+Spiral+Injector · · Score: 3, Informative

      Crud, that should have been 2.6.1-rc1 of course.

    3. Re:2.4.x? by Dimensio · · Score: 4, Informative

      Since you meant 2.6.1-rc1, I assume that it applies to 2.6.0?

    4. Re:2.4.x? by Molina+the+Bofh · · Score: 1

      I didn't migrate to 2.6 yet because patch-o-matic-ng hasn't been released yet, and this is going to be a patch-o-matic that works both on 2.4 and 2.6.

      --

      -
      Roses are #FF0000, Violets are #0000FF, find / -name '*base*' |xargs chown -R us && mv zig greatjustice
    5. Re:2.4.x? by Anonymous Coward · · Score: 0

      Do you have a the URL for that patch?

    6. Re:2.4.x? by Anonymous Coward · · Score: 0

      --- linux-2.6.0-mm1/mm/mremap.c 2003-12-17 21:58:56.000000000 -0500
      +++ linux-2.6.0-mm2/mm/mremap.c 2004-01-05 13:28:11.000000000 -0500
      @@ -324,6 +324,14 @@

      if (new_len > TASK_SIZE || new_addr > TASK_SIZE - new_len)
      goto out;
      +
      + /*
      + * Allow new_len == 0 only if new_addr == addr
      + * to preserve truncation in place (that was working
      + * safe and some app may depend on it).
      + */
      + if (unlikely(!new_len && new_addr != addr))
      + goto out;

      /* Check if the location we're moving into overlaps the
      * old location at all, and fail if it does.

    7. Re:2.4.x? by Anonymous Coward · · Score: 0

      It looks like it should apply cleanly to 2.6.0.

    8. Re:2.4.x? by mentin · · Score: 1, Troll

      Interesting. Yesterday we flamed MS for dropping support of Windows 98, which is 5 years old, and today we are proposing to drop support of 2 weeks old kernel.

      --
      MSDOS: 20+ years without remote hole in the default install
    9. Re:2.4.x? by Da+Web+Guru · · Score: 2, Insightful

      Maybe, but to upgrade your kernel you don't have to purchase an entire operating system to go along with it...

      --

      --guru

    10. Re:2.4.x? by WNight · · Score: 1

      Now we merely don't sell that kernel anymore and we hope people buy an upgrade to the 2.6.0 line.

      But when we EOL 2.6.x we'll actually have technology in it to disable it if you don't upgrade to 2.8.x within six months. And we'll bill you either way, because the only way to keep your Linux apps working is to buy into our new Licensing 6.0 program. But it's cheaper for you, and better. Really. No, we mean it.

    11. Re:2.4.x? by grahamlee · · Score: 1

      Argh! Goto! My eyes are melting!!!

    12. Re:2.4.x? by AME · · Score: 1

      Actually, in languages that don't support exceptions (like C), goto is about the easiest way to jump to the cleanup code at the end of a function. The alternative is ugly deep nested if's or something like:

      void example() {
      while (1) { /* not really a loop */
      if (error) break;
      do_something();
      if (error) break;
      do_something_else();
      break;
      }
      perform_cleanup_here();
      return;
      }

      which isn't any easier to follow than goto.

      --
      "I have a good idea why it's hard to verify programs. They're usually wrong." --Manuel Blum, FOCS 94
    13. Re:2.4.x? by jgrahn · · Score: 1

      But a do ... while(0); is often easier to follow than gotos. Not always, and there is a use for goto, and the example is artificial since no cleanup is involved...

      void example(void) {
      do {
      if(error) break;
      do_something();
      if(error) break;
      do_sth_else();
      } while(0);
      }

  2. Article title misleading... by kevin_conaway · · Score: 4, Interesting

    Was this bug introduced in 2.4.23 or has it been in the 2.4 series all along ?

    1. Re:Article title misleading... by simoniker · · Score: 4, Informative

      Good point, article title now changed.

      s!

    2. Re:Article title misleading... by gazbo · · Score: 5, Funny
      Sir,

      You are dangerously close to making me believe that a slashdot editor both reads the site and actually takes action based on it. This is distorting my worldview, and most halt.

      plfxthx.

    3. Re:Article title misleading... by mbyte · · Score: 5, Informative

      its been in the kernel since the 2.2 days .. the 2.2 series kernel's are also affected.

      read the synopsis: here
    4. Re:Article title misleading... by gvc · · Score: 1, Redundant

      What's the answer to the question? Is this something that pre-2.4.23 users should be concerned with?

    5. Re:Article title misleading... by whovian · · Score: 1

      There's no patch for 2.2 on kernel.org just yet.

      --
      To-do List: Receive telemarketing call during a tornado warning. Check.
    6. Re:Article title misleading... by Anonymous Coward · · Score: 0

      We must now crown simoniker the One True Editor as he is the only one in recent memory to acknowledge an error and change it without open animosity or apathy.

    7. Re:Article title misleading... by FattMattP · · Score: 1

      Thank goodness I'm still running 2.0.x!

      --
      Prevent email address forgery. Publish SPF records for y
    8. Re:Article title misleading... by Anonymous Coward · · Score: 0

      Wow .. I'm really impressed with your responsiveness, and your concern for the integrity of the story you posted.

      This isn't sarcasm or trolling.

      I just want to say, THANK YOU, for your fantastic attitude towards Slashdot .. making it a useful and pleasant place for all of us.

      By the way, do you get paid full time to work as a Slashdot editor?

    9. Re:Article title misleading... by verbatim_verbose · · Score: 0, Flamebait

      Yeah, so all 7 people still running the 2.2 series better get on the ball!

    10. Re:Article title misleading... by Anonymous Coward · · Score: 1, Informative

      Simoniker is actually a pretty interesting guy, y'know ..

    11. Re:Article title misleading... by Anonymous Coward · · Score: 0

      Oh my god... you really regard Slashdot editors as gods, don't you?

    12. Re:Article title misleading... by jred · · Score: 1

      I know a lot of people still running 2.2 kernels. If it ain't broke...

      --

      jred
      I'm not a mechanic but I play one in my garage...
    13. Re:Article title misleading... by Anonymous Coward · · Score: 5, Funny

      If it ain't broke...

      ...it is now.

    14. Re:Article title misleading... by Anonymous Coward · · Score: 0

      are you married?

    15. Re:Article title misleading... by Squinky86 · · Score: 1

      Yes. I think most of the 2.2 series is also vulnerable.

    16. Re:Article title misleading... by ROC · · Score: 1

      If it ain't broke...

      But it is :-(

    17. Re:Article title misleading... by Anonymous Coward · · Score: 0

      Yes sir! I would gladly be simoniker's cum bucket.

    18. Re:Article title misleading... by jred · · Score: 1

      That depends. Most of the ones I'm aware of operate in closed networks, with the only public internet access being through a workstation w/ dial-up service. Those linux boxes are providing file & print services, and that's it.

      So are they broken? Technically, yes. Practically, no. They still provide the services needed, and the chances of them being rooted are slim.

      --

      jred
      I'm not a mechanic but I play one in my garage...
    19. Re:Article title misleading... by Anonymous Coward · · Score: 0

      this is a real editor, its not like its michael posting this..

    20. Re:Article title misleading... by szo · · Score: 1

      I was thinking the same. If you didn't spell 'must' as 'most', I've surely died from happyness, but as it I can see the world has not changed much around here :)

      Szo

      --
      Red Leader Standing By!
    21. Re:Article title misleading... by Anonymous Coward · · Score: 0

      Still? I thought that 2.0.x was pretty up to date...

    22. Re:Article title misleading... by Lost+Race · · Score: 2, Informative
      I can't see how this applies to 2.2. In the new 2.4.24 patch to mremap, a new size of zero is explicitly allowed if new_addr==addr. In 2.2 there was no new_addr argument to mremap, so effectively new_addr==addr always. Is there a bug in 2.2's munmap that was fixed sometime in 2.3 or 2.4 but the fix never backported? That seems unlikely. I've examined 2.2.20 and 2.2.25 and they both look OK.

      For those of us who can't upgrade to the latest 2.4 kernels here is the mremap patch by itself. This applies cleanly to 2.4.21 and 2.4.22 (and probably most other 2.4 kernels as well).

    23. Re:Article title misleading... by Perky_Goth · · Score: 1

      I was thinking the same. If you didn't spell 'must' as 'most', I've surely died from happyness, but as it I can see the world has not changed much around here

      that wouldn't be as funny if you hadn't misspelled happiness

    24. Re:Article title misleading... by whoever57 · · Score: 1

      According to the LKML, it's probably not in 2.2.x

      --
      The real "Libtards" are the Libertarians!
    25. Re:Article title misleading... by FattMattP · · Score: 1

      I'm actually refering to this 2.0.x.

      --
      Prevent email address forgery. Publish SPF records for y
    26. Re:Article title misleading... by Lost+Race · · Score: 1
  3. Anyone written an exploit yet? by cyt0plas · · Score: 3, Interesting

    Was this one of the usual "inform, wait, release" cases, or is this one of those "oh crap! time for a fix!" cases.

    In other words, should I, Joe Schmoe SysAdmin be afraid of the script kiddies yet?

    --
    Contact Me (got tired of viruses emailing me).
    1. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 0

      RTFA

    2. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 0, Offtopic

      Try this:- exploit

    3. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 3, Informative

      "Proof-of-concept exploit code has been created and successfully tested giving UID 0 shell on vulnerable systems."

      Just because the proof of concept exploit was created DOESN'T MEAN IT WAS RELEASED! If Linus and one other guy are the only ones with the proof of concept exploit, there is no reason to fear the script kiddies yet.

      They did NOT say if the reason for the fix was because someone released an exploit, or if the reason for the exploit is simply to prove the vulnerability works, and was not publically disseminated.

      Go STFU.

    4. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 0

      Completely different thing.

    5. Re:Anyone written an exploit yet? by Xzzy · · Score: 4, Interesting

      > should I, Joe Schmoe SysAdmin be afraid of the script kiddies yet?

      As soon as an exploit is publicised, yes you should.

      Since it's a local exploit it's not as bad as it could be, but I guarantee you if a rootkit didn't already exist, once is being worked on now.

      If you trust all your open services to not execute foreign code you can probably doze a bit, but that's walking on a razor's edge.

    6. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 0

      AC#1 is right!

    7. Re:Anyone written an exploit yet? by irc.goatse.cx+troll · · Score: 2, Insightful

      "Just because the proof of concept exploit was created DOESN'T MEAN IT WAS RELEASED! If Linus and one other guy are the only ones with the proof of concept exploit, there is no reason to fear the script kiddies yet."

      No, but it means the exploit is valid and worth patching. Its not like a lack of code in the wild means the script kiddies don't have it, just that they're good at hiding it. If sysadmins of the world knew how long some ssh exploits were private.. scarey world.

      I'm assuming you're more of a windows admin, where you don't patch until you notice a new admin account named 'zer0c00l' has been created?

      --
      Pain lasts, kid. Its how you know you're alive. Sometimes I think this growing up thing is just pain management-TheMaxx
    8. Re:Anyone written an exploit yet? by cyt0plas · · Score: 1

      Nah, no need to patch. My cronjob already emerged the latest kernel automatically.

      --
      Contact Me (got tired of viruses emailing me).
    9. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 1, Insightful

      Remember, just because the good guys have found this problem now, doesn't mean the bad guys didn't find it first, a while back.

    10. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 0

      It's a local exploit. You need to be afraid now if you have untrusted users logging into your system. You need to be aware that one layer of security has been removed if you offer network services on untrusted networks. This does not make your system remote-rootable if your daemons are secure.

    11. Re:Anyone written an exploit yet? by Anonymous Coward · · Score: 0

      And you're wrong too.

    12. Re:Anyone written an exploit yet? by ComputerSlicer23 · · Score: 2, Insightful
      There needs to be a reboot in there somewhere, otherwise, your just fooling yourself into believeing it's secure, because it's installed.

      I always end up rebooting manually, on glibc, ldd, and kernel security fixes. Generally pam changes too. Those are libraries that get sucked into early binaries and never get restarted. I suppose I could reboot into single user mode for everything but the kernel, but a reboot is a good idea anyways.

      Kirby

  4. Where to get it by algeliten · · Score: 0, Redundant

    Users of their distribution's kernel should install upgrades when their distribution releases an update (should be soonish). Those who prefer stock kernels can grab patches from your local mirror or use my torrent (includes linux-2.4.24.tar.bz, pgp signature and 23->24 changelog).

    1. Re:Where to get it by OrangeSpyderMan · · Score: 1

      LoL - don't get your security fixes from a well-known reliable place, be a rebel and download them from some guy's homedir. Now that's what I call security policy!

      --
      Try NetBSD... safe,straightforward,useful.
    2. Re:Where to get it by 42forty-two42 · · Score: 1

      The PGP signature can be used to verify that the file's genuine.

    3. Re:Where to get it by Anonymous Coward · · Score: 0

      Though the parent has a lot of merit, "some guy" to you may be a good source to someone else. But, just randomly picking a site, yea, not a good idea.

    4. Re:Where to get it by Anonymous Coward · · Score: 1, Insightful
      The PGP signature can be used to verify that the file's genuine.

      I'm sure he'd be happy to put those in his home directory too.

    5. Re:Where to get it by Anonymous Coward · · Score: 0

      no, you get it from the original root source. Which saves/helps the main server on bandwidth.

  5. Not another one by nns6561 · · Score: 1

    I was just getting around to finally installing 2.4.23. All that work gone out the window.

    1. Re:Not another one by ContextSwitch · · Score: 3, Funny

      Yup, another 5 minutes down the drain.

    2. Re:Not another one by Anonymous Coward · · Score: 1, Funny

      Ssssh! I don't think he's smart enough to apply a patch or to know that "make" will only recompile files which need recompiling. Let him have his day as a martyr.

    3. Re:Not another one by Vlad_the_Inhaler · · Score: 4, Funny

      what 'work'?
      how long does it take you to prepare a kernel-upgrade?

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
    4. Re:Not another one by Anonymous Coward · · Score: 0

      On for example production servers new kernels will have to be extensively tested. Also, some patches weren't ready for .23 yet.

    5. Re:Not another one by Anonymous Coward · · Score: 0

      Neither does this guy. He says to run "make clean dep".

    6. Re:Not another one by Vlad_the_Inhaler · · Score: 1

      well, this one is virtually unchanged so that work will still be valid.

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
    7. Re:Not another one by TobiasSodergren · · Score: 1

      ... instead of working, he was installing a new kernel

    8. Re:Not another one by Anonymous Coward · · Score: 0

      This comment shows your ignorance. Inthe real world deploying a new kernel means DOWNTIME..this means scheduling outage time for users.. Now if you have hundreds of boxes like we do, then this is a major pain in the ass. Patching linux boxes is no worse/no better than patching Windows boxes..

    9. Re:Not another one by Benley · · Score: 0, Offtopic

      No kidding. I saw this release and I was like "You've got to be fucking kidding me." I upgraded my colo server to 2.4.23 TWO DAYS AGO when I was in Chicago. It's a good thing I was onsite for it, too, because it wouldn't have rebooted all by itself.

      It is because of this sort of thing that I am 'upgrading' to a Sun machine running Solaris. Not because Solaris never needs kernel patches, but because Suns are more likely to actually COME BACK UP when you reboot them remotely. Some errors you WILL NOT SEE ON A SUN:

      KEYBOARD ERROR
      PRESS F1 TO CONTINUE

      FLOPPY DRIVE A: ERROR
      PRESS F1 TO CONTINUE

      CMOS CHECKSUM INVALID
      RUN BIOS SETUP
      PRESS F1 TO CONTINUE
      etc. I will be a HAPPY CAMPER when I don't have to worry about that sort of crap anymore.

      I debated between buying (used) a Sun Ultra2 (2x300mhz UltraSparc II) and an IBM RS6000 7013-43p/140 (233mhz 604e), because I like AIX as much as I like Solaris. I even considered getting an SGI Origin200 (2x180mhz R10k), but punted on that one because IRIX is a pain in the ass. I ended up buying an Ultra2 last night for $260 because AIX 5.2 can't run on 43p/140's for some arbitrary reason. The Ultra2 will remain supported for a good long while. AND IT WILL HAVE MIRRORED SYSTEM DRIVES. That will be nice.

    10. Re:Not another one by ikekrull · · Score: 1

      No, on Sun machines, when the NVRAM battery or something dies, they dont even give you the 'Press F1 to continue' option.

      They just die, and refuse to boot at all.

      So, no you'll never see an error like that, but then, that box wont come back up until you physically replace the NVRAM chip.

      --
      I gots ta ding a ding dang my dang a long ling long
    11. Re:Not another one by PReDiToR · · Score: 1

      I really hate asking obvious questions, but all the instructions on Kernel Compiling that I have read advocate using make clean/mrproper before doing any work. Does that not clear up all previously compiled objects and require recompilation of the whole shebang?

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    12. Re:Not another one by Anonymous Coward · · Score: 0

      They must have gone in the toilet in recent years, then. I picked up a pair of SparcStation 1+ boxes that were being thrown out for amusement. Both of their batteries are long dead. The impact is minimal - before booting, I have to clue them in about what they are, including the Ethernet address.

      I'm no fan of Sun, but what you're saying implies that they had things right circa 1991 and have broken it since then. I would hope that's not the case.

      As for the actual problem: the PC Weasel is your friend. It provides enough of a keyboard to make the machine boot, and it lets you redirect the keyboard and text mode console over its serial port. As long as you colocate boxes in pairs or bigger groups, you should be able to cross-connect them and cover all the bases.

    13. Re:Not another one by Anonymous Coward · · Score: 0

      Are you running some kind of consumer grade crap? Server motherboards don't do that. Buy some decent hardware. Jesus.

    14. Re:Not another one by Anonymous Coward · · Score: 0

      How about when you're operating a hosting site, and you now have to notify all your customers and reboot your servers again? To compound that, you're not hosting Web servers which won't notice the down time, but other services which need to be rebooted individually by each customer.

      So, in other words, all these local root exploits in the kernel are a real royal pain in the butt. Which is probably a good reason to move to OpenBSD.

    15. Re:Not another one by Viol8 · · Score: 1

      When you're running a production enviroment you can't just assume everything will work because "not much has changed".
      If your business can be brought down because of ANY potential reason you MUST do testing.

  6. Changelog by SuperDuG · · Score: 4, Informative
    List: linux-kernel
    Subject: linux-2.4.24 released
    From: Marcelo Tosatti
    Date: 2004-01-05 13:55:57

    - 2.4.24-rc1 was released as 2.4.24 with no changes.

    Summary of changes from v2.4.23 to v2.4.24-rc1

    <bjorn.helgaas:hp.com>:
    &nbs p; - Fix 2.4 EFI RTC oops

    <marcelo.tosatti:cyclades.com>:
    - Andrea Arcangeli: malicious users of mremap() syscall can gain priviledges

    <marcelo:logos.cnet>:
    - Harald Welte: Fix ipchains MASQUERADE oops
    - Change EXTRAVERSION to 2.4.24-rc1

    <trini:mvista.com>:
    - /dev/rtc can leak parts of kernel memory to unpriviledged users

    Jean Tourrilhes:
    - IrDA kernel log buster

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/
    Sorry it just seemed a bit more informative than the "YES" reply ...
    --
    Ignore the "p2p is theft" trolls, they're just uninformed
    1. Re:Changelog by Anonymous Coward · · Score: 1, Informative

      diff -urN linux-2.4.24-pre3/mm/mremap.c linux-2.4.24-rc1/mm/mremap.c
      --- linux-2.4.24-pre3/mm/mremap.c 2003-08-25 04:44:44.000000000 -0700
      +++ linux-2.4.24-rc1/mm/mremap.c 2004-01-05 04:14:19.000000000 -0800
      @@ -241,6 +241,13 @@

      if (new_len > TASK_SIZE || new_addr > TASK_SIZE - new_len)
      goto out;
      + /*
      + * Allow new_len == 0 only if new_addr == addr
      + * to preserve truncation in place (that was working
      + * safe and some app may depend on it).
      + */
      + if (unlikely(!new_len && new_addr != addr))
      + goto out;

      /* Check if the location we're moving into overlaps the
      * old location at all, and fail if it does.

  7. Mod parent back up please by Frothy+Walrus · · Score: 2, Insightful

    In this case, "-1, Flamebait" can be read as "The truth hurts, don't it?"

    My experience with Linux is the same as the parent poster's: patching, patching, patching if you're up-to-date with the latest 2.x version, or running a kernel from 3 years ago if you prefer stability to tinkering.

    1. Re:Mod parent back up please by Anonymous Coward · · Score: 0

      care to document the assertion that uptime will be a max of two weeks at any given moment due to reoccuring vulns/exploits?

      i didn't think so you little troll garbage.

    2. Re:Mod parent back up please by AKnightCowboy · · Score: 1
      care to document the assertion that uptime will be a max of two weeks at any given moment due to reoccuring vulns/exploits?

      If he would've said a month uptime between reboots then I would agree. The 2.4.23 release came out at the end of November to fix a major kernel root exploit (do_brk) and now 2.4.24 is coming out about a month later to fix another major kernel root exploit. This isn't a very good track record to present to potential customers/users. I'm sick of rebooting my Linux boxes to load new kernels. When are we going to get kernels that can be dynamically reloaded without killing all the active processes?

    3. Re:Mod parent back up please by Frothy+Walrus · · Score: 1

      document it? no, I never documented it.

      but I did run linux 2.2 and 2.4 for a year or two, and in my experience (did you hear that, AC garbage?) I had to patch every few weeks to keep crackers out.

      then I went back to NetBSD (the first Unix I had ever used, on a Mac SE/30) and never looked back. it does not crash, period, unless there is a hardware failure or power outage. Linux crashed infrequently, but NetBSD has crashed once for me in a combined six years of constant use. NetBSD runs what I need it to run (for both desktop and server jobs), and once the machine is set up and running, I don't need to touch it.

      it makes me wonder why anyone wastes so much of their time in the Linux environment.

    4. Re:Mod parent back up please by zulux · · Score: 1, Insightful

      Hear Hear...

      Linux is great fun for personal computers - but I highly recomend that people looks at NetBSD, FreeBSD and OpenBSd for server use.

      They went throught the same problems that Linux is going through right now... but that was about 7 years ago and have moved on.

      There stable, secure and robust - the perfect atributes for a server or even pesonal use if you value productivity over features.

      --

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

    5. Re:Mod parent back up please by ivan256 · · Score: 2, Informative

      It's also not being said enough that updates for local root exploits are practically pointless on single user systems. If you're the only one with access to your system, you don't need to apply this update, and in fact if somebody did manage to get access to such a single user system there are probably far easier ways for the attacker to gain privliges.... Like if you're in the sudoers file for example.

      The recent patches are only really important if you run a multi-user system and don't trust your users.

    6. Re:Mod parent back up please by adrianbaugh · · Score: 1

      True - but remember that if you have demons running you're not single-user anymore. If you can trust all the remotely-accessible software on your system, by all means feel free to ignore the patch (I intend to), but don't assume you're single-user just because no other humans have accounts.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    7. Re:Mod parent back up please by Zapman · · Score: 3, Insightful


      Software is written by humans, and humans make errors, so software has bugs.

      All software.

      The sysadmin motto (abridged) is 'all software sucks, all hardware sucks'

      I just looked through the bugtraq archives, and found 3 local root exploits for OpenBSD in the year 2003. That's the same class of problem as was found in Linux.

      Security is a mindset, and a practice. It's not a platform.

      --
      Zapman
    8. Re:Mod parent back up please by 0x0d0a · · Score: 1

      Mmmmfff....it's not quite that bad.

      Most important servers have one thing running on them (say, your database server or your web server). If that thing gets compromised, you've already lost the game, since the only worthwhile thing on your system was just compromised.

    9. Re:Mod parent back up please by swb · · Score: 1

      I think "running Linux" is an activity, not a state of being.

      Of course BSD users have to buildworld from time to time, but it seems like since I switched from Linux a few years ago, I spend less time on the OS and more time actually solving the problem the box was supposed to solve in the first place.

    10. Re:Mod parent back up please by xchino · · Score: 2, Insightful

      Yes because we all know it's much better to sit around with known vulnerabilties for months at a time, because you are simply UNABLE to do anything about it. No one if forcing you to patch, and as this is a local exploit the need is certainly not as great for the majority of Linux users. Are you trying to imply that the better way to do it is to trust some companies code who has in the past put the very same vulnerabilities back into their OS that had been taken out in a previous update? If you hate patching so much and prefer windows binary updates, try just getting a prepatched binary kernel, install, reboot. Hell you could go so far as to emulate windows update by randomly making calls to windowsupdate.microsoft.com and uploading sensitive information. All in all your point is meritless and shows gross ignorance about system maintenance on your part.

      --
      Everyone is entitled to their own opinion. It's just that yours is stupid.
    11. Re:Mod parent back up please by Lumpy · · Score: 1

      Huh?

      so how is this different from windows or Solaris?

      last I remember was the past 3 years was patching, patching, patching...

      the ONLY server OS I have seen not follow such a path is netware.

      --
      Do not look at laser with remaining good eye.
    12. Re:Mod parent back up please by lintux · · Score: 1

      You got a point here. But when it's a webserver, the intruder usually doesn't get more permissions than the webserver has. Most webservers don't have enough permissions to change the served files.

      So when someone can get in but can't get root, he/she usually still can't deface a site.

    13. Re:Mod parent back up please by Anonymous Coward · · Score: 0

      Maybe that database server is the only important thing to you, but script kiddies could probably care less about your data. They just want to own any box that's connected to the internet 24x7 so that they can packet sco.com or whoever.

    14. Re:Mod parent back up please by weileong · · Score: 1

      the ONLY server OS I have seen not follow such a path is netware.

      Actually this is interesting. Does this mean that Netware is much better security-wise (in which case why aren't more people using it?) or does it mean that nobody's looking for exploits on Netware?

    15. Re:Mod parent back up please by Anonymous Coward · · Score: 0

      netware has less security exploits because it doesn't have useless services running on it.

      Microsoft though of RPC and it is the most useless service running. it is not needed, and is only asking for security holes.

      although netware is much MUCH more secure than microsoft products.. even netware 3.x from 7 years ago is majorly secure compared to the best microsoft server OS. because they had real programmers focus on making the server do it's job.

    16. Re:Mod parent back up please by Anonymous Coward · · Score: 0
      The recent patches are only really important if you run a multi-user system and don't trust your users.

      This is a very dangerous outlook.

      I recently analyzed a compromised Linux box. The attacker got in through a vulnerable php script (register_globals on, allow_url_fopen on, did 'include("$somevar.php")'). The first thing the attacker tried was to get root using a two-month-old kernel sploit. Fortunately, the kernel was patched, so this failed. Eventually, the attacker gave up and moved on.

      As for compromises using sudo - is your apache user in sudoers? How about your ssh privilege separation user? How many remote exploits that do you know of will actually give you the remote user's password?

      If your single-user Linux workstation doesn't run ssh or allow remote X11, then this is indeed a lower priority, but single-user Linux workstations generally allow some kind of incoming access, even laptops.

    17. Re:Mod parent back up please by adrianbaugh · · Score: 1

      Agreed as regards that particular system, but if you get a rootshell you can use the system as a base for further attacks far more effectively than if you only have access to the apache account. nmap, running services from privileged ports etc. are all valid reasons for a blackhat wanting a specifically root account.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
  8. Well... by Film11 · · Score: 2, Interesting

    This doesn't apply to me since I don't have Linux...yet. I plan to get a Knoppix cd, after all, it was on a PCFormat that came a while ago, if only I could find it. Although I know nothing about Linux, so some links to some beginner sites could be useful =\.
    Also, is Linux more secure than Windows, because I hear a fair amount of Linux security holes more than Windows, or maybe I'm just not perceptive enough.

    --
    ):
    1. Re:Well... by Anonymous Coward · · Score: 2, Insightful

      Microsoft has a lot more security issues than any typical linux distro.
      They only reason you don't hear about them so often anymore, is the fact that they recently changed from a weekly patch release cycle, to a monthly patch release cycle.

      That, and Automatic Updates. ;-)

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

      Yesterday when I was fixing my brother's winxp machine, I was downloading an update for his tax accounting software after reinstalling the entire OS. Ten minutes on the internet... BOOM! Blaster worm. Time to go get yet another windows fix I forgot to install.

    3. Re:Well... by RoLi · · Score: 4, Insightful

      Holes like elevation of privileges (like this one) cannot be used by worms since they work only when you already have access to the system. So while these bugs are bad enough, they are still not nearly as bad as the Win-RPC, or the bugs that allowed Nimda, CodeRed etc. to exist.

    4. Re:Well... by CommandNotFound · · Score: 4, Informative

      Also, is Linux more secure than Windows, because I hear a fair amount of Linux security holes more than Windows, or maybe I'm just not perceptive enough.

      All advanced operating systems can be insecure depending on configuration.

      However, regarding your specific question, you see more security exploits for Linux probably because Linux has both remote and local exploits; the vast majority are local exploits. A local exploit is usually only a concern in a multiuser mainframe-style environment where you have "trusted" users who can log in to the machine. These users can log in and use a local exploit to elevate their priviliges on the machine. If the user doesn't have a login account, they do not have the opportunity to perform the exploit. Local exploits generally use buffer overflows or hijack split-second temp files to do their nastiness.

      Windows generally does not operate in a multiuser fashion, so these exploits are not as pertinent. Having written Windows software for years, I can tell that if local exploits ever become a concern for Windows (e.g. if Windows ever goes multiuser in a big way, where a local user may want to exploit the machine), almost every Windows application will have big problems with local exploits, since they have been built assuming that the local system is single-user and temp files and registry entries are assumed to be safe.

    5. Re:Well... by Anonymous Coward · · Score: 0

      Yeah its so hard to install those damned patches. You have to do so much work like going to windows update, hitting the update button, waiting, and restarting the computer.

    6. Re:Well... by Anonymous Coward · · Score: 0
      Holes like elevation of privileges (like this one) cannot be used by worms since they work only when you already have access to the system.

      Holes like this have been used by worms. They use another exploit to get user level access.

    7. Re:Well... by Anonymous Coward · · Score: 0

      Yeah, except in order to download the patches, you have to connect to the internet. If you don't have a firewall or another computer to download the patches, you're screwed.

    8. Re:Well... by Anonymous Coward · · Score: 1, Insightful

      Yes, holes like this weren't responsible for the exploitation of code servers at Gentoo and Debian.

      Oh wait, yes they were.

    9. Re:Well... by Anonymous Coward · · Score: 0

      This doesn't apply to me since I don't have Linux...yet. I plan to get a Knoppix cd, after all, it was on a PCFormat that came a while ago, if only I could find it. Although I know nothing about Linux, so some links to some beginner sites could be useful =\.
      Also, is Linux more secure than Windows, because I hear a fair amount of Linux security holes more than Windows, or maybe I'm just not perceptive enough

      How is this interesting? It says he knows nothing about Linux and asks if it is more secure.

    10. Re:Well... by Anonymous Coward · · Score: 0

      Yesterday when I was fixing my brother's winxp machine, I was downloading an update for his tax accounting software after reinstalling the entire OS. Ten minutes on the internet... BOOM! Blaster worm. Time to go get yet another windows fix I forgot to install.
      Yeah because we all know installing *nix straight from the CD isn't vulnerable so this must not apply there. Moron.

    11. Re:Well... by Anonymous Coward · · Score: 0

      It says he knows nothing about Linux and asks if it is more secure.

      hmmm, very interesting. What do you think? is it?

    12. Re:Well... by unsung · · Score: 1


      Maybe I'm not seeing the point here, but what exactly is the difference between local and remote exploit? I mean all that it takes is for an uninformed user to run a viral application that opens up more holes for a remote user to log in and do damage, right?

    13. Re:Well... by placeclicker · · Score: 1

      Has there even ever been a remote root exploit in the Linux kernel?

      --

      Browse at -1, because trolls are often the most creative part of /.
    14. Re:Well... by paskie · · Score: 1

      Yes, at least early 2.0 kernels were vulnerable to the (in)famous Ping of Death

      --
      It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams
    15. Re:Well... by PReDiToR · · Score: 1

      To make life easy and save you the hassle of partitioning, have a look at VM ware virtual machines. You can run up a fake box while you play in Windows to test out the installation, configuration and use of your Linux system. I have VM's for different distros, and they run under both Linux and Windows if you get both packages.

      You can download the ISO images from FTP for your distro and mount them as CD devices in your VM, saving CDs and making life convenient for yourself. Try running up a VM with Linux in it while your Windows system in the background is downloading another distro.

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    16. Re:Well... by wasabii · · Score: 3, Interesting

      A remote exploit woudl be an exploit on a service such as Apache, or directly in the kernel's TCP stack. Something which would allow a user who does not have access to the machine to get it.

      A local exploit would be an exploit somebody sitting at a shell, or at the keyboard of the system itself, could use to elevate prividiledges he already has.

      Imagine this local exploit: A program, that runs as root, creates a temporary file in /tmp, it then reads that file, and processes the information in it. Imagine if you, a hacker, had access to that computer. /tmp is for temporary files, anybody can create files in it. You create the file in /tmp that this other program expects, and the other program reads from it, and has some sort of error (vulnerbility) where you can cause it to do whatever you want. You, a normal user, just hijacked another user's (possibly root's) program. A local exploit. To exploit this, you must have access to /tmp. You must be able to run programs on the system.

      Windows does not deal with local exploits, ever. Imagine all the programs that create files in C:\WinNT\Temp. All the programs that read from registry entries. I would bet the vast majority of these could be exploited without a thought. There are probably thousands/millions of local exploits in windows. But you never see patches for them. Because nobody cares. Windows isn't designed to be "multiuser". They are trying to shove it into that role, and it won't fit. :0 Or if it fits, it will be disasterous.

      Linux on the other hand, commonly has many users. Think of shell accounts where you can telnet/ssh in, and run your programs. How many windows computers can you ssh into?

      As MS tries harder and harder to penetrate this market, the market that Unix has historically stood in, they're going to have to radically alter their development methodologies. They have no idea what sort of task they are up against. :0 It'll be fun to watch. When you develop Unix programs, just CLI or GUI programs, these kind of condititions are always taken into consideration. I've never seen a Windows programmer even consider them.

    17. Re:Well... by Anonymous Coward · · Score: 0

      Also, is Linux more secure than Windows, because I hear a fair amount of Linux security holes more than Windows, or maybe I'm just not perceptive enough.

      You hear much more about security holes in Linux because there's a whole world of users and developers watching the code permanently, all of them wiling to report anything found to be suspicious ASAP.

      In contrast, MS surely have relatively much less human resources dedicated to that task, and nonetheless I doubt that the company is wiling to disclose all security bugs they find, unless, of course, the flaw goes public (in other words, when it's too late).

      That's pretty simple, IMHO.

    18. Re:Well... by sg_oneill · · Score: 1

      actually the registry does have a degree of security with acl's

      One nifty but overlooked way to lock some stuff down (I do this with parents w2k machine) is to just set permissions on various critical reg entries.

      to easy.

      but your right. the worst problem for win security is userland chaos.

      Hey, just open that temp file (or a preemptive dummy) and lock the inode (or whatever the hell its called in win) and watch that root program try and access it. oooooops. even more fun with dlls.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    19. Re:Well... by CommandNotFound · · Score: 1

      A local exploit is when a local user purposefully tries to crack the system they are currently working on. Most Windows machines are single-user and sitting right next to you, so generally you don't need or want to exploit your own machine. Even in university labs, the local machine is usually fairly stripped down, and the data is on a remote file server. In a multiuser environment that many Unix and Linux machines run, the physical machine you are logged into may be down the hall, in another building, or many miles away. There also may be dozens of other users running applications on the same physical machine, so getting root/admin privileges would give you a great deal of access over other users. Windows machines rarely are run in this configuration, Terminal Services/Citrix notwithstanding.

      In other words, a rough equivalent to a local exploit in Windows would be launching an attack on the Quicken/MS Money Billpay reminder (assuming it runs as Administrator) to get its privilege level, or exploiting one of the local system services. Most Windows users have relatively high privilege levels by default, so generally a local exploit is not necessary to do damage, and again, it is most likely your own machine you would be cracking. The same applies to most Linux desktops, which is why local exploits are not a concern for most desktop Linux users.

    20. Re:Well... by Anonymous Coward · · Score: 0

      but the ping-o-death is not an "exploit" but rather a DoS attack? exploit = priviledge escalation, rooting etc.?

    21. Re:Well... by Foolhardy · · Score: 1
      Windows generally does not operate in a multiuser fashion, so these exploits are not as pertinent. Having written Windows software for years, I can tell that if local exploits ever become a concern for Windows (e.g. if Windows ever goes multiuser in a big way, where a local user may want to exploit the machine), almost every Windows application will have big problems with local exploits, since they have been built assuming that the local system is single-user and temp files and registry entries are assumed to be safe.
      Ever heard of 'terminal services'?

      Care to name any specific local exploits? Every file, registry key and every other system object has an ACL; WinNT certainly IS securable and multi-user. Running every user as an Administrator and expecting security is pointless though; it's almost like running everything as root in unix.
      Local exploits generally use buffer overflows or hijack split-second temp files to do their nastiness.
      I can't think of any system processes that use temporary files. (unless you count page files, but those are opened exclusively.)
      I suppose that a buffer-exploit is a big risk; Microsoft has a bad reputation for those.
    22. Re:Well... by Foolhardy · · Score: 1
      Windows does not deal with local exploits, ever. Imagine all the programs that create files in C:\WinNT\Temp. All the programs that read from registry entries. I would bet the vast majority of these could be exploited without a thought. There are probably thousands/millions of local exploits in windows. But you never see patches for them. Because nobody cares. Windows isn't designed to be "multiuser". They are trying to shove it into that role, and it won't fit. :0 Or if it fits, it will be disasterous.
      I don't see anything in my \Windows\Temp directory. Do you know of any privleged services that actually use temp files? There are some things from VS.NET in the current user's temp directory, but hijacking those won't help much (only that user has acces to them). Windows can be multi user; ever used Terminal Services? Each user (non-admin) is sandboxed. Some of the default settings suck but they are usually easy to change. (For example, normal users, by default, can shut down the system; this is unacceptable for multi-user. It can be easily changed by removing the shutdown privelege from the users group.)
    23. Re:Well... by 4024490502 · · Score: 1

      actually the registry does have a degree of security with acl's
      Out of curiosity, how do you modify these acl's in the registry? I don't see anything in regedit that might do the trick. Do you use some other utility?

      --

      Why is this moist???
    24. Re:Well... by sg_oneill · · Score: 1

      Erm. From memory (I havent tweaked with win2k in over a year and a half btw) its something like regedit32 or something.

      Its in the windows/system32 directory I think

      In there there is a security thingo that allows you to tweak the acl's for reg keys.

      From memory.

      Now go and lock down that pc.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    25. Re:Well... by RoLi · · Score: 1
      Anybody with only half a brain knows that bugs that can be used by humans (evil hackers that have already stolen a user password) are bad, but bugs that can be used by automated programs, too (worms) are a lot worse.

    26. Re:Well... by Anonymous Coward · · Score: 0
      Holes like elevation of privileges (like this one) cannot be used by worms since they work only when you already have access to the system.



      That's like saying: "Holes like elevation of privileges (like this one) cannot be used by humans since they work only when you already have access to the system."



      Just because a root bug is not a remote root bug doesn't mean it can't be used to get root remotely.

  9. Re:HOW DO I KNOW WHAT VERSION I'M RUNNING? by Anonymous Coward · · Score: 0

    uname -a

  10. Nice by Anonymous Coward · · Score: 2, Insightful

    I don't expect I'll be switching to 2.6 until May. The 2.6.1 release is very important to me as it includes a lot of patches previously rejected by Linus. I expect by May we'll have 2.6.3 at least and this kernel will be on its way to rock solid stability. As for now, 2.4 is in maintenance mode and will only be updated for bug fixes. This is great because it will replace the 2.2 kernel in this arena. But in this limbo we are in now, 2.4 is good enough for me.

    1. Re:Nice by iabervon · · Score: 1

      I suspect that we'll have a much faster stabilization for 2.6.x than we did for previous kernels, because the changes that are destined for 2.6.1 (and beyond) have been in -mm for a while, where people have been testing them. In previous series, .0 is pretty stable, but .1 contained a lot of stuff that had been seen by Linus and nobody else, which generally led to a lot of instability. Now Linus knows better and Andrew Morton has been doing a good job of getting stuff that Linus postponed tested.

  11. Quick! by Anonymous Coward · · Score: 5, Funny

    Use Depenguinator on all the unpatched boxen! Let the revolution begin! >:)

    1. Re:Quick! by Xpilot · · Score: 1, Flamebait

      Use Depenguinator on all the unpatched boxen! Let the revolution begin! >:)

      Ugh, a BSD troll. How come these guys are tolerated?

      --
      "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
    2. Re:Quick! by cperciva · · Score: 1

      Now that you mention it, there have been a few more downloads of that package than usual today...

    3. Re:Quick! by Anonymous Coward · · Score: 0

      someone needs to make an untrollinator and install it here

    4. Re:Quick! by Anonymous Coward · · Score: 0

      The use of italics was SUBTLE way of pointing out a stupid joke. Thank you, for I am a fucking retard.

    5. Re:Quick! by Anonymous Coward · · Score: 0

      BSD is dying.

    6. Re:Quick! by Anonymous Coward · · Score: 0

      Because this is yet another remote root exploit that BSD is immune to.

    7. Re:Quick! by Anonymous Coward · · Score: 0

      Oh great! Again! Another Linux exploit, how lovely! I'm sick and tired of weekly kernels and insecurities! OpenBSD, here I come!

    8. Re:Quick! by Anonymous Coward · · Score: 0

      Because this is yet another remote root exploit that BSD is immune to.

      A.) Not a "remote" exploit.

      B.) Windows XP is "immune" to this as well. That still doesn't make it better.

      C.) BSD is dying.

    9. Re:Quick! by roka · · Score: 1

      humor is dying

    10. Re:Quick! by roka · · Score: 1

      But don't you think that you are completely secure by just switching to OpenBSD.

  12. Re:HOW DO I KNOW WHAT VERSION I'M RUNNING? by Zo0ok · · Score: 2, Informative

    #uname -a ...but I guess you are a troll...

  13. patch is very small - about 2K compressed by Anonymous Coward · · Score: 2, Informative
    This is a quick and simple fix.

    patch -p1 < patch-2.4.24
    make clean dep
    make bzImage modules_install

    Depending on your situation, configure your boot loader - grub or lilo - to recognize the new image.

    1. Re:patch is very small - about 2K compressed by pod · · Score: 1

      Oh yeah, compiling a kernel is 'quick', for unuslally large values of 'quick'...

      --
      "Hot lesbian witches! It's fucking genius!"
  14. XFS Filesystem by Dibblah · · Score: 5, Funny

    AAAAAARGH!

    It's XFS. NOT XFS Filesystem. I'm gonna do something illegal to the next person that says ATM machine, too.

    1. Re:XFS Filesystem by Aliencow · · Score: 1

      Built on Windows NT technology !

    2. Re:XFS Filesystem by Kenja · · Score: 4, Funny

      Just dont hurt their RAM memory or HD drive or they'll have to get new ones with money from the ATM machine.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    3. Re:XFS Filesystem by leoboiko · · Score: 2, Insightful

      Maybe this widespread usage is an effort to avoid confusion (e.g. with XFS fonts or ATM networks)?

      --
      Prescriptive grammar:linguistics :: alchemy:chemistry. Stop being a nazi and learn some science.
    4. Re:XFS Filesystem by 74nova · · Score: 1

      just like an automobile's VIN number, eh?

      brought to you by the Department of Redundancy Department

      --
      use your turn signal! you people act like it's divulging information to the enemy
    5. Re:XFS Filesystem by AKnightCowboy · · Score: 5, Funny
      I'm gonna do something illegal to the next person that says ATM machine, too.

      Isn't that the thing where you type in your PIN number?

    6. Re:XFS Filesystem by mats · · Score: 1

      Or CD disc.

    7. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Or DSL line, NIC card, or LCD display.

    8. Re:XFS Filesystem by SirCrashALot · · Score: 3, Insightful

      XFS is also the X font server.....

    9. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Or LAN network?

      (Djeebus this makes my nose hair curl when I hear *pros* that know better say that!!!)

    10. Re:XFS Filesystem by isj · · Score: 3, Funny

      I always thought that XFS was some sort of an integrated IC circuit.

    11. Re:XFS Filesystem by stmpynode · · Score: 1

      Actually HD Drive is correct. HD stands for HardDisk. Now if you said HDD drive then heads would be rolling. I'm not going to even mention the rest of your comment ;)

      --

      Blah.

    12. Re:XFS Filesystem by phUnBalanced · · Score: 1

      that's because it's not "Built on NT Technology"

    13. Re:XFS Filesystem by Stephen+Williams · · Score: 1

      Actually, "HD drive" is fine: it expands to "hard disk drive". Personally, I've used "HDD" as the abbreviation for same for years, since "HD" used to be taken by "high density" (for floppies).

      "PIN number" is my pet hate.

      -Stephen

    14. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Even if you take NT to mean "new technology", Windows NT technology is not in the same category as an LCD display. Windows NT is the name of a product, so technically Windows NT technology is technology used in that product, not technology technology.

    15. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      If your deity is your shepard, then I am the big bad wolf.

      shepard?

    16. Re:XFS Filesystem by Valdrax · · Score: 1

      Technically, the name NT comes from the N-Ten simulator for the Intel i860 RISC processor that the designers of NT were using to test the portability of the project early on. NT was originally to be targetted towards "server" chips and shipped for 4 platforms. Calling NT "new technology" was a later marketting revision, and by the time it shipped NT was stripped of meaning (not an acronym) just like SCO is today.

      --
      If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    17. Re:XFS Filesystem by Feztaa · · Score: 1

      I wanted to get some money out of the automatic ATM teller machine, but I forgot my personal PIN identification number, so I had to do without. :)

    18. Re:XFS Filesystem by tobocop · · Score: 0

      XFS Filesystem
      ATM Machine
      KDE Desktop Environment
      FTP Protocol ...

      --
      Support bacteria, it's the only culture some people have
    19. Re:XFS Filesystem by Anonymous Coward · · Score: 1, Funny

      RSVP Please!

    20. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Kind of like "Windows 2000, built on NT Technology" where NT stands for New Technology.

      Built on New Technology Technology

    21. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Even so, "New Technology" is a name for that technology. It is a proper noun. "New Technology" is a technology.

    22. Re:XFS Filesystem by mark-t · · Score: 3, Funny
      I'm gonna do something illegal to the next person that says ATM machine, too.
      My curiousity got the better of me...

      "ATM Machine".

      Okay... what are you gonna do to me?

    23. Re:XFS Filesystem by man_ls · · Score: 1

      Except that NT was also the brand name of their previous Windows operating system, therefore, this statement was equivilant to saying "Windows 2000, based on the same technology as our previous business OS."

    24. Re:XFS Filesystem by azimir · · Score: 1

      I call dibs if they have an LCD display!

    25. Re:XFS Filesystem by pclminion · · Score: 1
      I'm gonna do something illegal to the next person that says ATM machine, too.

      Then I guess somebody's going to have to call in the SWAT team...

    26. Re:XFS Filesystem by Hard_Code · · Score: 3, Funny

      download your mp3s?

      --

      It's 10 PM. Do you know if you're un-American?
    27. Re:XFS Filesystem by finkployd · · Score: 1

      Yeah, I just had to use one to get money out to buy some tasty TCBY yogurt.

      Oh well, back to work. I'm working on a PKI infrastructure these days :)

      Finkployd

    28. Re:XFS Filesystem by Elwood+P+Dowd · · Score: 1

      SPECIAL WEAPONS AND TRAINING.

      I don't know what you thought SWAT stood for, but none of the words are "team".

      --

      There are no trails. There are no trees out here.
    29. Re:XFS Filesystem by Anonymous Coward · · Score: 2, Informative

      I think it's "special weapons and tactics"

    30. Re:XFS Filesystem by dietz · · Score: 2, Insightful

      XFS is not incorrect. XFS is not an acronym, even if you want it to be. XFS is the name of the file system. You can not expand it out and talk about the "X File System", even if you wanted to, because that's not what it's called.

      It's the filesystem named "XFS". Or, to put it another way, the XFS file system.

    31. Re:XFS Filesystem by thisissilly · · Score: 1
      Isn't that the thing where you type in your PIN number?

      Yes, after you put in your MAC card.

    32. Re:XFS Filesystem by jachim69 · · Score: 1

      And to make it easy to remember, make your ATM Machine PIN Number the same as your car's VIN Number.

    33. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      I see most of my pet peeves have already been listed...

      Cash On Delivery delivery.
      Accelerated Graphics Port port.
      Compact Disc disc.

      Some in my line of work:
      Human Immunodeficiency Virus virus.
      Herpes Zoster Virus virus.
      (Di-)Deoxyribonucleic Acid nucleic acid.
      Magnetic Resonance Imaging imaging.
      Frosty Pist post. Oh, wait...

    34. Re:XFS Filesystem by /dev/trash · · Score: 1

      Or my fave pet peeve . . . PIN number.

    35. Re:XFS Filesystem by AceCaseOR · · Score: 1

      I've also seen the "T" stand for "tactics".

      --
      Zagreus sits inside your head, Zagreus lives among the dead, Zagreus sees you in your bed and eats you in your sleep.
    36. Re:XFS Filesystem by SquadBoy · · Score: 1

      NIC card drives me batty

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    37. Re:XFS Filesystem by Anonymous Coward · · Score: 0
      Built on Windows NT technology !


      No, built on SCO technology!

    38. Re:XFS Filesystem by Elwood+P+Dowd · · Score: 3, Informative

      "Special weapons and training" yields 42 google hits, while "special weapons and tactics" yields 17,000.

      I'd say you've got the accepted definition.

      --

      There are no trails. There are no trees out here.
    39. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      What about...

      An ATM machine built on NT technology?

    40. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Yeah, RAM memory and HD drives are really a crucial part of PC computers.

    41. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Don't forget that the kernel is available under the GPL license. Yup.

    42. Re:XFS Filesystem by DavyByrne · · Score: 3, Funny

      Isn't that the thing where you type in your PIN number?

      PIN number is quite a mouthful. I usually abbreviate it `PINN'.

    43. Re:XFS Filesystem by bain · · Score: 1

      but I have a /dev/hdd, and I buy with Credit Card ;P

      --
      Sanity is a majority vote.
    44. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Dude you're a retard. You have no idea what MAC even means do you? Dumass.

    45. Re:XFS Filesystem by TheScienceKid · · Score: 3, Interesting

      It's sgi's eXtended File System.

    46. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      HD drive

      Hard-Disk drive? Damn, if I need a new one of them, I'll have to go to the ATM machine and put my PIN number in.

    47. Re:XFS Filesystem by theendlessnow · · Score: 1
      Thank goodness it doesn't have anything to do with my Windows 2000 platform (built on NT technology).

      I wonder if XP is built on new NT technology?

    48. Re:XFS Filesystem by HerbieStone · · Score: 1

      Do they run their XFS filesystem on HDD Drives on their ATM machines? With LCD Displays, connecting by TCP- and IP-protocol? Funny stuff from the united states of USA :)

    49. Re:XFS Filesystem by Bombcar · · Score: 1

      You must love the La Brea tar pits.... or

      the The Tar tar pits... (translated)

    50. Re:XFS Filesystem by ktulu1115 · · Score: 1

      Well since none of the other posts under this actually addressed the issue of XFS, I must ask...

      When will XFS "filesystem" be introducted into the 2.4.x series? It'll make things a lot easier getting FC1 working properly with it than 2.6 series

      --
      # fuser -v /dev/attention | grep work
      #
    51. Re:XFS Filesystem by squidfood · · Score: 2, Funny
      PIN number is quite a mouthful. I usually abbreviate it `PINN'.

      That's not very descriptive to me though. To help, why not make it PINN Number?

    52. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      woah dude, your shouting caused you to spit saliva on your LCD Display!

    53. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      STFU, s'il vous plait.

    54. Re:XFS Filesystem by mezron · · Score: 1

      Yea, down by the Rio Grande river... ;)

    55. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      Don't forget Network Interface Card card. That one is more annoying that trying to find out how non-stick teflon sticks to the pan.

    56. Re:XFS Filesystem by pclminion · · Score: 2, Informative
      I don't know what you thought SWAT stood for, but none of the words are "team".

      No, that's the sanitized version of the acronym. SWAT originally meant Special Weapons Attack Team, but the acronym was quickly changed, probably for reasons of political correctness, to "Special Weapons and Tactics."

      Similarly to how they renamed the NMR machine to MRI, because people didn't feel comfortable stepping into a nuclear magnetic resonance device.

      Anyway, "SWAT team" is redundant.

    57. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      From your link:
      MAC Medicaid Authorization Card And it's spelled Dumbass, not Dumass, you dumbass.

    58. Re:XFS Filesystem by Cat_Byte · · Score: 4, Funny

      I smell another slashdot poll.
      Most annoying acronyms:
      a) NIC card
      b) Compact Disk disk
      c) VIN number
      d) ATM machine
      e) Cowboy Neal Neal

      --
      Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
    59. Re:XFS Filesystem by ChrisMaple · · Score: 1

      Or use their MBNA America credit card.

      --
      Contribute to civilization: ari.aynrand.org/donate
    60. Re:XFS Filesystem by iabervon · · Score: 1

      Guess I'll have to buy my RA memory and H drive with money from an AT machine, then, so that I can use my X filesystem. Of course, everybody says that window systems shouldn't be used as filesystems, and that old IBM (IB machine?) in the basement's buried. But with more memory in my research assistant, I'll be able to develop a hydrogen drive and take over the world!

    61. Re:XFS Filesystem by red+floyd · · Score: 1

      Is that by The La Brea Tar Pits?

      (for those who don't know, "La Brea" literally translates as "the tar");

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    62. Re:XFS Filesystem by jimand · · Score: 1

      I know you are right, but if someone asks "Which filesystem do you use?" would you answer "X" or "XFS?

    63. Re:XFS Filesystem by tunah · · Score: 1

      But we distinguish it by calling it "XFS server".

      --
      Free Java games for your phone: Tontie, Sokoban
    64. Re:XFS Filesystem by gad_zuki! · · Score: 1

      >I'm gonna do something illegal to the next person that says ATM machine,

      That's what you think you heard when they're actually saying:

      ATMachine

      PINumber

      I believe you are suffering from Acronym Pause Syndrome. See page 938 of the DSM-IV for more info and treatment.

    65. Re:XFS Filesystem by passion · · Score: 1

      but only if they can remember their PIN number!

      --
      - passion
    66. Re:XFS Filesystem by int18 · · Score: 1

      That HD drive is attached to a SCSI interface, right? And you transfer files to it over the network using the FTP protocol...

    67. Re:XFS Filesystem by deander2 · · Score: 1

      there is NOTHING wrong with saying "XFS File System". Don't you know what XFS stands for?

      X FS
      F ile
      S ystem

      All you're doing is spelling out the recursive TLA*! :-P

      * = Three Letter Acronym, AIYDKA ;)

    68. Re:XFS Filesystem by DickBreath · · Score: 1

      Isn't that the thing where you type in your PIN number?

      At least, they don't make you type in your SSN Number.

      --

      I'll see your senator, and I'll raise you two judges.
    69. Re:XFS Filesystem by Tokerat · · Score: 1

      I'm gonna do something illegal to the next person that says ATM machine, too.
      And it doesn't bother you at all that GNU's Not Unix? ;-)
      --
      CAn'T CompreHend SARcaSm?
    70. Re:XFS Filesystem by Tokerat · · Score: 1

      the The Tar tar pits... (translated)
      I dip me fish sticks in 'em. Arrrrrrr.
      --
      CAn'T CompreHend SARcaSm?
    71. Re:XFS Filesystem by Eristone · · Score: 3, Funny

      Actually HD Drive is correct. HD stands for HardDisk. Now if you said HDD drive then heads would be rolling. I'm not going to even mention the rest of your comment ;)


      Shouldn't that be heads would be crashing? (duck. run.) :)

    72. Re:XFS Filesystem by milkman_matt · · Score: 1
      You must love the La Brea tar pits.... or

      the The Tar tar pits... (translated)

      Hah, that just reminded me of Mickey Blue Eyes (yeah, I saw it, what of it?) they were saying he could find someone at "the la trattoria".

      Bah hell, It's funny when you see it, I guess :)

      -matt

    73. Re:XFS Filesystem by achurch · · Score: 1

      Nope, but it tastes real good with au jus gravy.

    74. Re:XFS Filesystem by Cro+Magnon · · Score: 1

      Hmm, maybe I shouldn't mention that I bank at UMB Bank.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    75. Re:XFS Filesystem by salimma · · Score: 1

      HD drive is actually correct - you should have made it HDD drive :P

      --
      Michel
      Fedora Project Contribut
    76. Re:XFS Filesystem by glitch23 · · Score: 1

      ATM machine

      --
      this nation, under God, shall have a new birth of freedom. -- Lincoln, Gettysburg Address
    77. Re:XFS Filesystem by jamesl · · Score: 1

      And if they change the software program inside the ATM machine ...

    78. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      SWAT = Special Weapons And Tactics. [snort] You dumbass.

    79. Re:XFS Filesystem by Anonymous Coward · · Score: 0

      No, it's a Personal PIN Number.

    80. Re:XFS Filesystem by teknico · · Score: 1
      I'm gonna do something illegal to the next person that says ATM machine, too.
      Isn't that the thing where you type in your PIN number?

      I hereby declare that everyone's PI number is 31415.

      Alas, it is unfortunate that most AT machines do not support an infinite number of digits.

      Even now that they are all ATX.

  15. This is why I love free (as in beer) software... by bc90021 · · Score: 2, Funny

    ...not only is there a fix already, but I didn't have to badger anyone to get it - it was announced! Off to emerge my new kernel... ;)

  16. Can't Wait! by gillbates · · Score: 3, Insightful

    For the Microsoft trolls to pick this one up.

    Is this just more proof that Linux was built by amateurs? Or wait - I know - that Linux can't be trusted because the source code is open.

    Now, for those who think I'm serious, think about it for a moment. Slashdot hypes up every single MS vulnerability as "proof" that MS systems are inherently insecure. And I wouldn't disagree that MS systems are insecure. But discovering a single (or a few) vulnerability doesn't make an OS insecure.

    What it comes down to is vigilance and design. The numerous security holes in MS products are a result of bad design, not merely a mistake or two. And this is the big difference between this vulnerability - a mere isolated mistake - and Microsoft's complete lack of engineering which ensures that their software _will_ have security holes.

    Okay, flame away Microsofties!

    --
    The society for a thought-free internet welcomes you.
    1. Re:Can't Wait! by TWX · · Score: 3, Insightful

      Not only that, but Open Source/Linux tends to state specifically what the problem is, where to see it, and what the exact fix as code is, versus just relying on some international megacorporation to release a binary-only patch that one has to trust doesn't contain any more report-ware or additional bugs.

      Even with Linux's problems, I'll take it any day over MS OSes. At least Linux developers are honest about their mistakes.

      --
      Do not look into laser with remaining eye.
    2. Re:Can't Wait! by Anonymous Coward · · Score: 0

      For years, I was basically a microsoft apologist, saying the "linux has holes too" line. Then I read about how MS "designed" (ha!) the message-passing in windows. It really is INTRINSICALLY INSECURE. You (or MS) just CANNOT fix it totally without breaking compatibility - something MS aren't fond of doing.

    3. Re:Can't Wait! by Meat+Blaster · · Score: 2, Interesting
      I'm not backing Microsoft, because how much is it worth being comparatively secure to another product (they've got three remote-roots and we've only got two!).

      I'm still convinced that a closed-source competently-designed operating system will be, on the whole, less vulnerable than an open-source competently-designed operating system. The theoretical million eyes on the source isn't worth as much as it (used to be) hyped, because you're not talking about a million security professionals and you're really talking about maybe a thousand eyes on different parts of the code.

      I'm still more comfortable with Linux than Windows, and not just because of security concerns, but I'd be much more convinced of the security benefit if there were more eyes looking proactively for things like this.

    4. Re:Can't Wait! by Anonymous Coward · · Score: 0, Troll

      yawn.....

      convinced of what you say?

      why don't you show us the info that has so-called convinced you.

      on the other hand mr. 578650....don't bother.

      oh and it's not that i'm bothered by pro/anti microsoft either way...(i'm typing this from xp)...it's just that your post almost insists that i give a shit.

      and i don't.

    5. Re:Can't Wait! by pballsim · · Score: 3, Insightful

      Personally I believe this shows that people are making the software and people make mistakes. Some mistakes are more stupid than others.

      I remember an exploit in the apache code that when they received an image that was bigger then there buffered they doubled the size of the buffer (ONCE!). (This was in November, not sure if they fixed it).

      I think this should just make the Linux and Microsoft and whatever communities be more humble and stop some of these flame wars.

      Linux/Unix/Microsoft all have their advantages and disadvantages. Both have great programming and weak programming. They all strive for the same goal, to make it easier for users to use computers. Linux/Unix was originally designed for programmers, Microsoft was originally designed for business people. They both are working on going to the other side.

    6. Re:Can't Wait! by swissmonkey · · Score: 1

      The numerous security holes in MS products are a result of bad design, not merely a mistake or two

      Dare to explain why they are bad design and not coding mistakes in Windows case ?

    7. Re:Can't Wait! by Anonymous Coward · · Score: 0

      Well, if Linux had the same market share as Windows then... oh wait...

    8. Re:Can't Wait! by Necrobruiser · · Score: 1

      It's interesting that Microsoft's vulnerabilities are referred to as "security flaws", or "security holes", or "security lapses" while Linux gets to have "bugs".
      I'm not trying to troll or draw any conclusions, but the use of language does affect how we think about a thing.

      --
      "I planned within my means and got a fixed rate mortgage, so where's MY bailout?" -cafepress
    9. Re:Can't Wait! by plcurechax · · Score: 1

      I'm still convinced that a closed-source competently-designed operating system will be, on the whole, less vulnerable than an open-source competently-designed operating system. The theoretical million eyes on the source isn't worth as much as it (used to be) hyped, because you're not talking about a million security professionals and you're really talking about maybe a thousand eyes on different parts of the code.

      Read the paper Security in Open versus Closed Systems -- The Dance of Boltzmann, Coase and Moore (pdf) by Computer Security expert (since the 1980s) and Cambridge University professor Ross Anderson.

      Your conclusion of more secure because it is close-sourced and "competently-designed" OS does not hold. The million eyes argument is a red herring.

    10. Re:Can't Wait! by NanoGator · · Score: 3, Insightful

      "Is this just more proof that Linux was built by amateurs? Or wait - I know - that Linux can't be trusted because the source code is open... Now, for those who think I'm serious, think about it for a moment. Slashdot hypes up every single MS vulnerability as "proof" that MS systems are inherently insecure. And I wouldn't disagree that MS systems are insecure. But discovering a single (or a few) vulnerability doesn't make an OS insecure."

      So doesn't it stand to reason then that the 'Microsoft Trolls' are simply giving you a taste of your own medicine? If Slashdot weren't out to sensationalize Microsoft at every turn, you wouldn't have to deal with 'Microsofties' forcing you to eat a bit of humble pie when these things come along.

      In short: People in glass houses...

      --
      "Derp de derp."
    11. Re:Can't Wait! by Anonymous Coward · · Score: 0
      on the other hand mr. 578650....don't bother.

      Oh, because it's anti-M$ this FLAMEBAIT gets modded "interesting". What exactly is "interesting" about this FLAMEBAIT? He's what's interesting about this FLAMEBAIT, he's SUCKING on TIMOTHY's cock right now. That's about it!

    12. Re:Can't Wait! by NanoGator · · Score: 1

      "I think this should just make the Linux and Microsoft and whatever communities be more humble and stop some of these flame wars."

      It's a little hard to resist the urge to say "See! Linux has problems too!" when every story involving Microsoft on Slashdot is spun out of proportion.

      --
      "Derp de derp."
    13. Re:Can't Wait! by Anonymous Coward · · Score: 0

      Slashdot hypes up every single MS vulnerability as "proof" that MS systems are inherently insecure.

      You obviously don't have to maintain any Microsoft systems. Only about one in twenty MS holes make it to Slashdot.

    14. Re:Can't Wait! by vadim_t · · Score: 1

      Heh, that'd be great, really.

      And very funny as well, since Windows has a local root exploit *by design*. It's called "shatter", and it's been on slashdot a while ago.

    15. Re:Can't Wait! by ktulu1115 · · Score: 1

      "In short: People in glass houses..."

      ...sink ships?

      --
      # fuser -v /dev/attention | grep work
      #
    16. Re:Can't Wait! by red+floyd · · Score: 1

      versus just relying on some international megacorporation to release a binary-only patch that one has to trust doesn't contain any more report-ware or additional bugs.

      You forgot stealth EULA changes in that list (W2KSP3 anyone?)

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    17. Re:Can't Wait! by Anonymous Coward · · Score: 0

      How do you know the security problems in Microsoft programs are the fault of bad design when you can't look at the source code? You are making wild assumptions about the state of their codebase based on jack squat.

    18. Re:Can't Wait! by AndreyF · · Score: 0

      the fact that every account set up on a WinXP system is Admin without a password by default

    19. Re:Can't Wait! by AndreyF · · Score: 0

      the assumtion was not made by looking at the MS code, but by looking at how MS products behave. when I set up accounts on a computer I make for friends/relatives, by default, accounts are set to administrator privelages and have no password. that's a design flaw.

    20. Re:Can't Wait! by Anonymous Coward · · Score: 0

      People in glass houses... ... shouldn't get stoned. :o)

    21. Re:Can't Wait! by gillbates · · Score: 1

      Yeah, I think the real problem is that slashdot concentrates on specific security problems rather than design problems. Quite frankly, I only read the headlines when I hear of Yet Another Microsoft Security Hole. It's not news - it's the expected result of poor design. And quite frankly, if a lot of slashdotters _weren't_ running Windows, it wouldn't be an issue.

      --
      The society for a thought-free internet welcomes you.
  17. (no subject) by lcde · · Score: 4, Funny

    unsubscribe linux-kernel

    --
    :%s/teh/the/g
  18. Atm... by Anonymous Coward · · Score: 0
    ATM Machine, ATM Machine, wherefore art thou?

    *thwack*

    Ah, there goes my head on the ground...Whoops!

  19. Not NIC Card either!... /nt by Anonymous Coward · · Score: 0

    haha

  20. Argh, just finished 2.4.23 went back from 2.6 by Anonymous Coward · · Score: 2, Interesting

    2.6 seemed pretty good to me, except one thing: I play games like enemy territory and map times just kept getting longer and longer as I played. Only shutting down et and restarting solved it. On 2.4 the maps load at about 20-30 secs, in 2.6 it would start at that and keep getting longer, last map was over 2 minutes until I was disconnected from server.

    I tried 2.6.1rc1 and with the -mm patch. Same thing. So now I'm back with 2.4.3. But in last few versions of the 2.4 series I get extreme slowdowns when using my psx pad on my lpt port. This worked fine in 2.6 and in much older kernels in the 2.4 series.

    I was just looking at the gamecon.c file for 2.6 and comparing to 2.4 and noticed a PSX_DELAY value was different. I modified it to 2.6 value but same thing.

    Anyone knowledgeable on this stuff tell me is it safe to use the gamecon.c from 2.6 for 2.4? Or why I would get these load times issues with 2.6?

    1. Re:Argh, just finished 2.4.23 went back from 2.6 by YellowSubRoutine · · Score: 2, Insightful

      Sounds like you're running your X window system with a nice value. Handy trick for better responsiveness in 2.4, but lethal in 2.6.

      Nice values *really* make a difference in 2.6

    2. Re:Argh, just finished 2.4.23 went back from 2.6 by ChristTrekker · · Score: 1
      Nice values *really* make a difference in 2.6

      Care to elaborate? Many of us don't keep up on the inner workings of the kernel.

    3. Re:Argh, just finished 2.4.23 went back from 2.6 by Anonymous Coward · · Score: 2, Interesting

      run top and make sure it doesn't say -10 or anything other than 0 for X's nice value, if it does say -10 or something you'll need to find what script or config file is setting it and change it to 0 for 2.6

    4. Re:Argh, just finished 2.4.23 went back from 2.6 by adrianbaugh · · Score: 2, Insightful

      Slashdot is probably not the best forum to get a timely response from the maintainers of the relevant parts of the kernel or X. Perhaps you should file a bug report in a more appropriate place?

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    5. Re:Argh, just finished 2.4.23 went back from 2.6 by 0x0d0a · · Score: 1

      I noticed this back in the 2.5 days. This won't explain what happens behind the scenes, but each nice point in 2.5/2.6 makes a *much* larger difference than in 2.4. Before, a nice difference of 5 was barely perceptable. You needed a difference of 10 to significantly "nice" down a pricess, and around 20 if you *really* wanted to keep a process from affecting another. This was really annoying, because there was essentially no point in adjusting niceness at a granularity of less than 5, and if you wanted to have regular user-level processes with interactive performance, entirely noninteractive daemons, and idle processes, there simply wasn't a large enough nice range to pull this off (you'd have to go to nice level 40 or so).

      I'm sure that it's more sophisticated than just this, but I've found that a nice difference of 5 in 2.6 means that the nicer process can almost get starved -- exactly desired behavior. You can simply nice 20 your idle daemons and still have a big range to let users set up their own lower priority processes.

    6. Re:Argh, just finished 2.4.23 went back from 2.6 by Per+Wigren · · Score: 3, Insightful

      $ man nice

      On kernel 2.4 and earlier, you usually gave the X-server a negative nice-value to give it higher priority which lead to somewhat better responsivness. But the 2.6-kernel has a new rewritten scheduler (?) that detects if the process is interactive or not and handle them differently to make interactive apps more responsive while giving non-interactive apps more throughput. By renicing the X-server you foul the kernel to not make use of this and thus get a much less responsive X desktop.
      If you just compiled and installed the 2.6 kernel on a 2.4 distro that is not 2.6-ready you'll have to mock with the X startup-scripts to remove the nice/renice-stuff to make use of the great 2.6 desktop-features.

      --
      My other account has a 3-digit UID.
    7. Re:Argh, just finished 2.4.23 went back from 2.6 by kju · · Score: 1

      > (you'd have to go to nice level 40 or so)

      Are you bubbling? Valid nice ranges are -20 to +19.

    8. Re:Argh, just finished 2.4.23 went back from 2.6 by Anonymous Coward · · Score: 0

      The PSX handling code in gamecon.c isn't the best (at least around 2.4.17, not sure if it has changed). If you use your controller in analog mode, the kernel will be "paused" (interrupts off, reading the controller) for about a millisecond. I submitted the following patch around 2.4.17, the maintainer said it was accepted, but I never saw it in recent kernels.

      http://confusatron.org/gamecon.c.patch

      The problem with the previous code was that it would read 1 bit every 120 microseconds. In analog mode there are about 80 bits to transfer, so (80 * 120us = 9600us). The PSX controller is clocked at 250kHz, so the gamecon.c code was waiting WAY too long (120us vs 4us).

      The patch also fixes some buttons, controller initialization problems, and adds a gc_psxdelay module parameter (I use 3 -- defaults to 8).

    9. Re:Argh, just finished 2.4.23 went back from 2.6 by SomeGuyFromCA · · Score: 1

      You overtrimmed:

      >> there simply wasn't a large enough nice range to pull this off (you'd have to go to nice level 40 or so).

      >Are you bubbling? Valid nice ranges are -20 to +19.

      Grandparent's point exactly - you can't go to 40.

      --
      if the answer isn't violence, neither is your silence / freedom of expression doesn't make it alright
    10. Re:Argh, just finished 2.4.23 went back from 2.6 by 0x0d0a · · Score: 1

      Are you bubbling? Valid nice ranges are -20 to +19.

      Sure -- read the whole sentence in my post:

      there simply wasn't a large enough nice range to pull this off (you'd have to go to nice level 40 or so).

      I'm complaining that you didn't *have* a large enough range, given the tiny difference between each nice level.

    11. Re:Argh, just finished 2.4.23 went back from 2.6 by Anonymous Coward · · Score: 0

      You fucking retard! Go back to M$, we don't need you using Linux with stupid newbie comments like this!

    12. Re:Argh, just finished 2.4.23 went back from 2.6 by kju · · Score: 1

      You're right, i'm sorry.

    13. Re:Argh, just finished 2.4.23 went back from 2.6 by Anonymous Coward · · Score: 0

      > On kernel 2.4 and earlier, you usually gave the X-server a negative nice-value

      This was always a debatable thing to do. Sure, your X Server drawing is more responsive, but your X Applications became LESS responsive. Which is probably not what you wanted.

      Linux should just copy the WinNT approach and have the Window Manager talk to the Scheduler in order to give the foreground app a nice boost. Most of Windows' percieved responsiveness comes from this trick.

  21. *raises eyebrow* by Faust7 · · Score: 2, Insightful
    Joe Schmoe SysAdmin

    Isn't that an oxymoron?

    ...

    Well, it should be.

  22. Re:HOW DO I KNOW WHAT VERSION I'M RUNNING? by Anonymous Coward · · Score: 0

    $ cat /proc/version

  23. Re:This is why I love free (as in beer) software.. by irc.goatse.cx+troll · · Score: 1, Troll

    You confuse Linux community with Open Source community. OpenBSD is also opensource, but that doesn't mean he announced the local vulns out there that would allow any user to bring down your server. You had to complain on the obsd mailinglist and have someone send you a patch, which is really pretty sad.

    --
    Pain lasts, kid. Its how you know you're alive. Sometimes I think this growing up thing is just pain management-TheMaxx
  24. Re:Linux has uptimes of 2 weeks by Anonymous Coward · · Score: 0

    Actually, that's your W2KAS is probably still up because it's running some spammer's trojan, and spammers have no interest in making their trojans crash boxes - in fact, spammer viruses and trojans try to be as minimal and unobtrusive as possible, doing as little as possible to jeopardise system stability.

  25. Redhat 7.3 updates? by GeekWithGuns · · Score: 1

    Ok, I know that I have read here that a few groups are making new updates for RedHat 7.3, but now I can't remember which story or groups. Anybody remember which story that was. As I recall one group was going to charge $5/machine and another was going to do it for free. I don't think that Fedora Legacy ever got around to supporting the old RedHat stuff, or did they?

    --
    [End of diatribe. We now return you to your regularly scheduled programming...] - Larry Wall in Configure from the perl
    1. Re:Redhat 7.3 updates? by Spoke · · Score: 2, Interesting

      Fedora Legacy isn't quite up and running yet, but RedHat released errata RPMs for RedHat 7.x, 8.0 and 9. If you read the archives of the Fedora Legacy list, you will get a good idea of the state of the project.

  26. Re:In Linux... by pseudochaotic · · Score: 1

    Practice makes perfect.

    --
    And the l33t shall inherit the 34r7h.
  27. Re:Linux has uptimes of 2 weeks by Anonymous Coward · · Score: 0

    Oh yeah, and script-kiddies have no intentions of turning your unsecured RedHat box into an FTP dumpsite for warez, either? And you wouldn't notice a few extra 'ftpd' processes hogging CPU and bandwidth because they've trojaned your ps, top and other binaries so it's as unobtrusive as possible?

    In addition, you can forget about it being some spammer's box. The Windows server is sitting behing a Cisco PIX firewall and the only services running on the machine are IIS FTP, file sharing and Active Directory. You also don't seem to be familiar with the group policy editor, something which no Linux tool can even touch when it comes to system security.

  28. NIC by grioghar · · Score: 1

    It's a Network Interface Card, or an Ethernet card, but it's not a freaking NIC Card...

    --
    Can you ping me now? Gooood! | Manhappenin.Net - Things to do
  29. Actually it's .. by Jeedo · · Score: 1

    $ uname -r

  30. Re:In Linux... by Anonymous Coward · · Score: 0

    it doesn't take that long for me, fixing windows actually takes longer comparatively

  31. Debian, Gentoo, and who else? by jrexilius · · Score: 1

    Was this how the various compromises this couple of months have occured?

    I know the one where the normal user password was stolen and then they mysteriously got root. Was this it?

    1. Re:Debian, Gentoo, and who else? by Anonymous Coward · · Score: 0

      The user to root escalation part of Debian's problem was because of the brk vulnerability fixed in 2.4.23, not this one. About the other compromises, who knows? Still, someone has to get local access (legitimately or through another exploit) before these two bugs can be possibly exploited, so it's not too big a deal for most otherwise up-to-date machines (of course, get your kernel fixed before something else you use does have an exploit; most software does eventually).

    2. Re:Debian, Gentoo, and who else? by a_n_d_e_r_s · · Score: 1

      no that problem was fixed in the next to last version of 2.4...

      --
      Just saying it like it are.
  32. Re:Linux has uptimes of 2 weeks by Anonymous Coward · · Score: 1, Insightful

    I wouldnt brag about running IIS FTP and file services on your AD box if I was you. That is if your FTP is accessible from the outside, you weren't clear :\

  33. RedHat fixed orphaned versions by Kalak · · Score: 5, Informative

    Possibly due to the fact that the last kernel fix was a week ago, or just that the patch is minoor, or because RH is being kind to those of us who still have reasons to run RH 7.3 just yet, but look to RH for a kernel update if you need one for 7.x and 8 which are unsupported in 2004. Thanks RedHat. Saved me a panicked kernel decision. I desperately didn't want to return from a vacation to a timetable jump of a few weeks.

    --
    I am, and always will be, an idiot. Karma: Coma (mostly effected by .hack)
  34. Re:In Linux... by Nasarius · · Score: 3, Insightful

    Uh, right. "make bzImage" actually takes a couple minutes on any decently fast computer. You don't need to rebuild all the modules, and even that will take much less than an hour unless you're running ancient hardware.

    --
    LOAD "SIG",8,1
  35. Progeny is the company you are thinking of... by chipster · · Score: 1
  36. Re:In Linux... by Anonymous Coward · · Score: 0

    this comment should break down the grandparent

  37. Got a problem? by Anonymous Coward · · Score: 0
    What are you going to do about it then? Do you think it's a problem that exploits are addressed quickly when they come up?

    If you don't like it, go to Microsoft. They have a long history of delaying patches and even not patching things!

  38. Even the multi-user functions of today... by Kjella · · Score: 4, Insightful

    Having written Windows software for years, I can tell that if local exploits ever become a concern for Windows (e.g. if Windows ever goes multiuser in a big way, where a local user may want to exploit the machine), almost every Windows application will have big problems with local exploits

    ...are pretty much only for convienience, that is to keep user settings and such separate among a group of mutually trusted users (like say, a family). There's not much in terms of real security.

    That users created at install time default to admins with no passwords only goes to prove that even more. Which is fine, as long as a) noone unauthorized can get to the machine and b) all the users trust eachother.

    On the other hand, local exploits are a grave concern in many settings, say for example a university where each student has a local account. So they should by no means be taken lightly, even if they don't produce worms.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  39. a syscall again by gph · · Score: 1

    Does someone want to rewrite every syscall of the linux kernel, cause it's seems very buggy this days :)

  40. and etc. by ChristTrekker · · Score: 1

    That's another good one for the department of redundancy department. (Hint: what does "et" mean?)

  41. Bad Design by valdis · · Score: 1

    *ANY* exploit that involves the 'My Computer Zone' or similar is due to bad design. When the fundamental security design is screwed, you're stuck with either throwing it out entirely, or patching, patching, patching, patching as new ways around it are found.

    1. Re:Bad Design by swissmonkey · · Score: 1

      What does the "My computer zone" feature has to do with the OS itself ?

      NOTHING, this is an IE related feature.

    2. Re:Bad Design by bucky0 · · Score: 1

      IE is a part of the OS. At least that's what Bill Gates has said during his testimony.

      Another example would be ActiveX. ActiveX was created because MS developers didnt like how Java was in a sandbox and made them jump through hoops to do certain things.

      --

      -Bucky
    3. Re:Bad Design by swissmonkey · · Score: 1

      IE is not part of the OS and has no say in the overall OS design. HTML rendering libraries are used throughout the OS(explorer, help,...), and these are part of IE, that doesn't make IE a part of the OS, IE uses these rendering libraries like any other app.

      Same for ActiveX, this is an IE thing, the OS has nothing to do with ActiveX.

    4. Re:Bad Design by _Sprocket_ · · Score: 1

      ...and these are part of IE, that doesn't make IE a part of the OS, IE uses these rendering libraries like any other app.

      Same for ActiveX, this is an IE thing, the OS has nothing to do with ActiveX.


      Cool. Now how do I remove these components from my current Win2K or future WinXP install?
    5. Re:Bad Design by Heidistein · · Score: 0

      C:\> format c:

    6. Re:Bad Design by bucky0 · · Score: 1

      First, like I said, I was quoting Bill G. (granted, he had an interest in saying that IE was irremovable)

      Secondly, the HTML rendering libraries are the crux of a horrible security hole waiting to happen. The HTML control is used everywhere, the way that it determines whether or not content should be trusted is broken ('the zones'). Secondly, there arent enough sanity checks and the control has access to the meat of the OS, which is why an email can bring the whole system down.

      --

      -Bucky
  42. RHN has new kernels for RH 7.1 to RH 8.0 by Erik_ · · Score: 3, Informative

    RedHat Network has patches for RH 7.3. From the RHN Errata page : "We have provided kernel updates for Red Hat Linux 7.1-8.0 with this advisory as these were prepared by us prior to December 31 2003. Please note that Red Hat Linux 7.1, 7.2, 7.3, and 8.0 have reached their end of life for errata support and no further errata will be issued for those distributions."

  43. But that's not the real problem. by Ungrounded+Lightning · · Score: 3, Interesting

    In Linux... (Score:-1, Troll) you have to spend 4 hours recompiling your kernel for stuff like this.

    In Windows, you just install a small binary patch that takes less than a minute.


    A few months later when/if they get around to releasing the small binary patch. B-)

    But there IS a real problem - at least as of the last version of RedHat I installed. (And I'm presuming the same is true with other "commercial-grade" distros, so somebody PLEASE let me know if there's one where this is NOT true.)

    In Linux the commercial distributions make it easy to do an initial install - once. But the included documentation doesn't tell a newbie how to compile and install a new kernel. Or how to download a kernel patch (unless, MAYBE, if he figures out it might be needed and digs deep and hard for it).

    With Red Hat:

    - The install tools are all directed at getting him from bare (or windows-loaded) machine to login prompt.

    - The phone support included with the distro (before the recent policy changes at least) stops when you get installed to where you have a login prompt.

    - The admin tools are essentially all directed at tuning that initial install. (Exception is rpm - with some of the most convoluted manual pages I've seen in a long time. But even that leaves him in the same position as a Windows user - waiting for an RPM patch.)

    Source included but NO documentation on how to build from source. The nicey-nice admin tools make it worse, by hiding what's going on from the user so he has NO clue what's going on behind the pretty GUIs.

    I'll believe Linux is ready for prime-time when the distro documentation includes:

    - A keystroke-by-keystroke walkthrough of applying a patch.

    - A keystroke-by-keystroke walkthrough of building and installing a distribution-equivalent kernel from source (so the user has a trusted baseline from which to make ONLY the changes he intended).

    - Explanations of the configuration-file twiddling done by the admin tools - broken down by GUI page.

    Anything less leaves him in a position much like a windows user - dependent on the vendor or a consultant. Unable to make his own changes (beyond config-tool knob-twiddling) without a long learning process (much like becoming a MSCE) because any change he makes might shatter his configuration beyond his own ability to recover (short of a reinstall from scratch).

    Yes, with Linux you can learn this stuff without having to go buy a monopoly's school supplies. But at least Microsoft understands that a user has other things to do than become a guru. Linux distro providers and hackers, on the other hand, seem to have forgotten the learning curve they climbed.

    Linux is still in the model-T / hot-rodder stage. Versus, say, Microsoft, which has advanced to black-box engine control / recall and dealer-fix stage. (Except that the recalls are too few and too often not-free. Unlike the "big three" plus foreign compeition, a dissatisfied customer can't dump the latest in a series of lemons and switch to a competitor's functionally-equivalent peach.)

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:But that's not the real problem. by hellraizr · · Score: 1

      A keystroke-by-keystroke walkthrough of applying a patch.

      So I guess the Linux Kernel-HOWTO just mysteriously disapeared all of a sudden. get over it people, linux has GLOBS of docs, more than any one human should ever have to read, FAR more than windows or any other OS for that matter considering all the user contrib'd sutff out there now.

      Get them here:
      and for some more reading on this subject go here

    2. Re:But that's not the real problem. by Ungrounded+Lightning · · Score: 1

      So I guess the Linux Kernel-HOWTO just mysteriously disapeared all of a sudden.

      No, that's not it.

      The Linux Kernel-HOWTO Isn't in the documentation provided with the distribution.

      Nor is a pointer to it.

      (Prove me wrong: Give me a page number in a manual included with a Red Hat distribution with either a copy of this or a link to it.)

      When a newbie buys a package from a distribution packager, it should INCLUDE documentation on how to do things as BASIC as build a patched kernel.

      As for "go find it on the web" - there's a LOT of stuff on the web. Digging it out is a RESEARCH PROJECT.

      A customer who PURCHASED a system from a repackager (who tweaked it) shouldn't have to DO that project - and then tune it for the repackager's tweaks - then iterate for every OTHER purchaser of that distro. The repackager should include a copy - with any tuning for that distro and release level already done and DEBUGGED BY HIS QA DEPARTMENT before the distro was released.

      This is BASIC to a ready-for-prime-time product.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    3. Re:But that's not the real problem. by Dalcius · · Score: 1

      It's my understanding that up2date will update your kernel for you? If you're impatient and want to patch before Red Hat has done QA on the patch, I can understand the desire for documentation, but I can't understand why one would think it's critical.

      Please correct me if I misread something in your post.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    4. Re:But that's not the real problem. by Anonymous Coward · · Score: 0
      We GAVE peace a chance. Boycott the ANTI-war machine.


      Are we supposed to listen to someone with their head shoved so far up their ass?

    5. Re:But that's not the real problem. by Anonymous Coward · · Score: 0

      Red Hat Linux 9: Red Hat Linux Customization Guide
      Appendix A. Building a Custom Kernel

      https://www.redhat.com/docs/manuals/linux/RHL-9- Ma nual/custom-guide/ch-custom-kernel.html

    6. Re:But that's not the real problem. by Anonymous Coward · · Score: 0
      Sorry kid, but the docs you are looking for are installed. Go look in /usr/src/linux-*. Then go look in the Documentation directory.


      Too hard to read or find? Then download the latest kernel from your disto...


      Read... don't put you head in the sand and then complain that you cannot see...

    7. Re:But that's not the real problem. by Anonymous Coward · · Score: 0

      With SuSE, you can start yast, and select 'Online Update'

      It will fetch a list of updates, select those that apply to your installation, present the list for confirmation, and install them, just a few clicks on 'Continue'.

      You can also have all updates installed with no questions asked, or set it up to run from cron.

  44. Re:In Linux... by PowerBert · · Score: 1

    I know the feeling it took me 6 hours to make this comment. It's so damn hard typing "make oldconfig" with only one finger ;-)

  45. "Bugs"? by spitzak · · Score: 2, Insightful

    The title of the article says "Root Vulnerability"!

    Anybody with any rudimentary knowledge knows that this is about the worst possible thing they could say. They did not even say "Local Root Vulnerability" which they could have.

    1. Re:"Bugs"? by Necrobruiser · · Score: 1

      I understand that the title of the article says "root vulnerability", but the post describes it as "a bug in the mremap(2) system call". What I'm trying to say is that had this "bug" occurred in a Windows service, it would not be described as a "bug", but as a "security hole" or "security flaw".

      --
      "I planned within my means and got a fixed rate mortgage, so where's MY bailout?" -cafepress
  46. YOUR SMILEY LOOKS LIKE EDDIE MUNSTER by Anonymous Coward · · Score: 0

    Your smiley looks like Eddie Munster.

  47. Parent: +5 FUNNY by blixel · · Score: 1

    If it ain't broke... ...it is now.

    Ahhahahahaha... that's FUNNY!

  48. Re:I got rooted by Anonymous Coward · · Score: 0

    Looks like wget's output. Are you trolling or are you sincere?

  49. RSVP Please! by 680x0 · · Score: 1
    Techincally, RSVP is an abbreviation of the French phrase "Repondez, s'il vous plait" (which loosely translated is "Respond, please"... more literally "respond, if it pleases you"). So, the final three letters SVP take the place of "Please".

    Similar, but not quite as obviously redundant as the other examples cited.

  50. How do you patch? by blixel · · Score: 1

    Normally I just download the entire 25MB+ tar.bz2 file, copy my config over and then recompile. But this is pretty major waste of their bandwidth and my time. Can someone give me a quick 1, 2, 3, on patching my existing /usr/src/linux-2.4.23 directory to become 2.4.24? Or are there some kind of advantages to just doing it the way I've been doing it?

    1. Re:How do you patch? by pr00f · · Score: 2, Informative

      cd /usr/src/linux-2.4.23 ; patch -p1 /path/to/patch.diff

      Recompile and off you go.

    2. Re:How do you patch? by demi · · Score: 5, Informative

      Okay:

      1. Download patch to /usr/src
      2. cd /usr/src (since that's where you say your linux-2.4.23 is)
      3. bzip2 -dc patch-2.4.24.bz2 | patch -p0
      4. mv linux-2.4.23 linux-2.4.24
      5. cd linux-2.4.24
      6. Now build and install your kernel as you like it, just as you would from the virgin tarball (make depend; make however you make your kernel and modules).

      Hope that helps!

      --
      demi
    3. Re:How do you patch? by pr00f · · Score: 2, Informative

      Damn. < got removed. Sorry.

      patch -p1 < /path/to/patch.diff

    4. Re:How do you patch? by blixel · · Score: 1

      Does this in effect make my 2.4.23 source tree == 2.4.24? Or is it still 2.4.23 with just the patches applied?

    5. Re:How do you patch? by grimiore1 · · Score: 0
      --
      Ben, you've become an UberGeek! Take me as your padawan!!!
    6. Re:How do you patch? by blixel · · Score: 1

      Thanks... that does help. I asked this question up above but I'll ask again here. When you patch the kernel like this, do you end up with the same exact tree that you would have if you downloaded the 2.4.24 source tarball and extracted it? In other words, am I "missing" anything by patching as opposed to downloading anew?

      like would "diff -r /usr/src/linux-2.4.23-patched /usr/src/linux-2.4.24" come back with any differences?

    7. Re:How do you patch? by Anonymous Coward · · Score: 0
      You can also use the patch-kernel utility, shipped with the kernel itself:
      • cd /usr/src/linux/scripts
      • ./patch-kernel ../ /dataLinux/kernel
      The first parameter is the location of the kernel tree (usually the directory right above the one you are in currently), the second the directory that contains the patches. It will apply all the patches it can find in the specified directory...
    8. Re:How do you patch? by Ben+Hutchings · · Score: 1

      If you unpack an official 2.4.23 tarball and apply the official 2.4.24 patch, the result is the same as if you unpack an official 2.4.24 tarball. If you made any changes in between unpacking and patching (e.g. by configuring it or building it) then the result is not the same, but this is OK as long as you "make $CONFIG_METHOD_OF_CHOICE && make dep && make clean" in the new tree before building the new kernel.

    9. Re:How do you patch? by defMan · · Score: 1

      like would "diff -r /usr/src/linux-2.4.23-patched /usr/src/linux-2.4.24" come back with any differences?

      No changes at all. This is going to be identical.

    10. Re:How do you patch? by Anonymous Coward · · Score: 0

      Yes; no. Or rather: yes; what's the difference?

    11. Re:How do you patch? by spudgun · · Score: 1

      cd /usr/src/linux-2.4.x
      bzip2 -dc /path/to/patch-2.4.y.bz2 | patch -p1

      --
      Type unto others as you would have them type unto you.
    12. Re:How do you patch? by Zey · · Score: 0
      Interesting the differences in technique, given the same tools...
      • cd /usr/src/linux # get to your linux source directory
      • wget http://location/patch.bz2 # download it
      • bunzip2 patch.bz2 # decompress patch
      • patch -p1 <patch.bz2 # patch it to existing source.
      • make oldconfig # update your existing config (get prompted for new stuff)
      • make all install modules modules_install # compile, install

  51. Can anybody explain... by Avian+visitor · · Score: 2, Interesting

    If the only changes from 2.4.23 to 2.4.24 were some "minor" bug fixes, why do I see such a big difference in the size of the kernel binary?


    -rw-r--r-- 1 root root 667113 Dec 1 22:44 vmlinuz-2.4.23
    -rw-r--r-- 1 root root 713946 Jan 5 18:53 vmlinuz-2.4.24

    1. Re:Can anybody explain... by tepples · · Score: 1

      Did you re-configure your kernel, compiling in 47 KB worth of extra drivers?

    2. Re:Can anybody explain... by Anonymous Coward · · Score: 0

      Or, perhaps there are 47Kb worth of NEW drivers, that have not been configured OFF?

    3. Re:Can anybody explain... by Avian+visitor · · Score: 1

      I only applied the patch-2.4.24 and recompiled the kernel. I didn't enable or disable any features. The configuration files are exactly the same.

    4. Re:Can anybody explain... by Anonymous Coward · · Score: 0

      Did you download the copy of the source that contains my new virus? You better not. That virus is untested. Remove it from your kernel config and remake.

    5. Re:Can anybody explain... by Anonymous Coward · · Score: 0

      heh. they inserted netbus troyan binary. since it is a windows executable there is a planty of windows emulation code ... :)

    6. Re:Can anybody explain... by ender_wiggin30 · · Score: 1

      Dude, the difference is the exploit code. It comes with the kernel for interested crackers.

  52. Hole not that awful by 0x0d0a · · Score: 1

    The story submission sounds pretty bad, but if you read the lkml email, it's actually pretty subtle. There's an obscure memory manager bug that requires some pretty serious finagling to be exploited.

  53. Re:I got rooted by ZorroIII · · Score: 1

    The url contains an elf executable:

    $ ls -l sys
    -rw-rw-r-- 1 user user 17313 des 11 17:18 sys
    $ file sys
    sys: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped
    $ strings sys

    [..]

    /dev/ptmx
    /dev/pty
    /dev/tty
    sock et
    bind
    listen
    LameBD is starting..duh
    OK, pid = %d
    /dev/null
    /tmp
    HOME=%s
    Can't fork pty, bye!
    /bin/sh

    Looks like something bad

  54. Kernel patches as modules? by Ktistec+Machine · · Score: 5, Interesting
    Hi folks,

    I remember, back when the last ptrace bug was found, some kind soul created a kernel module that (a) renamed the current ptrace function to something else and (b) implemented a new wrapper function that first checked to see if you were root, before deciding whether to call the old ptrace. Slick!

    I'm surprised this sort of workaround hasn't been done for other kernel bugs. It seems it wouldn't even have to be a workaround. A module could actually provide a new, repaired version of the buggy routine. Couldn't it?

    I can imagine insmoding a list of "kernel-fix" modules at boot time. Then, every once in a while , I'd upgrade my machines to a new kernel, but without the urgency of getting a new kernel installed RIGHT NOW! to fix a small (code-wise) security problem.

    1. Re:Kernel patches as modules? by Anonymous Coward · · Score: 4, Informative
      I remember, back when the last ptrace bug was found, some kind soul created a kernel module that (a) renamed the current ptrace function to something else and (b) implemented a new wrapper function that first checked to see if you were root, before deciding whether to call the old ptrace. Slick!

      Modules (or really any third-party code regardless of method be it /dev/kmem or modules or whatever) having access to the syscall table of a running kernel is (1) evil, (2) nonportable - it won't work on many of our architectures, and (3) likely to become even harder as the kernel gurus try to defeat people doing stupid things like this.

      BTW, this also affects things like (why would you need this?) realtime virus scanners that hook syscalls. Please, don't do this. If the argument is that you need the machine to stay up because it's too important to reboot for a patch, then you definitely should not be inserting modules that *intentionally overwrite important chunks of kernel memory* because if there's the slightest thing wrong, your machine will either crash or begin to do bizarre things. You could end up with data corruption and/or loss for an extended period before you even realize it. Do not do this. It is not what you want. Believe me.

    2. Re:Kernel patches as modules? by Imperator · · Score: 1

      Though this should be obvious, another advantage of distributing patches as modules is that you don't need to reboot to install a module.

      --

      Gates' Law: Every 18 months, the speed of software halves.
  55. I, for one, by Anonymous Coward · · Score: 0

    ...welcome our Depinguinator overlords!

    Lin^H^H^HBSD User

  56. Ambiguity by tepples · · Score: 1

    I'm gonna do something illegal to the next person that says ATM machine, too.

    What do you claim distinguishes "ATM" the cash machine from other meanings of "ATM" more easily than "ATM machine"?

    1. Re:Ambiguity by micromoog · · Score: 1
      What do you claim distinguishes "ATM" the cash machine from other meanings of "ATM" more easily than "ATM machine"?

      Context?

  57. Trademarks are adjectives by tepples · · Score: 2, Informative

    Even so, "New Technology" is a name for that technology.

    No. "Windows NT" is a trademark. The law recommends using trademarks and service marks as adjectives. Even if the mark consists of initials, one of which would expand to a generic term for the product (such as "FS" in "XFS" or "T" in "NT"), the law still recommends following the mark with a spelled-out the generic term.

  58. MOD PARENT DOWN!!! by Anonymous Coward · · Score: 0

    poster faked his mod points!

  59. Analogy overload!!! by Anonymous Coward · · Score: 0

    Okay so is XP the Camry or a Camaro

  60. Badger? by tepples · · Score: 1

    but I didn't have to badger anyone to get it

    True, but did you have to use a mushroom mushroom?

  61. PIN number by Chazmati · · Score: 1

    Well you couldn't call it the PI number, because that's 3.14159... and just think if everyone had to type pi in on the ATM keypad. They would be there all day. Or longer. Much longer. :)

    1. Re:PIN number by Drantin · · Score: 1

      Sometimes it's referred to as your PIN rather than your 'PIN number'...

      --
      Actio personalis moritur cum persona. (Dead men don't sue)
  62. Re:I got rooted by jrexilius · · Score: 1

    Just FYI check out:

    http://www.sleuthkit.org/index.php

    http://ohiohtcia.org/linuxintro-1.8.1.pdf

    Also do a cksum comparison with your distro's packages and whats on your filesystem.

    I wrote many years ago (as did millions of other people) an ugly little perl script (that needs to be updated) to find SetUID files. Give it a try also:

    http://www.jasonrexilius.com/code/find_suid.txt

    You will want to add to it a recursive function or use the find command:

    find / -type d -exec [theperlscript] {} \;

    this is very slow obviously..

  63. Slashdot definition of IE by tepples · · Score: 1

    HTML rendering libraries are used throughout the OS(explorer, help,...), and these are part of IE

    As you correctly recognize, when most Slashdot users refer to "IE", they refer to MSHTML.dll and its dependencies, not strictly to the 89 KB iexplore.exe shell. Most vulnerabilities "in IE" actually lie in MSHTML.dll or in one or more of its dependencies; hence the Windows Update warnings to the effect of "This affects you even if you don't use Internet Explorer as your primary web browser."

    that doesn't make IE a part of the OS

    Would you consider explorer.exe a part of the operating system? It uses MSHTML.dll. I claim that if a given program forms a "part of the operating system," then everything it depends on is also OS as well.

  64. Apparantly Linux distros worse than Winsoze by AlanWay · · Score: 1

    Also, is Linux more secure than Windows, because I hear a fair amount of Linux security holes more than Windows

    Well, according to the Inquirer http://www.theinquirer.net/?article=13420 some Linux distro's are WAY worse than Windoze. For e.g. Debian GNU/Linux 3.0 with 186 vulns last year opposed to Windoze XP Home with 32

    I find this very hard to believe, and haven't checked their sources yet, but it does look disturbing. Makes me wonder what comprises a "Linux" vuln vs a Windoze one?

    1. Re:Apparantly Linux distros worse than Winsoze by Anonymous Coward · · Score: 0

      Well The Inquirer are very well known for exaggerating things, and frankly, they pick up every rumour they can find and print it off, so I would double check if I were you ;).

    2. Re:Apparantly Linux distros worse than Winsoze by defMan · · Score: 1

      One important point to note is that Debian GNU/Linux comes with a lot of (optional) software, like multiple browsers, multiple desktop environments (KDE/Gnome/GNUStep?), editors, databases, etc. This means that a vulnerability in one of these pieces of software might count as a debian vulnerability.

      Windows comes with a very limited set of software and other software is available separately (Oracle database, Mozilla, Photoshop). This means that those won't count towards a windows vulnerability.

      Windows might still have less vulnerabilities (but i'm not counting on it).

  65. Codename: Angus by gfilion · · Score: 1

    This kernel received the codename: Angus; it should be refered to as "Kernel Angus," for example:

    Daddy: Oh, watch out, Melinda! Once a woman is introduced to Kernel Angus, she'll settle for nothing less.

    Melinda: Daddy, they say all the womenfolk just love Kernel Angus!

    Daddy: Hmm.. I don't know why people make such a big fuss over Kernel Angus!

    Miss Anabelle: I myself never much cared for Kernel Angus! He rubs me the wrong way. I'm not sure why.. can't put my finger on it..

    Daddy: Kernel Angus is an acquired taste! Bedelia!

    Props to Tina Fey for writing this great SNL skit.

    (BTW, It's easier to catch the joke if you read it out loud...)

    1. Re:Codename: Angus by mwillems · · Score: 1

      I personally prefer Kernel Sanders. Or perhaps Kernel Ghadaffi.

      --

      ---
      BDOS ERR ON A:>
    2. Re:Codename: Angus by Anonymous Coward · · Score: 0

      Or easier for OTHERS to catch the joke if you say it aloud. Not exactly cubicle-safe, eh? :)

  66. Password? by DarkRecluse · · Score: 1

    So if I was worried enough to set a root password on my linux box, I would be worried enough to use this patch right?

    --
    --"It's Bradford Company, slash your last name, dot your first name"
    1. Re:Password? by Anonymous Coward · · Score: 0

      If you have local users other than yourself, you might be well advised to upgrade.

  67. SuSE 8.2 already has a fix by Anonymous Coward · · Score: 0

    Moin,

    I just checked the Yast Online Update and there is already a fixed kernel for SuSe 8.2! Woa! I hope this time I don't need to re-install the Nvidia drivers....

    Cheers,

    Tels

  68. Microsoft To Linux by Anonymous Coward · · Score: 0

    Hello pot, this is kettle. Your black.

  69. Damnit!... by TypoNAM · · Score: 1

    Redhat just killed Redhat 7.3 support too!

    --
    This space is not for rent.
    1. Re:Damnit!... by Anonymous Coward · · Score: 0

      Red Hat Linux 7.3:

      SRPMS:
      ftp://updates.redhat.com/7.3/en/os/SRPMS /kernel-2. 4.20-28.7.src.rpm

      athlon:
      ftp://updates.redhat.com/7.3/en/os/athl on/kernel-2 .4.20-28.7.athlon.rpm
      ftp://updates.redhat.com/7. 3/en/os/athlon/kernel-s mp-2.4.20-28.7.athlon.rpm

      i386:
      ftp://updates.redhat.com/7.3/en/os/i386/k ernel-2.4 .20-28.7.i386.rpm
      ftp://updates.redhat.com/7.3/en /os/i386/kernel-sou rce-2.4.20-28.7.i386.rpm
      ftp://updates.redhat.com /7.3/en/os/i386/kernel-doc -2.4.20-28.7.i386.rpm
      ftp://updates.redhat.com/7. 3/en/os/i386/kernel-BOO T-2.4.20-28.7.i386.rpm

      i586:
      ftp://updates.redhat.com/7.3/en/os/i586/k ernel-2.4 .20-28.7.i586.rpm
      ftp://updates.redhat.com/7.3/en /os/i586/kernel-smp -2.4.20-28.7.i586.rpm

      i686:
      ftp://updates.redhat.com/7.3/en/os/i686/k ernel-2.4 .20-28.7.i686.rpm
      ftp://updates.redhat.com/7.3/en /os/i686/kernel-smp -2.4.20-28.7.i686.rpm
      ftp://updates.redhat.com/7. 3/en/os/i686/kernel-big mem-2.4.20-28.7.i686.rpm

  70. MOD UP! by Kalak · · Score: 1

    I've already posted in this thread, or I'd mod this one up myself. This answers a debate we were having at work about an errata being released after the EOL date.

    --
    I am, and always will be, an idiot. Karma: Coma (mostly effected by .hack)
  71. Yuck by anthony_dipierro · · Score: 1

    Isn't there a workaround besides reinstalling a new kernel?

  72. Bad 3 months for Linux. by imbaczek · · Score: 1

    2 local (= almost remote) roots in the kernel in 3 months isn't good. Guess the OpenBSD paranoia isn't that bad after all.

  73. Proof-of-concept exploit code for x86 by devine10 · · Score: 1

    Available here.

    1. Re:Proof-of-concept exploit code for x86 by Anonymous Coward · · Score: 0

      I see a small kernel dump and then a hard reboot...

      Not very useful!

    2. Re:Proof-of-concept exploit code for x86 by devine10 · · Score: 2, Informative

      It means your kernel is vulnerable. Writing an exploit that yields root privileges is much harder though.

  74. Re:I got rooted by Kegetys · · Score: 1

    Maybe you had a PHP page that passes input from the URL to the 'include' PHP function? Its an "easy" way to exploit, since you can pass an URL to another PHP script to it and PHP will grab that file and execute it. This might have been used to download a file with wget (executed with PHP, which is why the wget's output is in the apache log) and then executed it, and the binary propably used some local root exploit to gain root privileges for the apache user.

    I have had a few attempts like that on my server (this for example, no idea what it does), but I was prepared with a syntax check for the variable passed to include and it didnt work ;)

  75. Re:Hah! by AndreyF · · Score: 0

    This is not flamebait, but a very valid argument many people use against linux.

    The point it failes to realize though is that with linux, a patch comes out for every exploit almost instantaneously, and anyone is able to patch it. With windws, one has to wait for MS to come around to patching it, since they are the only ones that decide what is worth patching and when.

    A windows patch may happen tomorrow, next week, next month, or may not happen at all!
    A linux patch, if important, will be patched almost instantaneously, and if not, you can patch it all by yourself if you like.

  76. what was the change? by flok · · Score: 1

    What was actually the change? that way I can merge it into 2.4.21

    (upgrading to 2.4.24 ain't an option for me: the UPS-software stopped working after version 2.4.22)

    --

    www.vanheusden.com - home of Multitail, HTTPing, CoffeeSaint, EntropyBroker, rsstail, bsod, listener, nagcon, nagi
    1. Re:what was the change? by Anonymous Coward · · Score: 0

      The relevant portion of the patch appears to be:

      --- linux-2.4.23/mm/mremap.c 2003-08-25 04:44:44.000000000 -0700
      +++ linux-2.4.24/mm/mremap.c 2004-01-05 05:53:56.000000000 -0800
      @@ -241,6 +241,13 @@

      if (new_len > TASK_SIZE || new_addr > TASK_SIZE - new_len)
      goto out;
      + /*
      + * Allow new_len == 0 only if new_addr == addr
      + * to preserve truncation in place (that was working
      + * safe and some app may depend on it).
      + */
      + if (unlikely(!new_len && new_addr != addr))
      + goto out;

      /* Check if the location we're moving into overlaps the
      * old location at all, and fail if it does.

    2. Re:what was the change? by Lost+Race · · Score: 1
      Easy linky patchy here.

      (2.4.22 and up break ACPI for me.)

  77. PI number by LearnToSpell · · Score: 1

    That's an interesting idea - you can have any PIN you want, as long as it's a substring of Pi. If you don't want someone stealing your code, learn more numbers! Plus, having people memorize long sequences of random numbers would have the obvious benefit of, um, uhh... well, it wouldn't be much different than what we have now, anyway.

  78. Get the updated binary rpm for your distros... by Anonymous Coward · · Score: 0

    or the apt or similar stuff.

  79. Word. by LearnToSpell · · Score: 1

    I be gettin' mah cash money from the ATM machine, biznatch.

  80. Checkout Buildkernel by LinuxHam · · Score: 1

    Here is a great little utility which makes building new kernels easy. It automates the process of downloading and applying patches, and can be easily configured to build a new kernel reusing your previous kernel config selections. Makes the download/patch/recompile process about as seamless as it gets, especially if you have a static kernel config.

    --
    Intelligent Life on Earth
  81. UID 0 by Anonymous Coward · · Score: 0


    Proper exploitation of this vulnerability may lead to local privilege escalation including execution of arbitrary code with kernel level access. Proof-of-concept exploit code has been created and successfully tested giving UID 0 shell on vulnerable systems.

    Awwwww yeaaahhh....

  82. Re:I got rooted by Anonymous Coward · · Score: 0

    Yes, I really did get rooted. I'm running Debian, and I suddenly started getting console messages from syslog with just blank lines. It had been up for around 150 days, so I figured it was getting flaky and I'd do an apt-get upgrade and reboot. I tried that, but I got access denied messages (as root), some other stuff broke (like netstat would only segfault), did some more research, and chkrootkit found "t0rn v8"... I did a complete backup of the system and reinstalled (so I can look at the backup to figure out what happened). I do hope I can figure out how they got in so I can prevent it in the future.

  83. FAT Table by blixel · · Score: 1

    FAT Table is one I use to hear a lot

  84. 2.0.40? by drwtsn32 · · Score: 1

    What I want to know is when 2.0.40 will be released. rc6 has been out for over 18 months...

    1. Re:2.0.40? by JDWTopGuy · · Score: 1

      Did it ever occur to you that rc6 might essentially be 2.0.40? If they haven't had to change it in 18 months, it might be stable...

      --
      Ron Paul 2012
    2. Re:2.0.40? by Anonymous Coward · · Score: 0

      Or it might be abandoned. Then again, that never happens, does it.

  85. Re:I got rooted by Anonymous Coward · · Score: 0

    I wrote many years ago an ugly little perl script to find SetUID files.

    Perl idiocy strikes again.

    I mean, why learn how to properly admin the OS when you can waste time writing a Perl script instead?

    Hint: typing 'find / -perm 4000' will show you all of the SUID files on your system.

  86. My God... by Kjella · · Score: 1

    You mean that a company living off selling support, is prodding their customers towards downloading new kernels from their support?

    Seriously though, apart from here on slashdot I think the distro's have updated patches before 99,9% of the users compiling from source. So unless you absolutely want to dick around wtih your own kernel, what's the big point?

    To have thousands of Linux admins, running the same distro, all compiling the same kernel on thousands of machines is not "prime-time". It's a wasteful and futile duplication of effort.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  87. Gkrellm by tekniklr · · Score: 1

    When I upgraded to this kernel version, gkrellm stopped working. Did anyone else experience the same thing, or is it something unique to me?

    The debug information is incredibly unhelpful. It hangs here forever (at least until I -C it...)
    bash-2.05b$ gkrellm -w -d 3
    --- GKrellM 2.1.24 ---
    diskstats=0 partition_stats=0 sysfs_stats=0

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

      I guess you have to rebuild your sensor modules.

    2. Re:Gkrellm by tekniklr · · Score: 1

      It turns out it was the Seti@home plugin not working.

  88. we got r00t, d00d!!! by t0ny · · Score: 0, Flamebait
    Wow, another Linux kernel root exploit. Its nice to see the crown jewel of the OSS community really shine.

    Whats that everyone says about having so many eyes on the code? Looks like they may need to add a few more eyes.

    --

    Manipulate the moderator system! Mod someone as "overrated" today.

    1. Re:we got r00t, d00d!!! by Anonymous Coward · · Score: 0

      Nevermind the fact that anyone with a few script kiddie tools can get administrator access on Win XP with a few clicky clicks, if they can physically gain access to the computer. This is what this linux bug entails. Now, Microsoft has acknowledged that "feature" in Microsoft for what 2 years now and has no intention of changing it because it would require a complete overhaul of the basic gui concent for windows. This is the first time you've ever heard about this linux vulnerability right....and wow it's fixed! How about...you shut the fuck up!

    2. Re:we got r00t, d00d!!! by Anonymous Coward · · Score: 2, Insightful

      Seems to me, those eyes just found something...

    3. Re:we got r00t, d00d!!! by t0ny · · Score: 1
      Nevermind the fact that anyone with a few script kiddie tools can get administrator access on Win XP with a few clicky clicks, Prove it: because its not actaully true.

      if they can physically gain access to the computer. This is what this linux bug entails.

      Sigh. Once again, let me expain something to all you pseudo-expert security n00bs here: If somebody can get physical access to your computer, you have already lost. If I can gain physical access to a linux server, I could just unplug it and remove the hard drives. Wow, a security breach that only took me five minutes! Not only that, but my 'exploit' is platform independant, too. Since I have posted it here, I'll throw you a bone and make it an 'Open Source' exploit.

      If you actually knew what you were talking about, you wouldnt have made that statement. So go take some security classes, kid, and you may want to take you head out of the sand while you are at it.

      This is the first time you've ever heard about this linux vulnerability right....and wow it's fixed!

      I wonder how long the exploit that r00ted Caldera was in the wild for? I would guess pretty long. But since you guys taut how supposedly secure Linux is over Windows, it must be kind of scary that there have been two KERNEL-LEVEL r00t exploits in as many months. Almost makes one want to take their head out of the sand and look at the REAL world!

      Nah.

      How about...you shut the fuck up!

      How about you post with your real account instead of being a little pussy?

      How about you get ready for school tomorrow, kid?

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    4. Re:we got r00t, d00d!!! by MrNybbles · · Score: 2, Insightful
      if they can physically gain access to the computer. This is what this linux bug entails.

      Sigh. Once again, let me expain something to all you pseudo-expert security n00bs here: If somebody can get physical access to your computer, you have already lost. If I can gain physical access to a linux server, I could just unplug it and remove the hard drives. Wow, a security breach that only took me five minutes! Not only that, but my 'exploit' is platform independant, too. Since I have posted it here, I'll throw you a bone and make it an 'Open Source' exploit.

      I think you are missing the point. These people are not worried about someone walking in and taking hardware, they are worried about someone sneaking into the system and using it as a zombie or steal information without anyone knowing about it.

      You also missed the obvous, this bug can, in theory, be exploited remotly given the right kind of access.

      I wonder how long the exploit that r00ted Caldera was in the wild for?

      It doesn't really matter how long the bug/exploit existed. What matters is how big of a problem the exploit is and how fast it is fixed. Microsoft tends to take forever to fix it's bugs and it doesn't always do that right. Some patches would undo other patches and one of my friends ran Windows Update and it broke his ability to connect to the Internet.
      To take advantage of the mremap() syscall bug a person would either need to be able to run an executable on the Linux Box or be able to get some poorly written program to do it. And what business do most programs have calling mremap() anyway? This is not an easy bug to exploit. I would say that this exploit is not that big of a problem for most people and was fixed quickly. For people running a system where the admin was stupid enough to give untrustworthy people a login accout or somehow the ability to run executables, well, they should have been expecting something bad to happen.

      But since you guys taut how supposedly secure Linux is over Windows,. . .
      Why the hell are you comparing a Kernel to a collection of Operating Systems and Operating Environments (Windows 3.X 9X are not actually sperating systems) ?!? Most of the exploits of a Linux Distro are from the third party packages. I don't ever remember seeing anyone faulting Microsoft for a security hole in Windows caused by some third-party software. That Caldara exploit was most likely in a distro package, not Linux. Please get your terminology down before you pretend to know something.

      Almost makes one want to take their head out of the sand and look at the REAL world!

      Yah, and guess where your head is stuck? I'll give you a hint, it's not the sand. :p

      "Windows is better because. . .. Linux is better because. . . Mac is better because. . . Whoever sets the terms of the argument always wins (unless that person has no idea how to argue correctly)" -- MrNybbles

      --
      Losing faith in humanity one person at a time.
    5. Re:we got r00t, d00d!!! by parksie · · Score: 0, Troll

      Some patches would undo other patches and one of my friends ran Windows Update and it broke his ability to connect to the Internet.

      That's probably the most useful patch MS ever included in Windows Update.

    6. Re:we got r00t, d00d!!! by t0ny · · Score: 1

      Nice FUD, security n00b. Like all good FUD, its heavy on anecdotes and light on facts.

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    7. Re:we got r00t, d00d!!! by MrNybbles · · Score: 2, Insightful
      Nice FUD, security n00b. Like all good FUD, its heavy on anecdotes and light on facts.

      I took the time to tell you what was wrong with your arguments and even quoted your post for easy refrence and the best you can do is call me a noob and say I am light on the facts. Do you blow everyone off that way or just the people you can't reply to with a solid argument?


      First of all, what I wrote is not FUD. At most it would be misinformation and what I wrote is not even that. How could what I have said put Fear, Uncertainty, or Doubt into anyone that is unjustified. Did I say anything that you can prove is a lie? Back up what you have said.


      Second, I am not a security newbie, and am not a noob. If you disagree then define what a newbie or noob is and say why I fit that description. Back up what you have said.


      Third, FUD is usually not anecdotes but lies and half truths. Also, what I posted in my last reply is not an anecdote but an example. An anecdote is the telling of an interesting or humorous incident. My firend loosing the ability to connect to the Internet was not funny.


      Fourth, Microsoft left many security holes unpatched cuasing lists such ashttp://www.pivx.com/larholm/unpatched/ to be made. Unfortunatly it looks like Microsoft talked them into taking down the list.


      Microsoft Refuses To Fix NT 4.0 Exploit

      http://slashdot.org/article.pl?sid=03/03/27/1930 25 6&mode=thread&tid=201&tid=128&tid=172

      Okay, so when was the last time you saw the Linux Kernel people or the GNU people refuse to patch a known exploit?


      I also pointed out that the Linux Kenrel exploit could be done remotly, something that you had totally missed.


      Does anyone else see the irony of Ms t0ny accusing me of being light on facts and yet backing up nothing that she has said?


      Windows is not perfect. Linux and Gnu software is not perfect. Apple products are not perfect. If someone mad a lean, efficient OS that did everything, was secure and never screwed up I would buy it. I am still looking.


      Okay, now that I have thrown a few facts your way, do you have the balls to refute or apologize?

      --
      Losing faith in humanity one person at a time.
  89. debian by Anonymous Coward · · Score: 0

    is this what got those debian ftp server(s?) a while back?

  90. Apparently Inquirer worse than brain dead monkey by moncyb · · Score: 2, Interesting

    Arrgh! Not more people who just count the number of vulnerabilities! I just skimmed that article, but it looks like crap to me. Standard Microsoft trolling, nothing else.

    Don't listen to anyone who claims something is more secure based on the number of vulnerabilties. I bet if you look at all the "vulnerabilities" counted for Debian, most of them were for crap you'll never use (they seem to have every single little open source project ever made) or something stupid like "users can manipulate the high score file of some lame obsure video game." You have to look at what the vulnerablilites are.

    You should also take into consideration whether or not the organization in charge will disclose all vulnerabilities they know about. Debian is very open, they probably couldn't keep such things a secret if they wanted to. Also, I think Debian has far more packages than any other Linux distro (certainly far more software than MS ever put out), so obviously they are going to discover more problems.

    When I hear someone say a MS product is more secure than anything, my bullshit meter flies off the dial. Maybe something written by a ten year old script-kiddie. ...or something deliberately botched. I buy the statement something made by IBM or HP would be more secure (especially considering those projects are probably more mature), though obviously anything written by that reporter can't be trusted, and merely listing the number of disclosed vulnerabilities doesn't mean anything.

    This is total crap (emphasis mine):

    The other significant feature [talking about the three most "secure"] of these operating systems is the language in which they are written. The two from IBM are both written in assembler...

    C and similar languages that use pass-by-value techniques are exceptionally prone to buffer overflow... Avoiding the use of these languages at the most vulnerable points, namely user I/O and network I/O, would appear to be wise. Linux, Unix and Windows are almost entirely written in C, and most of their middleware and application software is also in these vulnerable languages, so it should come as no surprise that they are less secure than OpenVMS, OS/400 and zOS.

    Does this guy know what assembly language is???? It doesn't have any sort of bounds or type checking at all---well unless it is built into the processor design (I am not familiar with mainframe CPUs), and if it is, a C compiler written for that processor will most certainly use those features too.

    Also, looking at the table, they included OS 9. Does that version even have a filesystem permission system or a concept of users? Why don't they just include Win98 too. That's like saying "the building uses empty frames instead of doors. We didn't find any problems with the locks, therefore the building must be secure."

  91. Re:I got rooted by YetAnotherDave · · Score: 1

    to find setuid files, try using 'find'
    :)

    the following finds all setuid or setgid files in /usr/bin (on my laptop, which I haven't hardened much yet)
    [dave@scallop dave]$ find /usr/bin -perm +6000 -print
    /usr/bin/rcp
    /usr/bin/rsh
    /usr/bin/chfn
    /usr/bin/chsh
    /usr/bin/sudo
    ...

  92. Why would Microsoft promote bad designs? by geoswan · · Score: 1
    When I was growing up people used to ask, "can I get a virus by reading my mail?" And the short answer was "No". A longer answer was, "No. To get infected you have to execute a program of some kind. e-mail is just data. It is not executable."

    Then Microsoft announced plans to make the data files of its flagship applications executable.

    They were warned. Security experts warned that this crazy innovation would allow vandals to infect Word files and to infect e-mail.

    Microsoft ignored the warnings. And it wasn't long before the first Word macro viruses were seen in the wild. But, in the end, the e-mail viruses, that raided your address book, turned out to be much more expensive.

    Why?

    Why would a corporation with the public interest at heart introduce a suite of programs with such a fundamental design flaw?

    Some wise man counselled, "Never attribute to malice that which can be explained by incompetence." I used to think that this bad design could be explained by incompetence on Microsoft's executive floor.

    About a year ago I started to wonder about this. Gates and Ballmer started talking about security. Palladium . The Trusted Computing Platform. When I read about these schemes I realized that the explanation for Microsoft's terrible design choices could be part of a deep game. Make the internet an insecure place in the mid nineties? Reap the rewards by getting your victims^H^H^H^H^H^H^Hcustomers to welcome allowing you draconian control over their computers in the mid 00s?

    1. Re:Why would Microsoft promote bad designs? by slittle · · Score: 1
      Then Microsoft announced plans to make the data files of its flagship applications executable.

      And what do you propose as the alternative? No scripting? No macros? Do you realise you can write a virus in Postscript? Do we migrate to bitmap printing?

      What about forcing users to start applications, then load the data file into it, rather than be able to doubleclick the datafile and have it automatically load the application?

      What about true executables? Should email attachments not have Execute permissions by default? To accomplish... what?

      Nothing you have stated will ever succeed. Users will demand their fucked up frog-in-a-blender, singing-christmas-card and whatever other intra-office crap they get. They will work around the lack of +x and they will switch to competitors products if their macros stop working.

      Users are the design flaw.
      --
      Opportunity knocks. Karma hunts you down.
  93. exploit by Anonymous Coward · · Score: 0

    http://www.securitytracker.com/alerts/2003/Dec/100 8386.html

  94. Timely kernel update for Redhat by mrobinso · · Score: 1
    How convenient is that, a kernel update that fixes a major vulnerability a mere 5 days after support for the bulk of Redhat products expires.


    Awesome co-inkydink.

    .mike

    --
    -- Karma whore? You betcha. --
  95. Re:I got rooted by Anonymous Coward · · Score: 0

    Server has been up for 150 days, was hacked, and you wonder how they came in? Wow.

    Now this is how you can prevent it in the future: how about upgrading the kernel every time they release a security patch? You wouldn't have a 150 day uptime if you did that.

    I would recommend you choosing a serious distribution like Debian or Suse, use just the packages - do not compile anything what you do not really need, subscribe to the mailing list and UPDATE THE SYSTEM every time an update is released. Howgh.

  96. Re:I got rooted by jrexilius · · Score: 1

    It was actually a function called as part of a larger script where after it found the SUID files it did a number of other things.

    In short it isnt perl idiocy but a small part of a larger piece of logic that was just less efficient to code in bash or ksh.

    So relax and get off your soap box.

  97. Re:I got rooted by jrexilius · · Score: 1

    Yeah, that is the simple way ;-) The original script was actually just a subroutine that was called as part of a bunch of other stuff (like comparing cksums off of a known source CDROM, generating a list off diffrences, etc.). I referenced that script for the guy so he could get started developing something for himself. Better to teach someone to fish as they say..

  98. Re: goto vs break by some+guy+I+know · · Score: 1
    And that's why you use non-syntactic macros:
    #define BLOCK_START(x) {
    #define BLOCK_BREAK(x) goto x
    #define BLOCK_END(x) } x:

    ...

    void example ()
    {
    BLOCK_START(abc);
    if (error) BLOCK_BREAK(abc);
    code
    if (error) BLOCK_BREAK(abc);
    code
    if (error) BLOCK_BREAK(abc);
    code
    BLOCK_END(abc);
    cleanup code
    }
    (The above is meant to be a joke, but I have actually seen code similar to this.)
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  99. TCP/IP protocol by Anonymous Coward · · Score: 0

    Okay... but you're preaching to the choir here. Ever heard of the TCP/IP Protocol? 6 words in the acronym, 3 of them are "protocol".

  100. Re:Hah! by ThaReetLad · · Score: 1

    Anyone is able to patch it who knows that the bug exists. Of course this requires all linux users to subscribe to security advisories or regularly check for new vulnerabilities. Then they need to have learnt how to merge the patched code and compile the kernel. Somehow I see this as a problem for my 80 year old grandmother, but she is quite capable of saying "Yes" when her Windows XP machine tells her she needs to let it update itself.

    How much time do you spend checking for new problems in your OS and all the rest of your software? Wouldn't that be time better spent working or doing something fun? Of course you probably are such a sad case that patching your kernel IS fun, in which case knock yourself out, but stop looking down your nose at those that actually choose to have a life.

    --
    You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
  101. 2.6.1-rc2 by Anonymous Coward · · Score: 0

    From the article: "An incorrect bound check discovered inside the
    do_mremap() kernel code performing remapping of a virtual memory area
    may lead to creation of a virtual memory area of 0 bytes length."

    From the newly released 2.6.1-rc2 Changelog: " Don't allow mremap of zero-sized areas."

  102. Incorrect by Anonymous Coward · · Score: 0
    They all strive for the same goal, to make it easier for users to use computers

    Actually, this is wrong. Microsoft's goal is to make money - they could care less about their customers. If you don't believe this, try reading their EULA's some time.

  103. Re:Hah! by AndreyF · · Score: 1

    #1 many linux distros patch themselves also, just as easily as windows.

    if you are a sysadmin and have to worry about security being exploited during the time MS is patching, the advantage linux brings is obvious

  104. Re:Hah! by ThaReetLad · · Score: 1

    OK thats fine if your job is looking after a network. You have the time, knowledge and motivation to stay up to date. On the desktop is a different story however. Most users just don't bother. The sad truth is that even a programmer I know who ought to know better still uses Win95 at home and if they can't be persuaded to make sure they're PC's are secure who can be? Personally I don't understand linux or bsd or whatever. I'm a programmer with 5+ years development on windows plus some time on VMS but I've never had the time or reason to get to know linux or BSD. I tried once and gave up after a few weeks because I couldn't get it to be stable. I was trying to customise stuff and configure it, and to be honest I was probably making a real mess. The problem with linux is that if you don't know what you are doing but have to try and admin your system you can very quickly start to feel totally overwhelmed with little or no help at hand. No good games, bad development enviroments compared to Visual C++, and frustratingly confusing file system model for someone who has really only known windows. I can't think of any reason why I would now choose to run linux as my primary desktop OS. On a server or firewall, yes maybe, but more likely I'd run a BSD, but untill I have the need for a seperate server or firewall at home, I'll be sticking to XP, secure in the knowledge that as long as I run a software firewall, anti-virus software, keep up to date with patches, use firebird instead of IE and am moderately sensible, the chances of my system being hacked are pretty minimal.

    --
    You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
  105. Re:Hah! by AndreyF · · Score: 1

    that i can agree with. but linux is moving towards there also.