Slashdot Mirror


Gentoo rsync Server Compromised [updated]

costela writes "LWN points out that the Gentoo project fired out an alert about one compromised rsync server." From the message itself: "However, the compromised system had both an IDS and a file integrity checker installed and we have a very detailed forensic trail of what happened once the box was breached, so we are reasonably confident that the portage tree stored on that box was unaffected." Update: 12/03 22:54 GMT by T : One more damage report: gibson writes "The Free Software Foundation recently discovered that its software host site was compromised a month ago. The compromise appears to be the same as the recent attacks on the Debian servers. The site is shut down until Friday while they install replacement hardware and verify the authenticity of the hosted source code."

600 comments

  1. The only reason this is news... by An0maly · · Score: 0, Insightful

    The infrequency of linux/unix box break-ins is what makes this newsworthy. we all know that for every 1 linux/unix box that is compromised, there are a whole slew of windows machines.

    --
    "...if you don't like your job, you don't strike. You just go in every day and do it really half-assed..." -Homer
    1. Re:The only reason this is news... by gosand · · Score: 0, Offtopic
      "If you hate your job you don't quit. Just get in there every day and do it really half-assed." -Homer Simpson

      Yeah yeah, offtopic. But you have to fix your sig man. If you are going to quote, get it right. You are way off - it is "Lisa, if you don't like your job, you don't strike. You just go in every day and do it really half-assed. That's the American way."

      --

      My beliefs do not require that you agree with them.

    2. Re:The only reason this is news... by Anonymous Coward · · Score: 1, Insightful

      Wow. A post even a Linux zealot would blush at. Of course one could argue that there is a whole slew more Windows machines to be broken into. Either way your post is really scary.

    3. Re:The only reason this is news... by An0maly · · Score: 1

      Thank you sir. I am corrected. I shot what I had off from memory and I guess there was some data loss in the neural decoding process. Props on catching that and actually knowing the real quote tho. =)

      --
      "...if you don't like your job, you don't strike. You just go in every day and do it really half-assed..." -Homer
    4. Re:The only reason this is news... by Smallpond · · Score: 1, Interesting

      Infrequency?

      Get your facts right:
      "Linux is successfully compromised more than any other operating system". Mostly due to people setting it up straight out of the red box without adequately Reading The Fine Manual.

    5. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      If thats the case then why is it news everytime the miserable failure these people are rooting for grows a beard.

    6. Re:The only reason this is news... by kayen_telva · · Score: 5, Insightful

      no, its news because a very popular linux dist has been hacked which could effect a lot of people. that = news

      damn microsoft bashing wannabee

    7. Re:The only reason this is news... by An0maly · · Score: 0

      In any case, the faulty code that allowed the attack was obiously stolen from SCO. Yeah. that's it. It was SCO's shitty deprecated code!

      --
      "...if you don't like your job, you don't strike. You just go in every day and do it really half-assed..." -Homer
    8. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Wrong, it could affect 20 people. The exploit itself is unknown to the public and more than likely has nothing to do with Gentoo itself.

    9. Re:The only reason this is news... by NialScorva · · Score: 2, Insightful

      also because there's something there to comprimise. If I crack gramma's win98 machine, there's not a lot I can do with it except use it as a relay to attack spamhause.

      Do worms count as a comprimise? I can't see any possible way that you couldn't count them, and I can't see any possible way that linux would have more comprimises in a year than any of the latest worms would generate in a month.

    10. Re:The only reason this is news... by An0maly · · Score: 1

      That's exactly what I was getting at. How many times has MS patched RPC now? IIS? I lost count.

      --
      "...if you don't like your job, you don't strike. You just go in every day and do it really half-assed..." -Homer
    11. Re:The only reason this is news... by Trigun · · Score: 1

      Because he didn't grow one like this!

    12. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      What you were getting at and what you posted are two different things unfortunately. Nice way to backtrack though.

    13. Re:The only reason this is news... by simcop2387 · · Score: 1, Interesting

      you could also RTFA that you posted a link to

      We don't know how many total servers the numbers were gathered from or what percentage of those servers is Linux vs. Windows, etc. It is safe to say that these results are true for the servers they monitor, but the percentages may not be true for all servers across the globe. For more statistics and the rest of the story you can see this article at globetechnology.com: Linux is favourite hacker target: Study.

      as the article states the statistics are not conclusive because they cannot be confirmed because the data of the actual study is not presented.

      they also do not define was is meant by compromising, as far as i can tell it could be anything from a remote root exploit, or a setup in a mail server that creates an open spam relay

    14. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Since there are far Windows servers than Linux servers I would think that there is still plentry to compromise. Just on webservers alone it is like 50% to 29% in favor of Windows (notice I say Windows and not IIS and servers not sites). Add to that exchange and MSSQL servers, file servers, application servers, etc. and you have a lot of fun stuff to compromise.

      Compromising grandma's Win98 machine is also how DDoS attacks work.

    15. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Yeah, Linux is the most frequently "Successfully Compromized" operating system. Mostly due to a definition of "Successfully Compromized" that does not include installation of a trojan horse, spyware, or virus by a legitimate user, or self-propogating code infecting the host without being directed to do so by it's creator.

    16. Re:The only reason this is news... by An0maly · · Score: 0, Flamebait

      Well excuse me Mr. Prissy-pants. Forgive me for insulting you with my comments. I'll FTP you a dollar for your troubles of showing me the error of my ways. =P

      --
      "...if you don't like your job, you don't strike. You just go in every day and do it really half-assed..." -Homer
    17. Re:The only reason this is news... by mahdi13 · · Score: 5, Informative

      Only 20 people sync'd with this server within that hour it was compromised...not a big deal, expecially when the compromise did not touch the portage tree and was mearly a rootkit install and some logs edited...not to mention it is a donated server used for other purposes, the attacker might not of even known it was used for Gentoo rsync...
      But the server is down and will be scrubbed and re-sync'd, just to be safe

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    18. Re:The only reason this is news... by htmlboy · · Score: 5, Insightful
      Get your facts right:
      "Linux is successfully compromised more than any other operating system". Mostly due to people setting it up straight out of the red box without adequately Reading The Fine Manual.

      facts are tricky like that:
      "We don't know how many total servers the numbers were gathered from or what percentage of those servers is Linux vs. Windows, etc. It is safe to say that these results are true for the servers they monitor, but the percentages may not be true for all servers across the globe."

      while there certainly exist a large number of linux machines that have been compromised, i can't imagine the number of infected linux machines is anywhere near that of the win32 systems infected by blaster/welchia/code red/nimda/sql slammer/klez/dumaru/sobig/etc. in the same time frame. i suppose the counting in this case depends quite a bit on the counter's definition of "compromised."
    19. Re:The only reason this is news... by LurkerXXX · · Score: 1
      Just the kind of idiotic zealotry that would requires someone to post as an anonymous coward. No one said the exploit has anything to do with Gentoo itself. The problem is a lot of folks us that mirror to set up their own machines. Way more than 20 people could now have compromised machines if they got into the portage tree.

      Mirrors being exploited IS news. Keep it quiet and lots of folks could end up with rooted boxes and be none the wiser. Ignoring it is stupid.

    20. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Doubly wrong because the compromised system may not even have been running any flavor of Linux. Gentoo has declined to identify the system at the request of the system sponsor... and if it's like lots of mirror systems it will have lots of stuff on it that could have been the target besides Gentoo itself.

      It's not like Gentoo itself was compromised according to the report. Nor does there even seem to be any concern the Gentoo files on this mirror were affected either (which would be easy to check with md5 sums from a trusted host), so even the 20 whole users who rsynced against the system when it was compromised don't appear to be in any danger.

    21. Re:The only reason this is news... by damballah · · Score: 1
      Or maybe because less than 2 weeks ago, the Debian servers were broken into. Linux seems to be gaining popularity in being the target for crackers.

      Who will be next? :) (not that I'm looking forward to it).

    22. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      uh, didn't the email say that the portage tree wasn't comprimsed. way to read the article before tossing in your two cents slick.

    23. Re:The only reason this is news... by Stephan+Schulz · · Score: 4, Informative
      Do worms count as a comprimise? I can't see any possible way that you couldn't count them, and I can't see any possible way that linux would have more comprimises in a year than any of the latest worms would generate in a month.
      The study referenced above is from mi2g, a company that is known for reports that overstate risk and damage (hey, they sell security services), and is not considered a particularly good source. Moreover, they counted only attacks on servers (without a clear definition of what a server is) and only "successful and verifiable" attacks. How they got those numbers again is not explained in any of the online articles, and neither is what constitutes an attack (A ping? A portscan? A DOS attack? Or a remote root exploit?).

      So anyways, they did not count (most) worm incidents, as they would happen on non-server windows machines.

      That does not mean that Linux boxen should not have better default security settings, of course.

      --

      Stephan

    24. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      This is a huge problem since all operating systems were derived from SCO's codebase. This is bigger than y2k!

      -------
      Hey Cowboy, /. requires a two minute gap between posting so editors can bitchslap all content they don't like. You've only given them a 1 minute head start, you bastard.

    25. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Yeah, read the article. It flat out says that about 20 people used that mirror between the time it was comprimised and the time it was taken down. Not only that, but as noted the mirror itself isn't comprimised and they don't say what exactly was. You are correct, the machine was not Gentoo's box so there really isn't any reason to be tin foil hat worrying about it. This isn't news since it really didn't affect any Gentoo users.

      Read the article before you say the word zealot, anti-zealot zealot. And for that I will post this as anon too.

    26. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      As well, this isn't "just another exploit for Explorer/Windows/Linux/whatever," this is someone gaining access to THE source code server. I don't seem to recall too many stories where MS had their main code repository compromised, do you?

      That's what I thought.

    27. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      for every 1 linux/unix box, there are a whole slew of windows machines. your statement is greatly flawed. you should use ratios rather than raw numbers. using your statistical genius you could claim DOS to be more secure than all of them since it is quite rare to hear about a DOS machine being breached.

    28. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      My serious hope is this speeds up gpg signing of everything. The key holders should then firewall off their machines, use a key chain for their key, etc.

    29. Re:The only reason this is news... by Hobophile · · Score: 1
    30. Re:The only reason this is news... by MntlChaos · · Score: 1

      this was a mirror that was taken down within an hour of the compromise. only 20 people were affected. They would have published details to let those people fix their boxes if the tree WAS affected.

    31. Re:The only reason this is news... by Rodrin · · Score: 2, Informative

      The server wasn't actually running Gentoo Linux from what I have read.

    32. Re:The only reason this is news... by Blkdeath · · Score: 5, Insightful
      As well, this isn't "just another exploit for Explorer/Windows/Linux/whatever," this is someone gaining access to THE source code server. I don't seem to recall too many stories where MS had their main code repository compromised, do you?

      Since Gentoo doesn't have a "THE" source code repository, I'm afraid you've got some facts to get straight, Herr Coward.

      The mirror had read-only rsync access to Gentoo's primary (US) mirror. Even if the tree were compromised, the changes could not propagate into the main tree. For that, one would require CVS access to the CVS repository, against which the primary rsync server is synchronized.

      This was only posted as a matter of keeping our user community, and the OSS community as a whole informed.

      Also, I believe the announcement gave mention of it, but the Portage tree on the primary mirror was re-created from the CVS repository immediately upon being notified that a mirror was compromised. Within 30 minutes, every Gentoo rsync mirror had a fresh copy of the tree automatically (as stated by Gentoo rsync mirror policy, mirrors are updated every 30 minutes in order to remain on the official rotation).

      Sorry for the confusion, all, but there's really nothing to see here. But it was good clamouring practise for when/if a real Gentoo server is compromised. ;)

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    33. Re:The only reason this is news... by LurkerXXX · · Score: 1

      Notice I said "could have" and "if". I had read the article and knew those facts. I was just stating that it IS news when a machine like this gets compromised. Luckily the admins found and fixed it quickly in this case. It easily could have been much much worse. There are still at least 20 folks out there who needed to know it happened tho (and anyone they may have passed on files to). I was saying that this IS news, and a good warning to others to keep monitoring tripwire or whatever else they are using to keep tabs on their system. Especially if the machine is used as a mirror.

    34. Re:The only reason this is news... by Anonymous Coward · · Score: 0
      Only 20 people sync'd with this server within that hour it was compromised...not a big deal

      Not a big deal? Isn't that about 40% of the Gentoo userbase?

    35. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      I smell a rat, first gnu.org get's compromised, then Debian, and now Gentoo?
      Anyone else find these attacks against Free Software distributors disturbing?
      If I was paranoid I'd think that the same pack that funds SCO's war on the GPL and the Free Software movement, are paying corporate blackhats to attack important free software distributors in order to make free/open source software seem less secure.

    36. Re:The only reason this is news... by fastidious+edward · · Score: 2

      "...not a big deal..." because only 20 people used the server in an hour.

      but there is the possibility it could have happened to a server with much more throughput. That is worrying. Dismissing this as not a big deal is a slack attitude to security, be it a part-time server or not.

      --

      karma karma karma karma karma chameleon, you come and go, you come and go.
    37. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Really? How does a windows machine being compromised effect me? Unless they get windows.update, I am not concerned at all. On the other hand, I am in deep trouble if my Debian box updates from a rooted server. Likewise if I was running Gentoo, which I never will because they seem to have cornered the market on obnoxious linux zealots. Thanks for your redirection attempt though.

    38. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      The mi2g site indicated before that this was "interactive" intrusions, and did NOT include worms and viruses.... When you take those into account, how do you think the numbers fall? :-)

    39. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      i can't imagine the number of infected linux machines is anywhere near that of the win32 systems infected

      That's only because 1 out of every 800,000 or so computer users run linux. Nice FUD, fanboi.

    40. Re:The only reason this is news... by You're+All+Wrong · · Score: 1

      "
      Moreover, they counted only attacks on servers (without a clear definition of what a server is)
      "

      A server is anything with an open port accepting requests from the outside world.

      Quite how Win98 boxes can serve files, and with IIS can serve web-pages, without being classified as servers is beyond me.

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    41. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      wow, this sure is a childish thread compared to the "Debian.org project servers compromised" thread.

    42. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Or in a day.

    43. Re:The only reason this is news... by AVee · · Score: 1

      Linux seems to be gaining popularity in being the target for crackers.

      The question is, why? The optimistic answer is that as Linux box is way more usefull ;-)
      What worries me is that machines used for distibuting sourcecode are being attacked, with some succes. We whould have a hell of a problem if someone messes with widely used source and it goes unnoticed. This proves the need for peer review and does not, in any way put closed source system in a better position, but it will be very important to be on very alert.

      The guy's running that server did a hell of a job finding it in one hour. Kuddos to them, whoever they may be.

    44. Re:The only reason this is news... by AVee · · Score: 3, Insightful

      Really? How does a windows machine being compromised effect me?

      Ever looked at the amount of incomming traffic when you're online? Ever considered where the amount of you are getting is mainly comming from?
      Unless they get windows.update, I am not concerned at all.

      Well, start worring right now. How big do you consider the chance that your vendor tells you about that? They don't even tell you about problem in your OS they know about for months before some exploit is published in the wild.

      I do share your concern about trusting the source of your software, but even with these compromises i'd trust Debian and Gentoo more that a big company that has a huge interest in hiding problems like that.
      There is no solution to this problem, other then writing all your software yourself. The thing that comes the closed to that, while being still practical, is and open development model where a lot of people are reviewing the source for mistakes and/or malware.

    45. Re:The only reason this is news... by damballah · · Score: 1
      machines used for distibuting sourcecode are being attacked, with some succes.

      You probably know by now that Savanah has been broken into, and they only learned about it 1 month after. It's even worse, since this is where some important software is being actively developped. This is not good at all. And of course, you cannot propose that they make access to the source restricted, since GNU's purpose is to provide free software...

    46. Re:The only reason this is news... by Anonymous Coward · · Score: 1, Funny

      That's good product endorsement. "Our product is great! No, we don't actually use it."

    47. Re:The only reason this is news... by Anonymous Coward · · Score: 0

      Perhaps he's thinking of Savannah as THE main source code repository.

    48. Re:The only reason this is news... by mahdi13 · · Score: 1
      Read the rest of the damn post...
      expecially when the compromise did not touch the portage tree and was mearly a rootkit install and some logs edited
      Slack security or not, it didn't affect the tree, It was caught within an hour of compomise and taken off-line...how the hell can this be considered "slack attitude to security"??! RTFA
      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    49. Re:The only reason this is news... by fastidious+edward · · Score: 1

      Thanks, I did RTFA and was responding to the comment it was not a big deal - it was and the server was thus taken offline, but think, just for a moment, that if this was possible it could be possible on other computers (until we know for sure otherwise)... so how about all those other computers, is it not a big deal for how many other computers were also using that config? Couple this with the recent news of a malicious program obtaining root on another distro and hell I don't care about the portage tree I care about machines already configured being exploited - maybe there will be more in the future too?

      "...it didn't affect the tree" no, it affected the computer so the computer is exploitable... why was it exploitable and how many others are exploitable too?

      --

      karma karma karma karma karma chameleon, you come and go, you come and go.
    50. Re:The only reason this is news... by mahdi13 · · Score: 1
      I do agree with you, the "not a big deal" was the wrong wording (why else was the server taken down?)
      why was it exploitable and how many others are exploitable too?
      That is the real question...there was no specifics released about what the server was, what it was running, if it's been patched...only that it was compromised. Hopefully when they discover what did happen they will let everyone know
      --
      "Some things have to be believed to be seen." - Ralph Hodgson
  2. well... by neo8750 · · Score: 5, Insightful

    who didn't see this coming? I use gentoo and i figured it was a matter of time before someone did this. I mean haveing a central tree is cool but it does make it more of a target for attacks. I am however glad to see that they took precautions.

    1. Re:well... by ballyn · · Score: 5, Insightful

      Luckily this "central tree" is actually a distributed mirror, so a simple emerge sync will get your portage tree back in shape if you're one of 20 or so people who happened to sync to this server after it was compromised...

    2. Re:well... by frodo+from+middle+ea · · Score: 1
      I was under the impression , that the rsync servers were mirrored , and you are supposed to use the one nearest to you.

      Although I am not sure how they sync between themselves. i.e. Would compromizing one lead to compromising the others as well ?

      --
      for the last time people, I am "frodo from middle eaRTH", not "middle eaST".
    3. Re:well... by Anonymous Coward · · Score: 0

      haveing

      Are you sure you don't mean "havening" ??

    4. Re:well... by Anonymous Coward · · Score: 5, Interesting

      And what if syncing to the server installed a compromised "emerge" program?

    5. Re:well... by KentoNET · · Score: 2, Insightful

      The rsync servers are, indeed, mirrors. The mirrors are load balanced through the use of a DNS round robin. The cvs.gentoo.org machine propagates the portage tree throughout the rotational rsync mirrors, so any portage tree attack would need to be taken either on most of the rsync mirrors or on the cvs machine. This single attack (had anything actually happened) only affected 20 users.

      --
      "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    6. Re:well... by Theatetus · · Score: 4, Insightful

      Somebody mod that tinfoil-hat-wearing parent post up.

      Download gentoolkit and emerge from a current server and validate the checksum. Manually build them. Then emerge sync. Then emerge -u world. Anything less is just trusting that the attackers couldn't cover their tracks well.

      --
      All's true that is mistrusted
    7. Re:well... by RedHat+Rocky · · Score: 3, Informative

      The rsync servers sync with...rsync!

      So, yes, changes in the source rsync tree would trickle down to all the mirrors. It wouldn't actually compromise those servers, in the root-on-the-box sense, but they would be serving compromised data.

      --
      Anything is possible given time and money.
    8. Re:well... by Anonymous Coward · · Score: 0

      (posting AC becuase i done have an account)
      The compromised server was /not/ the master server, so the only affected people were the ones to use that particular server during the hour it was compromised.

      If the master tree server was compromised, the backdoor/whatever would indeed be propogated to every mirror in half an hour..

    9. Re:well... by Anonymous Coward · · Score: 1, Insightful

      If you still have your ebuilds and distfiles handy, then you don't need to do a full-blown emerge -u world. That's a pure waste of time if the md5 checksums from both the .ebuild and .tar.(g|b)z2* files match those of authoritative files. Given the correct ebuilds and tarballs you can assume that your system probably built the correct binaries. If you find a faulty ebuild or tarball, it would make sense to investigate that first before doing an emerge -u world, anyway. If your gcc were compromised, using it to do an emerge -u world would be an exercise in futility if the goal were to clean a system.

    10. Re:well... by unixbob · · Score: 4, Interesting

      Even if you didn't RTFA, at least RTFP.

      However, the compromised system had both an IDS and a file integrity checker installed

      The file integrity checker will have provided a list of the files that changed and if emerge was compromised then Gentoo would have let you know. After all, they haven't kept the compromise quiet so presumably they are informing users to let them know the Gentoo are on top of things.

      --
      The Romans didn't find algebra very challenging, because X was always 10
    11. Re:well... by Amgine007 · · Score: 3, Interesting

      And who doesn't see this coming again? All you need is a box with some bandwidth, and you can become a gentoo mirror.

      Now, you want to compromise every gentoo box on the planet? Edit any ebuild you want to add your compromise. Make it break out of the gentoo sandbox and erase that system straight from the ebuild. Or make it install a tainted binary. Whatever, just be sure to re-hash your ebuild in the Manifest, and wait for some poor suckers to download it. Given the frequency with which gentooer's rsync, this should happen very quickly.

      There is abosolutely _ZERO_TRUST_ in the gentoo system, and it is frightening how easily a rsync mirror could abuse whatever clout it has to taint a significant number of hosts.

      The solution for this is signed digests and shared trusted gentoo keys, but this is still a ways off.

    12. Re:well... by dotgain · · Score: 1
      >There is abosolutely _ZERO_TRUST_ in the gentoo system

      Don't you mean "total trust" in the system, in that the users "trust" the rsync servers not to be r00t3d, somewhat optimistically?

      Before you hit me with a flamebait, _I_ have actually been one of those people, trusting whatever rsync server I hit, and this has been an eye-opener for me.

    13. Re:well... by bn557 · · Score: 1

      one thing people forget to mention is that this wasn't JUST a gentoo mirror. They havn't disclosed what else the server was used for. There is an announcement on the gentoo forums about it. HERE

      P

      --
      Humans are slow, innaccurate, and brilliant; computers are fast, acurrate, and dumb; together they are unbeatable
    14. Re:well... by Amgine007 · · Score: 2, Interesting

      >> There is abosolutely _ZERO_TRUST_ in the gentoo
      >> system
      > Don't you mean "total trust" in the system, in that the
      > users "trust" the rsync servers not to be r00t3d,
      > somewhat optimistically?

      Doh! But yes, that's what I meant in my somewhat hasty response. (I have been thinking about gentoo and this for a while.)

      Gentoo would be ideal with a web of trust, such that a gentoo deployment maintained keys that it trusted -- ie, from gentoo, from developers, from friends, etc, and accepted and rejected ebuilds accordingly. Considering the development distribution of gentoo, it is almost a case study in how to build and use a mini public key infrastructure.

      The whole gentoo tree could be viewed as as many 'virtual' trees as you desire, by multiple signatures on single or multiple ebuilds: for example, instead of setting "~x86" (experimental x86 ebuild) from within the ebuild, why not sign the ebuild with the gentoo_experimental_x86 key? Then, sign it with a "testing" or "stable" key as it fits.

      With keys from developers (gpg message signing is already a big habit on gentoo-dev), you can accept patches from developers and other people you trust, even if you receive the ebuild out of band (eg, on bugzilla). All of this also removes the posibility of, say, an errant CVS commit. Now all you trust is those public keys (and however many signatures you require on an ebuild to believe it wasn't porrly signed.)

      (Of course, verifying signatures adds more complexity to the build time, but... this is gentoo! You love the build time!)

      cheers.. (a gentoo user)

    15. Re:well... by Blkdeath · · Score: 2, Informative
      And what if syncing to the server installed a compromised "emerge" program?

      Because, save for an attacker compromising all Gentoo workstations and altering the Portage application itself, this is not plausible. `emerge sync` updates only the tree of ebuilds - text file application install scripts, analagous to Makefiles. The process is quite similar to BSD's `cvsup` process. The only files modified in this process are contained in /usr/portage/ (or another location optionally configured by the user). The `emerge` program itself is contained in /usr/bin, and is not touched by the rsync process.

      Sorry to tear that nasty gash in your tin-foil hat, though.

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    16. Re:well... by Anonymous Coward · · Score: 0

      The file integrity checker will have provided a list of the files that changed...

      Well, yes, unless they also *compromised the file integrity checker*. And yet you have the nerve to tell someone that they should RTFA.

      Perhaps you should FT. (Hint: T=Think)

    17. Re:well... by yosemite · · Score: 2, Funny

      Well what if they comprimised the file integrity checker *checker*? or the backup file integrity checker checker *checker*. Or what if they hacked the matrix and made you stupid.

    18. Re:well... by NineNine · · Score: 1

      Download gentoolkit and emerge from a current server and validate the checksum. Manually build them. Then emerge sync. Then emerge -u world. Anything less is just trusting that the attackers couldn't cover their tracks well.


      That's great. How about instructions on how to do all of this?

    19. Re:well... by Xabraxas · · Score: 2, Interesting
      Edit any ebuild you want to add your compromise. Make it break out of the gentoo sandbox and erase that system straight from the ebuild. Or make it install a tainted binary.

      You make it sound so easy. Just "break out" of the sandbox and erase the system. No system is ever going to be 100% secure, but things like sandboxing make it safer. I'll take my chances with Gentoo. The RPC exploits alone have convinced me to never even look at a Windows box again. It's just too much hassle.

      --
      Time makes more converts than reason
    20. Re:well... by Anonymous Coward · · Score: 0

      How about if you ignore it, since the advice is pretty worthless to begin with? Gentoolkit can't verify your existing binaries since, in theory, they would be unique to your system depending on your configuration. And the remaining steps listed are meaningless if your system has been compromised. I already pointed out that the only thing you really can do in this situation is trust Gentoo that none of the mirror files were affected. And if you just emerge sync'ed your tree against the compromised mirror, you probably also just ran an emerge -u world, which would have updated x number of files (where x>=0)... in which case you are likely to still have the tarballs in /usr/portage/distfiles. Check your emerge log in /var/log/emerge.log to see which packages you updated, if any. Verify the ebuild files and distfile tarballs for those files against some other source that you trust. If they match, fine. Nothing to see. If they don't match, you have a lot of work to do either cleaning your system or reinstalling (both of which are beyond the scope of a Slashdot post).

    21. Re:well... by You're+All+Wrong · · Score: 1

      "Download ... validate the checksum ... build"

      How do you know the the program that does the downloading isn't now hacked? How do you know the thing that validates the checksum isn't now hacked? How do you know the thing that does the compiling isn't now hacked?

      You've just asked the computer owner to run at least three programs whose state is unknown, and therefore ought to considered insecure.

      If you've run _any_ code downloaded from a compromised server, then your entire system state is potentially unknown. Unless you're prepared to pretend that local root exploits don't exist.

      Boot from a read-only floppy and don't touch _any_ executable or library on your hard disk until you've checksummed it with the md5sum off another read-only floppy. Preferably use something like tripwire that again runs off a read-only floppy. If you do anything else you don't know exactly what you're running.

      And who said the floppy was dead?

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    22. Re:well... by FxChiP · · Score: 3, Informative

      ... No modding up necessary.

      emerge sync doesn't touch emerge. Basically, all emerge sync does is get a listing of the Portage tree and fetch the latest ebuilds, and delete whatever is old. The only thing emerge sync does in relation to emerge itself is tell you that a new version is available if there is one.

    23. Re:well... by Amgine007 · · Score: 1

      > You make it sound so easy. Just "break out" of the
      > sandbox and erase the system.

      There are any number of ways to cause harm from within an ebuild. Perhaps I was misleading; you can "break out" by using legal ebuild syntax. Eg, "insinto /etc", and the "doins shadow". Someone might notice the install log, but who cares? This attack targets joe rsync'r, who must update world daily. Replace /bin/bash if you want -- nothing will stop your trojaned x11-themes package. Ok?

      > No system is ever going to be 100% secure, but things
      > like sandboxing make it safer.

      Sandboxing was not at all the point.

      The point was that Gentoo is built around distributing esentially shell scripts over rsync -- and at present these can easily be modified by a compromised or malicious mirror and cause GREAT harm. A hash of the ebuild is rsync'd WITH the ebuild from the SAME source! Simple integrity check? Yes. Proof that the Manifest, or anything in it, is the same as Gentoo intends it? Absolutely not. The fact that this would be so easy to exploit is surprising.

      By the way, sandboxing in Gentoo is protect build scripts outside of the ebuild from installing things where they shouldn't be.

      cat /usr/bin/emerge

      Portage itself is mostly a few python modules. Modify the emerge program to delete a few files, then package it back up and put it (with a new manifest) on your rsync mirror. You don't even need to know how to use gcc.

    24. Re:well... by Anonymous Coward · · Score: 0

      That's great. How about instructions on how to do all of this?

      If you have to ask, you shouldn't be running Gentoo. Sorry, but it's true.

    25. Re:well... by John+Hurliman · · Score: 1

      Ebuilds can point anywhere on the web to binaries, the attacker could have changed the portage ebuild to point to a malicious emerge binary. It would have said "there is a portage update available" and would recommend downloading it immediately. Of course if this happened the Gentoo folks would have made a note of it, but it's not an implausible situation.

    26. Re:well... by unixbob · · Score: 2, Insightful

      So they compromised the server, cleared down some of the logs, but weren't able to completely hide the intrusion, but still managed to compromise the file integrity checker and the source code for emerge?

      This being the same file integrtity checker that alerted the sys admins to the compromise in the first place? If you are good enough to compromise Tripwire or AIDE or whatever then you are good enough to hide the fact that you have done it, not remove some logs install a rootkit then get found out by the IDS.

      Perhaps you should FT

      --
      The Romans didn't find algebra very challenging, because X was always 10
    27. Re:well... by warrax_666 · · Score: 1
      A hash of the ebuild is rsync'd WITH the ebuild from the SAME source! Simple integrity check? Yes. Proof that the Manifest, or anything in it, is the same as Gentoo intends it? Absolutely not.

      I was actually thinking about this the other day, and it seems very strange that the Gentoo people haven't realized that they could enhance the security greatly by simply rsync'ing from two different servers. The ebuilds are fecthed from the first server, and the manifests/digests are fetched from another server. This would greatly diminish the risk of a rooted mirror being used to sneak in trojans, etc.

      Hmm, maybe I should file a bug report...?

      --
      HAND.
    28. Re:well... by Anonymous Coward · · Score: 0

      that is, unless your bios was overwritten. real paranoid people cut their Write Enable (WE) line to their bios chips so they can't be reflashed without reconnecting. :) *tinfoil hat*

    29. Re:well... by Sevn · · Score: 1

      More importantly, if you are that good you probably aren't the kind of piece of shit that would hack a server and get caught so easily. You'd probably have things like a life and a job. I'd bet cash this was more of those index.* replacers that seem to think they are special because they can make a posting to zone-h. They had no idea it was a gentoo rsync server at all is my guess.

      --
      For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
    30. Re:well... by heikkile · · Score: 1
      That's a pure waste of time if the md5 checksums from both the .ebuild and .tar.(g|b)z2* files match those of authoritative files.

      Yes, if you can trust your md5 sums! What if a compriomized emerge first modified your md5sum to display values from a hard-coded list for those packages it has modified? It is hard to know what you really can trust.

      Luckily everything indicates that this is just empty speculation. But what about the next time something gets compromized?

      --

      In Murphy We Turst

    31. Re:well... by Random+Walk · · Score: 1

      Depends on the file integrity checker. E.g. with samhain, you can have the baseline database on a remote server. So you can just re-install the client, and run a check against the baseline that the client will retrieve from the server.

    32. Re:well... by Rich0 · · Score: 1

      Actually, verifying emerge itself is trivial - it is a python script. Hardly platform-dependent...

      Merely syncing against a server just updates the portage tree - not any binaries on the system. You would have had to have used a modified ebuild file to actually get something active on your system.

    33. Re:well... by Rich0 · · Score: 1

      As has already been pointed out - the server in question didn't host ANY binaries. When you sync up using emerge rsync it just downloads a list of packages and how to build each one.

      To compromise a binary on your system you'd have to emerge sync with a compromised server, and then use emerge to actually build a package which was compromised with a trojan of some sort.

      In any case, they were running an IDS and some sort of tripwire system on the server, and so we know everything is safe...

    34. Re:well... by Rich0 · · Score: 1

      Uh - I don't know about you, but if I were running a professional site I'd be running tripwire once a day and saving my checksums for a month at least.

      If there were any sign I'd been hacked then I'd:

      1. Shutdown the server.
      2. Boot from a rescue floppy/CD (so now you're in a known clean state.
      3. Mount the drives on the server and run tripwire FROM THE CD against the most recent checksums before the intrusion FROM THE CD.

      Viola - you now know with certainty each file that has been modified.

      It isn't like the methods of good systemadministration are a closely-held state-secret or anything. I'm sure somebody hosting an rsync peer would follow them...

    35. Re:well... by Rich0 · · Score: 3, Insightful

      Uh - have you read the recent linux weekly news which praises the gentoo community for their unusually high level of support?

      I hate to respond to such a silly flame - but this is really unfounded.

      The parent's attitude hardly reflects that of most people running gentoo. A simple browse of the gentoo forums would demonstrate this.

      How exactly is gentoo harming linux anyway? Because some idiot compromises a server? A server whose admins apparently knew what they were doing and had it offline within an hour? Whose admins were thoughtful enough to have significant IDS capabilities installed so they can verify that the whole portage tree is still intact? Last time I checked, the FSF wasn't able to do that in a few hours, and I'd hardly argue that they're doing linux a disservice!

    36. Re:well... by Anonymous Coward · · Score: 0

      Right. But I assume the main reason to do an emerge sync is so that you can run emerge -u world. Otherwise what's the point in keeping your portage tree synced up? So. 1) Check for changed ebuilds. 2) Check if any changed ebuilds were used to build binaries. 3) If not, fine, delete the bad ebuild and resync. If so, more work is necessary to understand the impact of having a compromised binary on the system.

    37. Re:well... by You're+All+Wrong · · Score: 0, Flamebait

      "it just downloads a list of packages and how to build each one."

      Oh, OK, that method guarantees that compromised binaries won't get onto your system. No chance that the list of packages would be altered to point to compromised ones, and no chance that the instructions how to build them might involve underhand actions. Sure, sure, all's rosy.

      NOT!

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    38. Re:well... by Blkdeath · · Score: 1
      Ebuilds can point anywhere on the web to binaries, the attacker could have changed the portage ebuild to point to a malicious emerge binary. It would have said "there is a portage update available" and would recommend downloading it immediately. Of course if this happened the Gentoo folks would have made a note of it, but it's not an implausible situation.

      Ok; assuming our attacker is thorough, he's compromised an rsync server. He's got a trojanned version of Portage on ice. He also knows how to use our development tools so he's created new digest and Manifest files correctly. He uploaded these three files to the rsync server, and there's a 30 minute window during which time some people on that particular national rsync rotation could possibly sync and retreive the false copy before the tree is automatically re-synced with the master. After this, there is a minute chance that someone will upgrade (a) package(s) which could pull in the trojan. (Note that except in severe cases, the user must specify one of -u(pgrade) or -U(pgrade only) to pull in dependancies - including Portage)

      So we have a breech that could have, in an extreme hypothetical situation, caused a percentage of 20 people to become trojanned out of our ~300k userbase.

      That's a lot of time and trouble to (possibly) affect so few people. If someone were intending to do damage to the Gentoo community, they'd have been wiser to attack rsync1.us.gentoo.org or cvs.gentoo.org and pollute one of those trees. In all likelyhood this attacker was merely a script kiddie looking to r00t lots of machines to have a place to play, or possibly a Mitnick-esque type looking for a drop-point for files, but most likely a person attacking for a reason completely un-related to Gentoo.

      You have to keep in mind that the rsync mirrors are provided by volunteers. I have enough bandwidth at home and at work that I could set up two myself.

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    39. Re:well... by Anonymous Coward · · Score: 0

      And of course, it's not possible they wanted to get caught, right?

      So, root the server, compromise the file checker, compromise emerge, and then you root those 20 boxes that synched up. Get caught, have Gentoo declare, "Nope, no damage for you guys" and then have your way with those boxes.

      A talented cracker could have been sniffing some packets, and noticed scripted syncing. Maybe his actual target wasn't using the round robin DNS, but this specific server for convenience, or speed, or whatever. So, if you can't crack your actual target, crack the server it syncs against, drop some dumbass script kiddie evidence, and then go on your way.

      Who knows? Is it implausable? Sure. Is it *impossible*?

      Well, no. And that's the point. You're making assumptions, and while you'll get away with it most of the time, it can get you hurt in the long run. If that's the sort of thing you like, go ahead, keep doing that.

      Oh, I have a local file integrity checker! I'm bulletproof!

      Yeah, replace "file integrity checker" with "firewall" and see how seriously you get taken. Or hell, replace "file integrity checker" with *anything*. Nothing makes you perfectly safe. If your box gets compromised, even in the slightest way, everything on it is suspect . Anything less, and you're being retarded.

      (jackass)

    40. Re:well... by You're+All+Wrong · · Score: 1

      Score:0, Flamebait

      Having your head in the sand doesn't make you more elite.

      Grow up.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    41. Re:well... by alexpage · · Score: 1

      Now, now. Gentoo keeps the hardcore weenie crowd away from other distributions, which give those other distros more credibility :)

  3. All this bad news. by iantri · · Score: 4, Interesting
    Lately there has been a lot of bad news about Linux.. SCO, Red Hat's discontinuing of the Red Hat Linux line, the Debian server compromise.. now this.

    A conspiracy theorist could have a field day..

    Now where did I put my tin-foil hat?

    1. Re:All this bad news. by Anonymous Coward · · Score: 0

      Yeah, I'm kinda surprised no one's started foaming at the mouth yet about how the Bush administration is conspiring to destroy all of Linux.

    2. Re:All this bad news. by bytesmythe · · Score: 4, Interesting
      Don't forget when gnu's servers were compromised a few months back...

      A conspiracy theorist could have a field day..

      Is it sad the first thing that crossed my mind was "lots of well-timed security breaches... Microsoft may be behind them all"? ;)

      --
      bytesmythe
      Hypocrisy is the resin that holds the plywood of society together.
      -- Scott Meyer
    3. Re:All this bad news. by ChesireKat · · Score: 2, Interesting

      Perhaps I'm wrong, but I believe you have no IDEA what you are talking about. There has been no more bad news than normal about linux. Again, perhaps I'm wrong, I'm always open to other's opinions. There always has been, and always will be, bad news about linux. Just like windows. And Macs, too for that matter. It's totally offtopic.

      Also, what does SCO have to do with the Debian Server compromise? those are two TOTALLY different subjects. You can't group them all in the same "bad news" categories! One has to do with security, the other with the corporate-world. Again, totally offtopic!

      --
      ~Just keep eating, porky. Fat people are harder to kidnap.
    4. Re:All this bad news. by iantri · · Score: 3, Insightful
      Also, what does SCO have to do with the Debian Server compromise? those are two TOTALLY different subjects. You can't group them all in the same "bad news" categories! One has to do with security, the other with the corporate-world.

      Yes, I can. Both give Linux a negative image to people that aren't as clued in about this sort of thing, which is were Linux needs the most support.

    5. Re:All this bad news. by penguin+king · · Score: 5, Funny

      Yeah... it was probably SCO: "ooops.... I think I hacked someone" "shit.. what now?" "new lawsuit.. they're runing our rootkit!"

    6. Re:All this bad news. by Anonymous Coward · · Score: 0

      Now where did I put my tin-foil hat?

      It's in my lap.

    7. Re:All this bad news. by Spl0it · · Score: 0, Troll

      Actually besides SCO's over-all trashing of linux I would have to say the stories about Debian Server and Gentoo's One Server are good news. Its shows that security measures work, and that being honest works too. If every time a companies Windows 200# server box was broken into we would have plenty of stories every single day. I think one reason we don't see that from big companies is alot don't disclose it, and the other half don't even know their systems have been comprimised.

      --

      No, this is
    8. Re:All this bad news. by cgenman · · Score: 5, Funny

      Is it sad the first thing that crossed my mind was "lots of well-timed security breaches... Microsoft may be behind them all"?

      Come on. Do you really think Microsoft knows that much about security?

    9. Re:All this bad news. by mr_z_beeblebrox · · Score: 4, Insightful

      A conspiracy theorist could have a field day..

      Uh....Ok. I'll bite. Top three theories about why all the Linux bad news.
      Number 3: Some companies that got in early on are outgrowing their business models and thus adapting.
      Number 2: Some companies with REALLY flaky software and business models are trying to figure out how to use other peoples superior software to increase their own revenue.
      The number 1 reason....: How much fun can it possibly be to say "I did a google search on Windows Exploits and owned 1000 boxen in just under an hour" as opposed to " I heard about an SSH2 compromise and searched for 2 weeks and found an affected system, gained access. Found another program with an exploit kit, eventually gained root. All in all it took a week."

    10. Re: All this bad news. by Shoggoth+of+Maul · · Score: 1

      The impossibility of securing a windows system is not so much an indication of MS-ignorance as it is of their lack of initiative to improve their product, i.e., get off their asses and stop compounding the weaknesses that have been in their products for so long.

      By analogy:

      They've created one hell of a hydra; and instead of burning the stumps they feed it and let it loose on the public, who lack the Promethean equipment to sterilize the beast.

    11. Re:All this bad news. by i_r_sensitive · · Score: 1

      Further, have they ever timed anything, let alone well timed?

      --
      "Talk minus action equals nothing" - Joey Shithead, D.O.A.
      "Talk minus action equals /." -
    12. Re:All this bad news. by DickBreath · · Score: 1

      Come on. Do you really think Microsoft knows that much about security?

      Come on. Do you really think that the RIAA knows that much about Kazaa?

      Point: it doesn't matter what you know if you can write a check to a whore who will do anything for money. (A technology whore: will do anything for money.)

      --

      I'll see your senator, and I'll raise you two judges.
    13. Re:All this bad news. by Anonymous Coward · · Score: 0

      My first thought was the U.S. govenment. It fits thier modus operandi almost exactly. Linux is gaining more and more marketshare, especially abroad where the U.S. has less accurate intelligence sources. Windows can be owned at will, but linux is a bit more of a challenge. I'm sure there are some super-secret-hi-tech-3-letter-organization-to-the- max spies out there that can walk into linux without too much of a problem, but some of the less competent agencies hirng good, but not the best, hackers out there and tasking them with putting backdoors in major linux distributions would be right in character. The Dept. of Homeland defense would be a good suspect.

    14. Re:All this bad news. by Anonymous Coward · · Score: 0

      Now where did I put my tin-foil hat?

      Uh, here it is:

    15. Re: All this bad news. by Timbo · · Score: 1

      That's a tenuous analogy really isn't it? :)

    16. Re:All this bad news. by ameoba · · Score: 1

      Everything on the GNU servers seems to be back in order now. ...except the win32 ports of Emacs. Is this some sort of political statement, or is it really -that- hard to get the files verified and put back up?

      --
      my sig's at the bottom of the page.
    17. Re:All this bad news. by gnu-generation-one · · Score: 1

      "Now where did I put my tin-foil hat?"

      Right here

    18. Re:All this bad news. by Anonymous Coward · · Score: 0

      No, that's an ass hat.

    19. Re:All this bad news. by ameoba · · Score: 1

      A few minor issues compared to the continual occurance of windows exploits, worms & viruses?

      --
      my sig's at the bottom of the page.
    20. Re:All this bad news. by WasterDave · · Score: 1

      No, but they do know about throwing money at people who do.

      Dave

      --
      I write a blog now, you should be afraid.
    21. Re:All this bad news. by bytesmythe · · Score: 1

      I was going to mention that very missing file set but didn't want to start a text editor flame war. ;)

      --
      bytesmythe
      Hypocrisy is the resin that holds the plywood of society together.
      -- Scott Meyer
    22. Re: All this bad news. by Anonymous Coward · · Score: 0
      In other words, by analogy:

      They've collectively exploded a glass bottle factory, and instead of looking for the safe and finding the money, they are spreading the little bits of glass around so that people will drive over them, and step on them. Then, two days layer they created a hydra -- one hell of a hydra -- and have added glass bottle fragments to the necks of the hydra, then painted the faces to look like Britney Spears, in the hopes of luring countless males into necking with it instead of burning the stumps. But don't forget the safe! In the glass bottle factory! MICROsOFT IS THE ONES INSIDE THE SAFE WHO ARE PLANNING TO EXPLODE EVENMORE GLASS FACKTORIES!!!!

      Hopefully that cleared things up.

    23. Re:All this bad news. by Anonymous Coward · · Score: 0

      " Lately there has been a lot of bad news about Linux.. SCO, Red Hat's discontinuing of the Red Hat Linux line, the Debian server compromise.. now this. A conspiracy theorist could have a field day.."

      The problem is people have such an overblown image of Linux, that they can't accept the reality that it's not as good as they think it is. So there must be a conspiracy.

    24. Re:All this bad news. by bonch · · Score: 1

      In other words, you're desperately spinning it all to make Linux good and Windows bad. Slashdot could be reporting that the Linux kernel infects your hard drive with trojans, and people would still spin it to involve how bad Windows is somehow.

      Prove your "1000 boxen" claim.

    25. Re:All this bad news. by Anonymous Coward · · Score: 0
      Yes, Mother Fucking John Asscrotch is personally funding and over-seeing the attack of a third tier Gentoo rsync mirror server!

      I heard that was Elvis Presley's personal mirror, too.

    26. Re:All this bad news. by Tony-A · · Score: 1

      A conspiracy theorist could have a field day..

      Ok, I'll bite.
      Looks like someone (or more than one someone) is turning up the heat.
      Seems like there has been a bit of alternation between Open Source and Microsoft. It will be interesting to see how well Microsoft copes with the next malware aimed against Microsoft.

      Backup early. Backup often.

    27. Re:All this bad news. by kabocox · · Score: 1

      No but they could buy a company or 2 that does.

    28. Re:All this bad news. by Anonymous Coward · · Score: 0
      Slashdot could be reporting that the Linux kernel infects your hard drive with trojans, and people would still spin it to involve how bad Windows is somehow.
      Microsoft already have the Copyright on kernels acting as trojans!
    29. Re:All this bad news. by jacoplane · · Score: 1

      You don't need to be a conspiracy theorist to realize it's in Microsoft's interest to point to vulnerabilities in Linux. I'm sure they've got a team of hackers hidden away somewhere dedicated to doing just that. Corporations don't have to disclose everything they do, so they will resort to some pretty nasty tactics to achieve what they want. This isn't really a conspiracy, just a fact of live. The best we can do is make sure our security kicks ass.

      In the end we could perhaps thank microsoft for pointing out these vulnerabilities, since I am of the opinion that security through obscurity doesn't work.

      A good hack will leave no traces behind, so law enforcement will have a hard time protecting us from corporate hackers.

    30. Re:All this bad news. by Anonymous Coward · · Score: 0

      It has crossed my mind too, particularly after the relative professionalism of the linux kernel backdoor compromise attempt. However, in this case, it's partly an effect of the rising linux monoculture - the local privilege exploit in brk affected many people, anyone box giving remote logins insecurely was affected and vulnerable to the same (fairly tricky) attack pattern. At least the sodding sociapathic assholes didn't turn the boxes into spamming zombies...

      It might be interesting to feel around the underground to check if there really is a bounty for compromising OSS sites of importance - I wouldn't think MS or its neofascist Bush-administration allies are above such things, but at this stage I'd still attribute it to admin incompetence (the brk() issue was known some time ago) and user incompetence (all the attacks thus far have depended on sniffed passwords) rather than malice.

      No one serious in the OSS security claims OSS is invulnerable - just that attacks are proactively and openly fixed. As an admin, I'd much rather know ASAP that an upstream source was compromised, than have to wonder what secrets a commercial vendor was keeping. And in the case of Microsoft, they themselves might be hostile to my company if it grows beyond a certain size....

    31. Re:All this bad news. by You're+All+Wrong · · Score: 3, Informative

      I have received >2000 sobigs from >1000 IP addresses.
      There's your 1000 rooted boxes, and I didn't even need to do it myself.

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    32. Re:All this bad news. by Anonymous Coward · · Score: 0

      Nope, I think it was SCO.
      You know Satan's Code is Open.

    33. Re:All this bad news. by Anonymous Coward · · Score: 0

      No but I do know microsoft does have a lot of money and saying "Make linux look bad!" to a number of hackers and paying them well for a couple months or maybe a year would be very easy for any executive. They could even spend there own money and not even the companies to get this done.

    34. Re:All this bad news. by einer · · Score: 1

      Considering that windows update has never been hacked?

    35. Re:All this bad news. by azuretek · · Score: 1

      I really cant believe even when microsoft has nothing to do with anything it is still blamed for security flaws.

      When will all you fanboys learn that blaming SCO and Microsoft for anything wrong isn't "cool".

    36. Re:All this bad news. by aposch · · Score: 1

      Conspiracy? Hey, wait, that's my second name!

      Wasn't there lately a "news", that MS is setting up a linux department for tighter analysis, to find weaknesses in this competitor?
      Now, these are fast results!

      Sorry, couldn't resist.

    37. Re:All this bad news. by Anonymous Coward · · Score: 0

      Would they tell you if it had?

    38. Re:All this bad news. by Lemmy+Caution · · Score: 1

      What you say is true. However, there's also a big difference between 1000 IP addresses of desktop machines and SOHO systems, and compromising the central system of a major - no, 2 major - distributions.

    39. Re:All this bad news. by hummassa · · Score: 1

      yeah, and microsoft update servers -AND- microsoft central source code vaults had -NEVER- been compromised... pffff.

      --
      It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
    40. Re:All this bad news. by artg · · Score: 1

      Be reasonable : if it was a year late and didn't work properly until the third attempt, THEN you might think it was MS.

    41. Re:All this bad news. by mr_z_beeblebrox · · Score: 1

      Prove your "1000 boxen" claim

      Oh, Ow. I have to prove that....to someone savvy enough to type slashdot.org in the address bar? Ok, my point was not to make Windows look good or bad. I am a math major my point was that if A is greater than B, A is greater period. There is no desperation, I have an MCSE and I maintain a heterogenous network consisting of Win 2K and RedHat ES 3.
      Some Windows hackers actually write exploits, but when they do, they post them everywhere. MS Blast was a good example of this. That writer may have been original. Then some kids downloaded the code and it's various variants have owned LARGE chunks of the web. "But that's not an exploit" you cry. A worm is a remote intrusion 'device'. You can load any payload (a trojan etc...) so in the last six months my "thousand boxen" claim is GENEROUS.

    42. Re:All this bad news. by bytesmythe · · Score: 1

      I swear it was just supposed to be a joke. I was as surprised as anyone to see it get modded as insightful!

      --
      bytesmythe
      Hypocrisy is the resin that holds the plywood of society together.
      -- Scott Meyer
    43. Re:All this bad news. by Grotus · · Score: 1
      Now where did I put my tin-foil hat?


      Whoa now, I'd be extremely careful about relying on that hat, assuming that you can find it. How can you be sure that they haven't installed some sort of bypass mechanism! Most likely though, the hat has been taken for DNA and residual brainwave analysis.

      My advice is to make a new hat, and this time, don't ever take it off.
      --
      "From my cold, dead hands you damn, dirty apes!" - CH
    44. Re:All this bad news. by Lemmy+Caution · · Score: 1

      Try to browse debian packages lately? They are still offline, after 2 weeks.

    45. Re:All this bad news. by hummassa · · Score: 1
      apt-cache search
      ... 'coz ftp.debian.org ain't.
      --
      It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  4. FULL TEXT by h4rm0ny · · Score: 1, Informative

    This is the sort of site that gets /.'d so here's the full text.
    Just to summarize - they don't know how it was done but they're pretty certain no damage was done.

    Text

    On December 2nd at approximately 03:45 UTC, one of the servers that makes up the rsync.gentoo.org rotation was compromised via a remote exploit. At this point, we are still performing forensic analysis. However, the compromised system had both an IDS and a file integrity checker installed and we have a very detailed forensic trail of what happened once the box was breached, so we are reasonably confident that the portage tree stored on that box was unaffected. The attacker appears to have installed a rootkit and modified/deleted some files to cover their tracks, but left the server otherwise untouched.

    The box was in a compromised state for approximately one hour before it was discovered and shut down. During this time, approximately 20 users synchronized against the portage mirror stored on this box. The method used to gain access to the box remotely is still under investigation. We will release more details once we have ascertained the cause of the remote explo it.

    This box is not an official Gentoo infrastructure box and is instead donated by a sponsor. The box provides other services not related to Gentoo Linux as well and the sponsor has requested that we not publicly identify the box at this time. Because the Gentoo part of this box appears to be unaffected by this exploit, we are currently honoring the sponsor's request. That said, = if at any point, we determine that any file in the portage tree was inappropriately modified, we will release full details about the compromised server.

    Again, based on the forensic analysis done so far, we are reasonably confid= ent that no files within the Portage tree on the box were affected. However, t= he server has been removed from all rsync.*.gentoo.org rotations and will rema= in so until the forensic analysis has been completed and the box has been wiped and rebuilt. Thus, users preferring an extra level of security may ensure that they have a correct and accurate portage tree by running: emerge sync Which will perform a sync against another server, thus ensuring that all fil les are up to date.

    --

    Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    1. Re:FULL TEXT by Anonymous Coward · · Score: 0


      KARMA WHORING TROLL!!

      don't fall for this people, the site is up, stable and fast.

    2. Re:FULL TEXT by Anonymous Coward · · Score: 0

      Mod parent down--flamebait/troll

      He added text to the stuff he quoted: the server was exploited like timothy's butt sometime in the past few days.

  5. Wanna bet... by Howard+Beale · · Score: 0, Troll

    they hadn't patched to 2.4.23 yet?

    1. Re:Wanna bet... by drinkypoo · · Score: 4, Interesting

      Is it even a linux box? Just because it's part of the gentoo rsync respository network doesn't mean it's running gentoo, or indeed linux.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Wanna bet... by lisany · · Score: 1

      Did you RTFA? _REMOTE_ exploit, not local.

    3. Re:Wanna bet... by KentoNET · · Score: 4, Informative

      The kernel exploit was a local one. Evidence has shown that the exploit used against the rsync server was remotely exploited. Good thing that if anything had happened (which nothing has shown up yet, according to the #gentoo-dev channel on FreeNode), it would have only affected about 20 users. Still sucks that there's an exploit at all though.

      --
      "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    4. Re:Wanna bet... by pantherace · · Score: 1
      "the server was running linux, the distribution was gentoo, there is no indication that any gentoo-specific vulnerability exists at this time."

      that was from rac

      I suspect more info will be coming later on (as they get more information)

    5. Re:Wanna bet... by jrockway · · Score: 1

      Actually, it's good that this was exploited. A remote-root vulnerability is pretty bad, now we know about it and can fix it. That's what makes Linux and OSS better than the alternatives; when there's a problem it's fixed and Linux becomes that much better.

      Windows and its friends just slap on patches and Windows doesn't improve as a result. The next virus gets 'em all again.

      So as a result of these 20 people having a compromised rsync, some 'bigger fish' (the main server?) will be "saved" from this exploit. That's a very very good thing.

      --
      My other car is first.
    6. Re:Wanna bet... by Codifex+Maximus · · Score: 1

      I'll bet it was probably the exact same exploit that was used to hit Debian.

      With everyone updating to Linux 2.4.23, we should see less of this sploit in the near future. Now what it's going to do to uptimes....

      Makes you wanna dust off the old Tripwire doesn't it? I've gotten a copy of chkrootkit too. :)

      --
      Codifex Maximus ~ In search of... a shorter sig.
  6. windowsupdate.microsoft.com Breakins? by Anonymous Coward · · Score: 0

    How come we never hear about breakins there or at this miserable failure of a website.

    1. Re:windowsupdate.microsoft.com Breakins? by TWX · · Score: 4, Funny

      "How come we never hear about breakins [at windowsupdate.microsoft.com]..."

      Because we wouldn't have time for all of the other news.

      --
      Do not look into laser with remaining eye.
    2. Re:windowsupdate.microsoft.com Breakins? by JeffMagnus · · Score: 3, Insightful

      I'd like to see at least one credible report of a breakin at Windows Update. If someone can provide one you will forever earn my eternal respect.

    3. Re:windowsupdate.microsoft.com Breakins? by Tuba · · Score: 2, Insightful

      You're not likely to hear of it if one happens, as a general policy large companies a don't disclose such information to the public. Even the small-ish place where I work wouldn't.

      --
      We're sysadmins, to us, data is protocol overhead.
    4. Re:windowsupdate.microsoft.com Breakins? by Nerull · · Score: 1

      Ive seen a screenshot of it displaying the 'Hacked by Chinese!' Code Red page, but I didn't see it myself, so it may have been faked.

      Unless its a defacement, and someone notices, you probobly wouldn't hear about it.

    5. Re:windowsupdate.microsoft.com Breakins? by jrcamp · · Score: 2, Interesting

      Comparing WindowsUpdate to the portage tree isn't quite an accurate analogy. Portage is distributed to a number of 3rd party donors/volunteers who look after the servers. It's not like the Gentoo team looks after them.

      A better analogy would be to ask how many times the update sites for RedHat, Mandrake, etc. etc. has been broken into, since the main update locations are kept up by their respective corporations. I have no idea what the answer to this is.

    6. Re:windowsupdate.microsoft.com Breakins? by Anonymous Coward · · Score: 0

      I went to update Windows about 7 or 8 months ago (can't remember when it was exactly) and the site was changed to some online bookstore or some other rubbish. About an hour or two later, it was back to normal.

    7. Re:windowsupdate.microsoft.com Breakins? by Lehk228 · · Score: 1

      IIRC the load balancing for Windows Update is carried out bu linux machines and i wouldn't be suprised if the windows servers have other layers of OSS machines shielding them from the outside world.

      --
      Snowden and Manning are heroes.
    8. Re:windowsupdate.microsoft.com Breakins? by Tim+C · · Score: 1

      That sounds more like a DNS hijacking than a break in, though - that could have happened to your ISP's DNS servers, and almost certainly didn't involve anything owned or maintained by MS.

    9. Re:windowsupdate.microsoft.com Breakins? by kasperd · · Score: 1

      IIRC the load balancing for Windows Update is carried out bu linux machines

      Not anymore according to netcraft. Only trace left of Linux I could find is www.microsoft.com running on Linux until about a week ago. And they have been changing a lot the last week, so those traces will soon be gone as netcraft appears to keep only the last 10 changes.

      --

      Do you care about the security of your wireless mouse?
    10. Re:windowsupdate.microsoft.com Breakins? by You're+All+Wrong · · Score: 1

      May have been localised DNS poinsoning?

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    11. Re:windowsupdate.microsoft.com Breakins? by zcat_NZ · · Score: 1

      Does this count?

      --
      455fe10422ca29c4933f95052b792ab2
    12. Re:windowsupdate.microsoft.com Breakins? by Cyrus2001 · · Score: 0

      I've seen it compromised. It was some time ago, when the Unicode-Exploit was around. You could see that page changing nearly every second when the scriptkiddies were fighting about the server. 1 month after they had an update for that bug windowsupdate.microsoft.com wasn't updated. How ironically is that?

    13. Re:windowsupdate.microsoft.com Breakins? by aonaran · · Score: 1

      To be fair this is more on the scale of someone compromizing a SUS server, not really like compromizing windowsupdate.microsoft.com

    14. Re:windowsupdate.microsoft.com Breakins? by crschmidt · · Score: 1

      ot quite accurate: [crschmidt@peanut ~]$ host www.microsoft.com www.microsoft.com is an alias for www.microsoft.akadns.net. www.microsoft.akadns.net is an alias for www2.microsoft.akadns.net. Microsoft is still using Akamai, whose servers report as Linux, last I checked. Which it seems like, from this comment, you think it isn't. Either I'm miunderstanding, or you are, but Microsoft definitely does use a level of OSS between them and their servers. Of course, this level of seperation has no affect on security - it simply passes on what needs to be passed on. However, it is still there.

      --
      -- Christopher Schmidt YouTube Quality of Experience
    15. Re:windowsupdate.microsoft.com Breakins? by kasperd · · Score: 1

      an alias for www2.microsoft.akadns.net

      But that domain name points at an IP address inside Microsoft's network. But then I just noticed the funny part. The most stable web servers on Microsoft's own network are running Apache/1.3.9 on Linux

      --

      Do you care about the security of your wireless mouse?
    16. Re:windowsupdate.microsoft.com Breakins? by JeffMagnus · · Score: 1

      And the winner!

  7. RSYNC by lisany · · Score: 0

    This seems to be a vuln in Rsync, not Gentoo. Hmm... Should be interesting to see what the audit turns up!

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

      And on what, apart from your own fevered imagination, are you basing that assumption?

    2. Re:RSYNC by KentoNET · · Score: 1

      The part that resides on #gentoo-dev, where all the official chatter is going on.

      --
      "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    3. Re:RSYNC by lisany · · Score: 1

      Quite possibly from the ability -- which only I possess -- to read other person's thoughts and join #gentoo-dev.

      Now, whoever modded the original to "overrated" ? Oh come on. The connection this "incident" has to Gentoo is that it was a Gentoo rsync mirror. I could see the hype if the machine was under Gentoo control - but seriously now.

    4. Re:RSYNC by lisany · · Score: 1
  8. Re:huh? by Anonymous Coward · · Score: 0

    This was a local root hole. OpenBSD has had stacks of those.

  9. How do they know? by iantri · · Score: 2, Insightful
    "However, the compromised system had both an IDS and a file integrity checker installed and we have a very detailed forensic trail of what happened once the box was breached, so we are reasonably confident that the portage tree stored on that box was unaffected."

    IANAH (hacker), but isn't the first thing you do when you break into a system to 'fix' the logs?

    How can they guarantee the tree hasn't been affected? Compare it with another copy?

    1. Re:How do they know? by Feyr · · Score: 4, Informative

      remote logging

    2. Re:How do they know? by mahdi13 · · Score: 2, Insightful

      You can 'fix' logs, but you can't fix all the md5sums that are scattered around the internet

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    3. Re:How do they know? by Anonymous Coward · · Score: 0

      Depends. If you break in and have root then yes, if you break in and only get a non-root account then you can't.

    4. Re:How do they know? by agurkan · · Score: 3, Insightful

      An intrusion detection system, e.g. snort, can send the logs offsite, so compromising a machine does not always allow you to wipe the logs. The people who administer these machines probably know what they are talking about, and they have little incentive wrt prop. software guys to lie about their system safety. Debian guys came forward with all details, I believe Gentoo people would not tell lies about security breaches either.

      --
      ato
    5. Re:How do they know? by DA-MAN · · Score: 2, Insightful

      I don't know about this specific setup, but it is standard operating procedure to set up a bastion (read hardened) host that just runs syslog and nothing else for the purpose of logging what goes on in a central location.

      In addition, they can just rsync the portage stored on that box to another to see if any changes were made.

      --
      Can I get an eye poke?
      Dog House Forum
    6. Re:How do they know? by pete-classic · · Score: 3, Informative

      By "file integrity checker" I presume they mean something like AIDE.

      One makes hashes of each file and stores them on a non-networked system and/or read-only media. Then periodically runs a check (hopefully from a statically linked binary that is also on RO media) on the files and compares the hashes.

      If they match (and any number of other conditions are met, like the machine and the media the hashes were stored on are physically secure, etc.) you can say with reasonable certainty that the files are unmolested.

      -Peter

    7. Re:How do they know? by Our+Man+In+Redmond · · Score: 4, Insightful

      I'd just set up a remote box specifically for logging and connect it to a cheapo dot-matrix line printer and have the logs printed to paper. Yeah, you might use a bunch of paper, but it also might come in real handy if you ever need to figure out what really happened to your box.

      --
      Someone you trust is one of us.
    8. Re:How do they know? by Stonent1 · · Score: 3, Informative

      remote logging

      Do you mean that people don't use line printers any more???!!? Back in the good old days, (not really) we'd have the computer print the diffs of any files that ever changed on the system in real time!

    9. Re:How do they know? by 4of12 · · Score: 1

      you can't fix all the md5sums that are scattered around the internet

      That would be hard.

      What might be easier is to fix the routers to, uhmm..., make those downloaded md5sums be The Right Answer. Just look for http or ftp with URL ending .md5sum

      Or, compromise the md5sum source code in core-utils prior to the attack so that it reports The Right Answer when requested.

      To make it harder on the cracker, digitally signed code and a repository of previously- downloaded public keys make it pretty damn tough.

      --
      "Provided by the management for your protection."
    10. Re:How do they know? by boredMDer · · Score: 1

      Read The Cuckoo's Egg often, do we? heh

    11. Re:How do they know? by nathanh · · Score: 1
      IANAH (hacker), but isn't the first thing you do when you break into a system to 'fix' the logs?

      Any high-profile site has (or should have) a box dedicated to syslogd. No ssh. No ftp. No www. No non-syslog services of any kind. To read the logs you have to logon to the console. All other servers in the environment dump their logs to the logging server. In the event of a breach, you use the handy CD burner on the logging server to get your untainted forensics dump.

      Of course, you cross your fingers and pray to the gods that syslogd doesn't have a remotable compromise.

    12. Re:How do they know? by Anonymous Coward · · Score: 1, Funny

      ***
      12:15 - Entry - Werner Brandis...*****
      ***

    13. Re:How do they know? by Drantin · · Score: 1

      hehe... that reminds me of Cliff Stoll's The Cuckoo's Egg... He hooked up printers to the modems the comps were using and monitored the hacker that way.

      --
      Actio personalis moritur cum persona. (Dead men don't sue)
    14. Re:How do they know? by JK+Master-Slave · · Score: 1

      Most kids these days don't know what you mean by 'line printer.'

    15. Re:How do they know? by Anonymous Coward · · Score: 0

      That doesn't tell you what happened after they 'fixed' the remote logging routine.

    16. Re:How do they know? by jrockway · · Score: 1

      No. You can ssh into the box with the MD5 sums and the router can't do anything. Does it have the encryption/decryption key?

      Try again :)

      Also, if all the routers in the world are compromised, Gentoo's problem won't seem very severe anymore...

      --
      My other car is first.
    17. Re:How do they know? by jrockway · · Score: 1

      Put that server behind a NAT box / firewall so non-local IPs can't even see it. That makes a remote exploit even more difficult!

      --
      My other car is first.
    18. Re:How do they know? by Anonymous Coward · · Score: 0

      Why don't you just put a recieving-only machine dedicated to IDS ?

      Nobobdy will be able to alter anything on that machine, neither the soft nor the logs. (unless, of course, they have physical access to the machine)

      Please see 3.2 point of:
      http://www.snort.org/docs/FAQ.txt

      --
      Marc - http://www.planetgong.net

    19. Re:How do they know? by Anonymous Coward · · Score: 0

      Why not log to a serial port connected to a computer that has no ethernet card and stores the logs to disk (mount -o sync)? Perhaps that box can also have a CD or DVD writer and write the logs (multisession) to read-only media, just to be on the super safe side.

      Saves a lot of trees that way (not to mention administation hassles of the stacks of paper).

      Oh man, I did it again... I didn't get that it was meant as a joke.

    20. Re:How do they know? by scosol · · Score: 1

      Parent is not "insightful" in any way- go read some books or something...

      IDS?
      chroot?
      read-only?

      Does any of this mean anything to you?
      There are a myriad of ways to make it *impossible* for a remote attacker to totally cover his tracks.

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
    21. Re:How do they know? by MikeCapone · · Score: 1

      Oh man, I did it again... I didn't get that it was meant as a joke.

      Or was it?

      [pause]

      Ever wondered why forests are disappearing at this rate?

    22. Re:How do they know? by Rich0 · · Score: 1

      Most college students these days don't know what you meant by 'line printer'.

      Most kids these days don't know what you meant by 'dot matrix printer'.

      Also - when you say "encyclopedia" they think little shiny CD or a website.

      It was truly scary when a coworker's daughter asked him "you mean you didn't have email when you were a kid?".

  10. So... by Coryoth · · Score: 0, Troll

    What do all those Gentoo fanboys who were saying "this would never happen with Gentoo" when Debian had problems have to say now? What can you do about zealots?

    And sorry to all the many, many, perfectly sensible Gentoo users out there. An unfortunate incident, but, as with the Debian incident, it looks as if it is being well handled. I'll be interested to see the details on how the compromise occurred.

    Jedidiah

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

      I would just like to point out that this would never happen to gentoo! Gentoo is the best and most secure distro out there. Don't call me a "zealot" just because I tell the truth.

      --
      Gentoo user

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

      And it may yet never happen with Gentoo. It doesn't specify what was running on the server. It's a donated server running other unannounced services, there's a good chance it in fact wasn't running gentoo.

    3. Re:So... by Anonymous Coward · · Score: 0

      Sounds to me like the box is managed by the third party which donated it's use, so it's being compromised has little or nothing to do with Gentoo at all.

    4. Re:So... by Bombcar · · Score: 4, Funny

      I though the Gentoo Zealot response would be:

      "Ah, but Gentoo's root exploit was compiled from source, so Gentoo got rooted 0.000000124% faster than Debian!"
      :D

      Ah well, I like Gentoo myself. It is quite fun.

    5. Re:So... by IdleTime · · Score: 1

      Was there ever anyone saying that?

      As a Gentoo user and moderator at the forums, I have never seen any serious users of Gentoo take that attitude, quite the opposite actually. Any server can be vulnerable to attacks, no matter what system is run. There will always be ways of gaining access after an exploit has been discovered until it gets patched. It doesn't matter what the name of the OS is.

      --
      If you mod me down, I *will* introduce you to my sister!
    6. Re:So... by GooTi · · Score: 1
      Any server can be vulnerable to attacks, no matter what system is run.


      Does that include remote exploits for DOS? (not DoS, mind you!)

  11. Pointy-Hat theory time.. by msimm · · Score: 4, Insightful

    Either hackers have decided they *hate* OSS (not likely) or someone is putting up a purse trying to damage the OSS communities security image.

    --
    Quack, quack.
    1. Re:Pointy-Hat theory time.. by molafson · · Score: 5, Insightful

      Either hackers have decided they *hate* OSS (not likely) or someone is putting up a purse trying to damage the OSS communities security image.

      Or (C) None of the above. To want to crack something you don't need to hate it (or to be paid to hate it). The possibility of finding vulnerabilities is tantalizing enough on its own. To crack something that big would be a major black-hat ego trip, don't you think?

    2. Re:Pointy-Hat theory time.. by li99sh79 · · Score: 1
      Either hackers have decided they *hate* OSS (not likely) or someone is putting up a purse trying to damage the OSS communities security image.

      Well, everytime there's a major windows exploit you always hear "blah blah, Linux, blah blah BSD, blah blah OSX." Maybe the hackers are just looking for a new way to prove their "l33t h4x0r1ng sk1llz."

      -sam

      --
      I was just here, where did I go?
    3. Re:Pointy-Hat theory time.. by TrancePhreak · · Score: 1

      A lot of people *hate* OSS zealotry, so perhaps it was only a matter of time before one of them was smart enough to pull something like this off.

      --

      -]Phreak Out[-
    4. Re:Pointy-Hat theory time.. by CFBMoo1 · · Score: 5, Insightful

      I think part of this can be attributed to the fact that OSS and Linux is gaining popularity. While it isn't probebly the whole reason, there is a certain amount of truth to being in the spot light more and being a bigger target. I'm sure there will be more of these stories in the future. It's only natural to get more attention when you winning a popularity contest. :)

      --
      ~~ Behold the flying cow with a rail gun! ~~
    5. Re:Pointy-Hat theory time.. by Martigan80 · · Score: 2, Interesting

      I can agree to this in a way. Just because someone like an Alternate OS does not mean that they are ignorant about Linux, after all it's well documented!

      --
      This SIG pulled due to lack of funding. (This damn war is costing too much!)
    6. Re:Pointy-Hat theory time.. by Anonymous Coward · · Score: 0

      Or (much more likely), GNU/Linux systems are incredibly easy to compromise. One probably couldn't even count the bind and sendmail exploits alone on 30 hands and 20 feet.

    7. Re:Pointy-Hat theory time.. by iabervon · · Score: 1

      I think it's more likely that crackers have noticed that OSS servers tend to be interesting to crack. There are a lot of services which might be vulnerable to a number of different exploits, and they might contain or have access to information that could be used to attack other servers.

      Windows machines, by contrast, are pretty dull. It's evidently trivial to crack tons of them, and there's nothing interesting on them. Unless you want to do a DDoS attack, there's no point.

    8. Re:Pointy-Hat theory time.. by EvilTwinSkippy · · Score: 1

      I have a better theory. OSS finally has something that is worth cracking for them. I would almost say this is a sign of reverence and respect (as much as black hats understand the concepts.)

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    9. Re:Pointy-Hat theory time.. by Anonymous Coward · · Score: 0

      The possibility of finding vulnerabilities is tantalizing enough on its own.

      Funny, they can already legally RTF Source to do that.

    10. Re:Pointy-Hat theory time.. by aquarian · · Score: 1

      To crack something that big would be a major black-hat ego trip, don't you think?

      Only if you're some kind of anti-social fuckhead malcontent. Oh yeah, most of these guys are, at least the ones that I've met...

    11. Re:Pointy-Hat theory time.. by Anonymous Coward · · Score: 0

      Follow the profit motive upstream... who benefits from compromising Linux sites or otherwise interfering with the OSS people/movement.

      Microsoft has a major profit motive. If they can try to demonstrate exploits in OSS at least on par with what Windows 2003 has already been shown to have, they can try to claim equal security.

      The currently ultra-paranoid US Gov't. stands to gain if they can push all users onto "trusted" platforms. Windows is the next candidate and they have been shown to have non-trivial connections to the current administration either fiscally or in the "good ol' boys" sense.

      In all, the really paranoid notions all point to a joint effort. Microsoft might be providing impetus and the back-up line of offense in the form of Windows. The government wants to see all users on a platform that can be trusted, not by the users, but by the gov't. If they can see to it that Windows becomes that official closed-source platform of the US, they can pull all sorts of dirty tricks behind the scenes with no one the wiser.

  12. Just one of many. by zeroclip · · Score: 0, Troll

    Just one server of the many resync servers was compromised. It's not the end of the gentoo zealots, MUHAHAHA.Gentoo pwnz j00 :P

  13. Hmm... by Anonymous Coward · · Score: 0

    First Debian, now Gentoo.... Conspiracy! Either that or a horror movie.

    Fortress of Insanity

    1. Re:Hmm... by Trigun · · Score: 1

      Or the same vulnerability...
      Hell, if I wanted to hit a target, that's the one I'd go for. One crack and you have rooted hundreds of machines.

  14. Deliberate attacks? by Realistic_Dragon · · Score: 4, Interesting

    I just threw away my tinfoil hat and made a new one out of steel. With a spike on top.

    Once is happenstance, twice is coincidence, three times is some one playing silly buggers.

    (Kernel.org, debian.org, gentoo.org - all in the same two months?)

    --
    Beep beep.
    1. Re:Deliberate attacks? by Pyromage · · Score: 1

      The gnu servers too, not too long previous, iirc.

    2. Re:Deliberate attacks? by Anonymous Coward · · Score: 0

      I'm amazed that the linux community is shocked that flaws are being exploited. After all, only Windows is susceptible to security holes, right?? Face it, no OS out there is perfect and hackers are going to doing there thing against any type of box - they don't care whether it's linux, Mac, or windows. The OSS guys just need to get down off their ivory tower and face reality.

    3. Re:Deliberate attacks? by Anonymous Coward · · Score: 0

      new one out of steel. With a spike on top.

      Be careful that spike doesn't act as a lightning rod. Recommend you stick a rubber on it. (Now there's a new use for condoms - lightning prevention)

    4. Re:Deliberate attacks? by Anonymous Coward · · Score: 0

      How many attacks are not deliberate? "Oh, whoops, I installed a rootkit on the gentoo server. Dang!" ;-)

    5. Re:Deliberate attacks? by pjack76 · · Score: 1
      It does seem likely that the same person or group is behind the attacks, given that the targets are all so similar.

      But who in their right mind would attack a nonprofit that produces free software? I mean, the attackers are probably using open source/free software tools to launch the attacks, you'd think they wouldn't bite the hand that feeds them.

      My current favorite theory is that this is what Microsoft is using their Linux lab for. ;)

      --

      Wow, a lucrative publishing contract! I don't have to be evil anymore. --Meteor

    6. Re:Deliberate attacks? by fishbot · · Score: 1

      Yep, definitely a conspiracy. Especially as the three hit servers are the 'bastions of freedom' in the Linux World. Red Hat, SuSE, Mandrake etc. were not hit, and they are taking the capitalist route.

      *puts on conspiracy theory soundtrack and locks self in safe*

    7. Re:Deliberate attacks? by EvilTwinSkippy · · Score: 3, Interesting
      You see it every few years. I remember back in '98 everyone was getting rooted because of bugs in named. Later it was Apache. They come in waves as the crackers figure out new patterns of exploits, and like all of the other "fad" break-ins they are going to come to a crashing end after a quick code review.

      Whoever is behind this is showing off for sure.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    8. Re:Deliberate attacks? by Anonymous Coward · · Score: 0

      Another one of those 'I-only-see-the-big-picture' assholes eh?

      Truth is, the details matter too. Take a look at each one.

    9. Re:Deliberate attacks? by theCat · · Score: 1

      You didn't mention SCO in the list of "attacks"...but in a way you could have.

      I think many are tuning in to the same channel as you are; there appears to be a lot of activity to drive down linux mindshare. It might be a coincidence and many assume that is the case...but it doesn't have to be the case does it?

      And still Occam's razor demands the simplest explanation be assumed the correct one. So in this case we're seeing a chance alignment of events. SCO. Linux distributions attacked. Ballmer going on record saying that Windows has fewer (interesting) security failures. Et cetera. But Occam's razor does not require that we remain obtuse to patterns. Only that we wait and see what emerges.

      So let's wait. If this is a serious FUD effort then someone on the inside is bound to let the cat out of the bag. And if it's not FUD...then maybe there are rough seas ahead.

      --
      =^..^= all your rodent are belong to us
    10. Re:Deliberate attacks? by gid · · Score: 1

      heh, I kinda doubt a few millimeters of rubber is going to insulate anything against lightning.

      Kinda like how people say tires insulate a car against lightning, a few inches of rubber isn't going to do squat, according to my high school physics teacer, you're safe in a car because lightning stays on the outside of a metal enclosure.

    11. Re:Deliberate attacks? by caluml · · Score: 2, Funny

      I think the moral of the story is not to have a .org top level domain.

    12. Re:Deliberate attacks? by Anonymous Coward · · Score: 0

      Your condoms are a few millimeters thick? dude, going for the "don't care if I can feel anything I'm gonna be safe" style trojans eh?

    13. Re:Deliberate attacks? by You're+All+Wrong · · Score: 2, Informative

      There's more than one person behind this.
      Nearly the same time that Debian's boxes were rooted, a
      "friend of Debian" had his system rooted too, and the
      exploits and rootkits used were very similar, as the
      sysadmins compared notes. However, they were subtly
      different and the most likely explanation is that the
      two hackers knew each other, and exchanged some
      information, but weren't the same person.

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
  15. Time to Switch to Debian by Anonymous Coward · · Score: 5, Funny

    They haven't had a break in two weeks!

    1. Re:Time to Switch to Debian by AsnFkr · · Score: 1

      It took me two weeks to just load Gentoo on my box due to the last Debian hack! I can't keep up with all this!

      Laugh kids!

    2. Re:Time to Switch to Debian by Anonymous Coward · · Score: 0

      And here is the obligatory post of the person who doesn't get that it was meant as a joke.

      See line above.

  16. Re:huh? by Anonymous Coward · · Score: 0


    fuck you they have. It's all conspiracy from the Lunix boys. Theo de Raadt and his army of Real CodeX0r Men is teh shiznat.

  17. Debian, Gentoo.... who's next? by Goyuix · · Score: 4, Insightful

    Any bets on which major distro will be next? Better yet, instead of point spreads on professional sporting events - Vegas should be taking bets on which distro (or well established free software org) gets rooted next...

    First Debian, now Gentoo... Slackware perhaps? Maybe install a spam-bot on a knoppix image?

    1. Re:Debian, Gentoo.... who's next? by Anonymous Coward · · Score: 0

      are we sure that commercial distros haven't already faced similar attacks?

    2. Re:Debian, Gentoo.... who's next? by Anonymous Coward · · Score: 1, Interesting

      lets see, the big distros are
      Red Hat
      SuSE
      Debian
      Gentoo
      Slackware

      (sort)

      Debian
      Gentoo
      Red Hat
      Slackware
      SuSE

      Red Hat (if they still count since that fedora thing) followed by Slackware, then SuSE

      however, i probably missed a couple of other big ones, but then there is the whole debate about what is a major and minor distro.

    3. Re:Debian, Gentoo.... who's next? by malverian · · Score: 1

      Any bets on which major distro will be next? ... Slackware perhaps?

      Since when is Slackware a major distro? :-X

      --
      You're just mad because the voices in your head talk to me.
    4. Re:Debian, Gentoo.... who's next? by Anonymous Coward · · Score: 0
      a few missed: (between Gentoo and Red Hat)
      Lindows
      Lycoris
      Knoppix
      Mandrake

      based on Distro Watch's Major Alphabetical List

      and for fun you could add Caldera - its CEO was compermised... how else can you explain it?

    5. Re:Debian, Gentoo.... who's next? by placeclicker · · Score: 1

      For some reason i don't think they'll go after Redhat.

      Just because they've moved away from free distros.

      --

      Browse at -1, because trolls are often the most creative part of /.
    6. Re:Debian, Gentoo.... who's next? by Anonymous Coward · · Score: 0

      maybe not anymore, but its one of the only ones that still has half a brain

    7. Re:Debian, Gentoo.... who's next? by rastos1 · · Score: 1

      According to Linux counter it is number 4. Considering number of distributions out there it *is* a major distro.

  18. GAAAAH!!!! by Enahs · · Score: 1, Funny
    I decided to switch away from using Gentoo (after I accidentally nuked my system for the 12th time, my fault) to Debian. The day afterward, they were compromised, and they still haven't gotten back to normal.

    Today, I decided that I wasn't entirely happy with Debian, and so I have Gentoo stage3 LiveCDs sitting on my desk, ready for an install when I get home...

    Maybe someone should start working on Desktop OpenBSD. :-P

    --
    Stating on Slashdot that I like cheese since 1997.
    1. Re:GAAAAH!!!! by twoslice · · Score: 1

      Don't use GAAAAH! in your subject line dude! it is much too close to GNAA and you could be moderated to oblivion....

      --

      From excellent karma to terible karma with a single +5 funny post...
    2. Re:GAAAAH!!!! by Anonymous Coward · · Score: 0

      Whatever you install next, make sure you tell the people in charge of that OS/distribution. They should get some warning to check their servers before they get attacked.

    3. Re:GAAAAH!!!! by Unregistered · · Score: 1

      You're obviosly bad luck and i'd appreciate it if you avoid my favorite distro, gentoo. however, the OpenBSD guys work hard, so it wouldn't be nice to use OpenBSD either. Use SCO OpenServer and maybe the SCO problem will solve itself.

    4. Re:GAAAAH!!!! by MarkJensen · · Score: 1

      Oh, come on Moderators! Someone has *got* to mod the parent here Funny! :) Everyone could use a good SCO joke!

    5. Re:GAAAAH!!!! by Darth+Daver · · Score: 1

      >>Maybe someone should start working on Desktop OpenBSD. :-P

      Then the servers hosting the ports system will be compromised.

      If you change OS everytime something like this happens, you will wear out your CD drive (and yourself) installing new OS. No OS or organization is immune to being compromised. Even highly secure OS are vulnerable to poor processes and procedures. There are no guarantees in life.

      Just be thankful that the recent OSS attacks were quickly detected and handled in an honest, open and effective manner because the sysadmins understand and care about security more than about marketing.

  19. On the bright side... by Chalybeous · · Score: 4, Interesting

    ... they DO have records of what was done and were able to isolate it pretty quickly. IMHO, that's probably saved them a lot of trouble.
    Whether it's because the cracker was sloppy or inexperienced, or because the Gentoo team have good server security, I can't say - but it seems they were pretty lucky compared to Debian.

    What baffles me is why crackers go after targets like this. I can understand anticapitalist stuff, but my intuition says someone trying to crack a *nix server and damage a distro must have detailed knowledge of *nix systems - and is therefore likely a user of an OpenSource operating system.
    Is that guess a little too far off base? If so, what's your take?

    --

    "It is dark. You are likely to be eaten by a grue." -- Zork

    1. Re:On the bright side... by ballyn · · Score: 1

      Actually, it wasn't even a Gentoo machine... "This box is not an official Gentoo infrastructure box and is instead donated by a sponsor". I don't know if Gentoo requires server admins to use IDS or something similar if this was just a good admin running the mirror. I guess we'll know when (if?) Gentoo tells us who was running the box.

    2. Re:On the bright side... by zangdesign · · Score: 5, Insightful

      What baffles me is why crackers go after targets like this.

      Because some individuals are asshats, that's why. You could create the cure for cancer and some asshole would try to shoot it down just because it's there. After all, we are the same species that nailed some poor bastard to a cross just because he said we should all get along for a change.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    3. Re:On the bright side... by Our+Man+In+Redmond · · Score: 4, Informative

      OK, I RTFA and it doesn't look to me like they were going after Gentoo specifically. The way I read it, this was just a box somewhere that a sponsor had set up to house a Gentoo rsync node, and had a bunch of other stuff on it as well. The box got rooted and the cracker didn't touch any of the other stuff on the box -- just what he needed to obfuscate his entry and do all the usual rootkit stuff.

      Why do they do this? Because they can. Personally, I blame that darn rap music.

      --
      Someone you trust is one of us.
    4. Re:On the bright side... by Chalybeous · · Score: 1

      Yeah, I noticed that, but the fact it was a remote exploit and the cracker installed a rootkit immediately made me think *nix-based OS.
      However, as I keep reminding people, /me != g33k - I dunno if it's possible to do the same on other server OSs... I just picked up the thought because other articles on compromised *nix servers have mentioned rootkits.
      Anyone more technical than me care to step in and provide "Just the facts, Ma'am."? [/joefriday] ;-)

      --

      "It is dark. You are likely to be eaten by a grue." -- Zork

    5. Re:On the bright side... by Chris_Mir · · Score: 1

      but my intuition says someone trying to crack a *nix server and damage a distro must have detailed knowledge of *nix systems - and is therefore likely a user of an OpenSource operating system.

      Or on someone's payrole...

    6. Re:On the bright side... by rritterson · · Score: 1

      You are assuming that someone must be a supporter of something they are knowledgable about.

      Just because someone knows *nix very well does not mean they have a shred of affinity toward it.

      By the same token, how many people here know Windows?

      --
      -Ryan
      AUWYHSTOT (Acronyms are Useless When You Have to Spell Them Out Too)
    7. Re:On the bright side... by i_r_sensitive · · Score: 1
      I'd say your intuition is probably correct.

      But using FOSS is not equivalent to supporting FOSS. The script kiddies taking advantage of M$ vulnerabilities are probably M$ users themselves.

      In the majority of these cases trying to attach it to some group or another's agenda is pointless. SCO tried that stunt when they were getting harassed. The FOSS folk indicated that they had no knowledge, gave no support for, and even went so far as to condemn whoever was doing so. No, most adults I think understand that you cannot forward a legitimate agenda in this fashion.

      If they do catch whomsoever, I'm gonna guess they are young, probably under 18, almost certainly under 21. Failing that, I would expect the individual to function under that age level, there certainly is no shortage of thirty-somethings who are incapable of co-relating cause and effect. For proof, I suggest a day spent reading the AC posts on /.

      In general I think trying to find a political motive for these things is fruitless. Most often there probably isn;t one (in the case of true youth) or if there is, it is clearly sociopathic (the suspected use of trojans by spammers, for example.)

      Lastly though, check those edge kernel versions people!

      --
      "Talk minus action equals nothing" - Joey Shithead, D.O.A.
      "Talk minus action equals /." -
    8. Re:On the bright side... by Anonymous Coward · · Score: 0

      >Is that guess a little too far off base? If so, what's your take?

      It was hacked by a Debian zealot...

    9. Re:On the bright side... by Chalybeous · · Score: 1

      Good call on the M$ vulnerabilities point, I'd honestly forgotten about that. IIRC, there are cracking/intrusion kits and virus kits to attack Windows machines, that the cracker must run as a Windows .exe file.
      I never thought that the cracker was a *supporter* of OpenSource operating systems, but a user - he'd've had to get the knowledge from somewhere. I guess the rational bit of me says "Isn't that kind of crack like shooting yourself in the foot?", but then again - as the script kiddies prove - it's hardly a rational act.
      Thanks for the input, it's always good to get replies from folks like yourself who have an interesting point of view or a better knowledge of the issues than I do.

      --

      "It is dark. You are likely to be eaten by a grue." -- Zork

    10. Re:On the bright side... by RealityThreek · · Score: 1

      Cracking systems is a good thing, it points out vulneribilities. It would have been better if they left a README.hacked file on the machine, that showed what they changed and how they did it. Since they didn't, I can only assume they did it for less than altruistic reasons. ;)

      --
      :wq
    11. Re:On the bright side... by Anonymous Coward · · Score: 0

      we are the same species that nailed some poor bastard to a cross just because he said we should all get along for a change.

      Yes, I get the reference. Mr Adams, however, was mistaken. I don't remember the bit about "wouldn't it be nice if we could all get along", most of what's stuck in my mind is that stuff about "I come not to bring peace but a sword", and the bit where he called the religious authorities of the day a "nest of vipers", and then there's the bit where he damaged the local economy by throwing traders out of the temple... not to mention that he was causing serious civil unrest by, e.g., claiming to be God.

      Unless I've got it all wrong and you're talking about Brian, of course, ;)

    12. Re:On the bright side... by Anonymous Coward · · Score: 0
      What baffles me is why crackers go after targets like this.

      If you were going to hack something "because you can" which would look more impressive?

      compromising a K12 district/school or business server which may or may not have good security or

      compromising a linux distribution center where the administrators know their SH from their IT or

      backdooring an exploit in a linux kernel

      The answer is obvious - script-kiddies can usually do #1 but rarely are able to do #2 or #3. One proves their hacking ability by going after #2 or #3.

    13. Re:On the bright side... by Chalybeous · · Score: 1

      LOL - would've been nice if the guy was a white hat and did that. An OpenSource distro group might've let him get away with it and said "Thanks!", but I seem to recall that a few people who've hit the headlines in recent months for exposing vulnerabilities in proprietary software have actually ended up on the wrong end of legal action for computer crime, DMCA violations etc.
      A shame so few people appreciate white hats. I know I'd be grateful if a .txt file appeared on my workspace that said "Dude, you've left a port open that people can use to get into your machine - here's how you close it".

      --

      "It is dark. You are likely to be eaten by a grue." -- Zork

    14. Re:On the bright side... by i_r_sensitive · · Score: 1
      NP,

      BTW, I did not mean to implicate that you were making the erroneous link between user and supporter. However, as I bet you can appreciate, given the variety of folk who read the posts on /., I often feel constrained to teach everyone's grandmother to suck eggs.

      --
      "Talk minus action equals nothing" - Joey Shithead, D.O.A.
      "Talk minus action equals /." -
    15. Re:On the bright side... by N1KO · · Score: 1

      Does he actually claim to be God? He always calls himself "the son of god", the idea that he was god probably came later from someone in the church.

    16. Re:On the bright side... by Anonymous Coward · · Score: 0

      nailed some poor bastard to a cross just because he said we should all get along for a change.

      When did they nail Rodney King to a cross?

    17. Re:On the bright side... by pyros · · Score: 1
      they were pretty lucky compared to Debian

      In what way? Other than it just being one box I can't think of anything. The Debian people were able to detect the situation and state with a fair degree of certainty that the package archives were intact too. The Debian team's forensics led to the discovery of the local root kernel exploit (with aid from Red Hat and Suse). Not quite sure if there's something I'm missing.

    18. Re:On the bright side... by Anonymous Coward · · Score: 0

      Check Matthew 23:37. It's one of the synoptic (i.e. narrative) gospels, and Jesus is addressing Jerusalem the way the LORD addresses his people Israel through the prophets.

      It's quite striking - Jesus claims to be the mother hen, gathering his people under his wing. No prophet, king, or rabbi ever claimed to have that role because there is only one person who could rightly claim that role over Israel - God Himself. If Jesus didn't intend this to be a claim to divinity, he would have been an idiot for blaspheming.

      Yes, this is offtopic.

    19. Re:On the bright side... by Chalybeous · · Score: 1

      Well, it being confined to one box is one thing. That it's only affected one of a group of rsync servers is another - I think Debian's had to temporarily take some of their other web services down because different servers were affected. It sounds like the intrusion made less of an impact on Gentoo because of the nature of the box that was cracked.
      I was under the impression that Debian were still checking for interference with packages, too - but then, as I don't use Debian, I tend not to check related news too often.
      And it was only a small-scale outbreak. 20 affected users. So, maybe no comparisons, but it could've been a lot worse.

      --

      "It is dark. You are likely to be eaten by a grue." -- Zork

    20. Re:On the bright side... by Anonymous Coward · · Score: 0

      Hmmm... It's called a metaphor?

      The reason he said it like that is because he knew the message was radical. He was dividing father and son, brother against brother. When he told the society of the time that all men (and women) are brothers, and that we should all get along, he knew that was going to stir up trouble.

      The priests _were_ a bunch of vipers. They turned the temple into a money-mart and kissed the asses of the Roman overlords.

      For a modern example of what happens if you raise your voice against tyranny, Go to a Republican Rally and tell everyone you meet that Bush, Cheney, Ashcroft and Rumsfeld are a bunch of thieves and panderes, and that we should love our Arab brother and sisters.

      FW888

    21. Re:On the bright side... by Anonymous Coward · · Score: 2, Insightful

      Thats a lame excuse. If these so called "asshats" can crack a distro, so can other malicious folk, and so on. If a distro can be cracked, it very likely will be. You have to assume a malicious adversary when dealing with electronic security.

    22. Re:On the bright side... by Anonymous Coward · · Score: 0

      Exactly, mod this up. People generally do not go after high-profile targets unless they have a safety net, which usually means they have been "hired" for some malicious intent. "Asshats" with zero safety don't risk their real ass in jail. Corporate espionage is an old thing. How many people go around handicapping corporations for fun? Only a very tiny minority of pissed off ex-workers and such. The rest are paid for what they do.

    23. Re:On the bright side... by xenocide2 · · Score: 1

      High proliferation. High profile. People talk about how windows is awful with self propagating security exploits, but some forms of Linux can also be comprimised via a single point of entry. If done properly you could probably infect a wide swath of people and make it stick, similar to that old trick about compiling a login prompt and compiling the compiler.

      Of course, it doesn't take that much motivation to try something like this. I mean, why do people TK in counter-strike?

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    24. Re:On the bright side... by croddy · · Score: 1
      I wouldn't trust the .txt file's instructions, but I would be appreciative :-)

      and who here hasn't left something like that on the desktop of an open Win98 share on occasion?

    25. Re:On the bright side... by ghassanm · · Score: 1

      People knew how to get along prior. Christ was executed because he was an insurrectionist in the first colony to rebel against the Roman empire. Last I heard, treason was not looked upon so well in the United States.

      Statements like these degrade the level of civilization achieved in the ancient world. I wish a prominent pagan culture had survived so views like this wouldn't be so mainstream.

    26. Re:On the bright side... by ghassanm · · Score: 1

      Or considered "insightful" for that matter. How can such hackneyed statement be considered insightful.

    27. Re:On the bright side... by Anonymous Coward · · Score: 0

      I really shouldn't even bother, but you've got a few facts backwards. Christ was only insurrectionist with regards to the Sanhedrin and other Jewish bodies. We do not have any record that he supported overthrow of the Roman Empire. As far as the Romans were concerned, he had done nothing wrong.

      If you want to ask why Pilate had him crucified, it was because of his own weak political position, and the fact that he was afraid of revolt (on the part of the Jewish leaders), if he didn't. Thus the symbolic washing of his hands--as if to say, "I don't think this man is guilty, but I'll do what you want becuase I can't afford not to".

      Further, the accusations against him that the Jews fed to Pilate were insubstantiated at best. The real reason they wanted to crucify him was because of his claims to be the son of God (or, depending on your view--God himself).

      3

    28. Re:On the bright side... by Daniel · · Score: 1

      Whether it's because the cracker was sloppy or inexperienced, or because the Gentoo team have good server security, I can't say - but it seems they were pretty lucky compared to Debian.

      I'd imagine they were especially on-guard for breakins after the recent Debian incident. I would be if I were running a distribution's server (especially now).

      Daniel

      --
      Hurry up and jump on the individualist bandwagon!
    29. Re:On the bright side... by Anonymous Coward · · Score: 0

      Actually, there's no evidence this 'christ' fellow ever existed.

    30. Re:On the bright side... by ghassanm · · Score: 1

      Are you citing the bible on this issue? The trinity idea was an addendum, including Christ's divine lineage.

    31. Re:On the bright side... by ghassanm · · Score: 1

      The Romans ultimately accepted Christianity, while the Jews have not accepted Christ as the messiah. Who would you expect history to blame?

    32. Re:On the bright side... by El+Cubano · · Score: 1

      You could create the cure for cancer and some asshole would try to shoot it down just because it's there.

      Yup. Some researchers in Texas think they have discovered the cure for cancer. We have drug patents and HMOs in the US, which (in my eyes) is just as bad as shooting it down.

    33. Re:On the bright side... by Anonymous Coward · · Score: 0
      You could create the cure for cancer and some asshole would try to shoot it down just because it's there.

      Yeah, just imagine if Bill Gates funded the research team that did manage to find an all encompassing cure for cancer. You'd likely be in line ready to shoot him down.
    34. Re:On the bright side... by Anonymous Coward · · Score: 0

      Says you.

    35. Re:On the bright side... by Anonymous Coward · · Score: 0

      in other news, the GNU has now been hacked too with the same exploit that got debian. And hours after submitting it, it's still not on /. for some reason.

      security is a sham, it's worse than we imagined.

    36. Re:On the bright side... by TheAcousticMotrbiker · · Score: 1

      > What baffles me is why crackers go after targets like this.

      Because if you manage to stick a compromise in (say) their sshd undetected, then after a few months you will 0wn all gentoo boxen.

      And given the nature of gentoo, these will usually be boxen witha high band internet connection.

      Now imagine owning a few 1000 linux boxes all connected to a high speed internet connection.

      You could Ddos pretty much anything and everything .. or spam the entire world and it's dog 5 times over ... or lay waste to all the root DNS servers .. or ....

      The possibilities are endless

    37. Re:On the bright side... by Anonymous Coward · · Score: 0

      Are you insane! Tell you what, I'll break into your house at night, go through your things, and then leave a sweet note telling you how I broke in. Just after I scare the sh*t out of your wife and kids.

      What makes cyber breaking and entering acceptable here?!

    38. Re:On the bright side... by Anonymous Coward · · Score: 0

      Check out John 8:57-59.

      To claim that you existed before Abraham (2000 years prior) and to use the words "I AM" in the present tense is about as clear a way to say that one is God without actually saying it. Remember, when Moses asked God what his name was, he replied "I AM". The audience obviously got the point, since they immediately formed a mob and tried to stone him.

      Regardless of whether you believe that Jesus was God, you can't really say that he didn't make the claim... Even secular historians generally agree that as a whole the biblical accounts of what Christ taught are probably accurate.

    39. Re:On the bright side... by Anonymous Coward · · Score: 0

      Uh - what kind of evidence were you looking for - something along the lines of Lenin's tomb? There has to be as least as much evidence that christ existed than somebody like plato or aristotle - and nobody doubts that they existed.

      I'm sure many historians doubt that christ was God. I doubt that too many serious ones doubt that he ever existed in the first place.

    40. Re:On the bright side... by Rich0 · · Score: 1

      Uh - at worst that will delay it by 7-10 years. Arguably the cure wouldn't have been developed in the first place for another 30 years if it weren't for the patents. If these folks were the sort to do their work for free, then they won't patent it anyway, and you have nothing to fear...

      Besides, what shoots down most potential cures for cancer is that after the pharma company that sets out to develop it spends about $500 million in testing, they find out that it doesn't work after all. Of course, nobody pays them back for all those development costs that will never turn a product - hence the huge costs of the drugs that actually do work...

    41. Re:On the bright side... by Anonymous Coward · · Score: 0

      Rodney King? I thought we just kicked the crap outta him.

  20. wha? by Anonymous Coward · · Score: 0

    who uses rsync on internet connected boxes?

    doesn't that require rsh server?

    I believe a head examination is in order... better to rsync internally, then scp the new/different files out to internet boxes.

    1. Re:wha? by OlaL · · Score: 1

      It is possible to use ssh instead of rsh with "-e ssh".

    2. Re:wha? by Ryquir · · Score: 1

      RSH != Rsync

      Exerpted from the rsync man file:

      rsync - faster, flexible replacement for rcp

      rsync is a program that behaves in much the same way that rcp does, but has many more options and uses the rsync remote-update protocol to greatly speed up file transfers when the destination file already exists.

      Excerpted from the rsh man file:

      rsh, remsh, remote_shell - remote shell

      rsh connects to the specified hostname and executes the specified command. rsh copies its standard input to the remote command, the standard output of the remote command to its standard output, and the standard error of the remote command to its standard error. Interrupt, quit, and terminate signals are propagated to the remote command; rsh normally terminates when the remote command does.

      That said you clearly don't understand what place rsync has within gentoo so your idle speculation is pretty pointless.

  21. Linux vs M$ breakins. by Anonymous Coward · · Score: 5, Insightful

    break in to Debian, it was notices within 24 hours. Break into Gentoo, noticed in 1 hour. Break in to Microsoft, not noticed for MONTHS.

    1. Re:Linux vs M$ breakins. by Anonymous Coward · · Score: 0

      How do you know ?
      I would guess they have pretty good security checking, since Windows gets compromised by attackers a lot more often

    2. Re:Linux vs M$ breakins. by Anonymous Coward · · Score: 0

      Can you please provide an example of a Microsoft *break-in* (i.e. not security hole), that they did not admit to for "MONTHS"?? Please back up you claims instead of stating generalizations. These types of statements are typical linux fanboy/OSS zealotry and major reason why it's so annoying.

    3. Re:Linux vs M$ breakins. by espo812 · · Score: 2, Insightful
      break in to Debian, it was notices within 24 hours. Break into Gentoo, noticed in 1 hour.
      These are breakins to project servers - a handfull at best.
      Break in to Microsoft, not noticed for MONTHS.
      This was a breakin to a campus and national network of thousands of nodes. It's quite a bit more complicated and thus difficult to monitor everything going on on the Microsoft network than what happens on a few servers.
      --

      espo
    4. Re:Linux vs M$ breakins. by Anonymous+Chicken · · Score: 5, Funny

      Break in to SCO... priceless...

      --
      This signature is intentionally left blank.
    5. Re:Linux vs M$ breakins. by Anonymous Coward · · Score: 0

      Why do I never have moderator points when these come around. That's the damn funniest thing I've read all week.

    6. Re:Linux vs M$ breakins. by Anonymous Coward · · Score: 0

      The FSF breakin wasn't caught for quite a long time, linux apologist.

    7. Re:Linux vs M$ breakins. by kasperd · · Score: 1

      Break in to SCO... priceless...

      What would you do if you succeeded? Steal their source?

      --

      Do you care about the security of your wireless mouse?
    8. Re:Linux vs M$ breakins. by phy_si_kal · · Score: 1

      so many _own_ sco that they use it as a chat

    9. Re:Linux vs M$ breakins. by bondjamesbond · · Score: 1

      THAT.... was priceless.

    10. Re:Linux vs M$ breakins. by hattmoward · · Score: 1

      Let us not forget ye olde Half-Life 2, either! A spectacle of a compromise!

    11. Re:Linux vs M$ breakins. by parker2222 · · Score: 0

      Break into Savannah - 1 month Break into GNU - 4 months

  22. Firstly, get used to it by Nijika · · Score: 5, Interesting
    These things just happen. What I'm more impressed with is the detailed reports of the breakins. I mean you're going to have compramises, if you're on the Internet, try as you might to stop them dilligently. The important thing now is making sure you know when somebody's on the inside when they shouldn't be. And even more props if you make the knowledge public so that it gets harder and harder to break in.

    To those who aren't intentionally trying to troll.. and computer journalists;

    Yes, Linux servers can be compramised.

    No, the sky is not falling.

    No, it's not the end of Linux or open source.

    --
    Luck favors the prepared, darling.
    1. Re:Firstly, get used to it by Anonymous Coward · · Score: 1, Interesting

      Has anyone one put together a Knoppix-like distribution, self-contained on a cd, containing any rootkit/post-mortem analysis tools? i.e. chkrootkit, etc. This would allow you to take your system offline temporarily and check things out from a known-good baseline..

    2. Re:Firstly, get used to it by bersl2 · · Score: 1
      To those who aren't intentionally trying to troll.. and computer journalists;
      • Yes, Linux servers can be compramised.
      • No, the sky is not falling.
      • No, it's not the end of Linux or open source.

      Well, I was very scared about seeing more FUD-slinging when, for instance, I saw that Yahoo, on Monday, had on its front page "Major Security Flaw Found in Linux" or something like that. The kind of headline that blows things WAAAAY out of proportion. So while I agree with you, the perception may have been different (and still can; it's impossible to know where else this sensationalized story can crop up).
    3. Re:Firstly, get used to it by smittyoneeach · · Score: 1

      The presumptions going down the page seem to exclude the idea that somebody screwed up.

      Sure, the software flaws, but what if the compromise is human error, or even internal subterfuge?

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  23. heh by ed.han · · Score: 1

    perhaps you've noticed just how few posts there are to this thread so far as of this date/time stamp, compared to the date/time stamp of the story?

    ed

  24. Exactly. by twoslice · · Score: 5, Funny
    I am however glad to see that they took precautions.

    Now consider what would happen if the Windows update service was compromized and hackers managed to get past Microsoft's tight security. These update servers could be used for WMD's (Windows Massive Disruptions)...

    --

    From excellent karma to terible karma with a single +5 funny post...
    1. Re:Exactly. by hypermegachi · · Score: 1

      well at least no one has compromised windows update yet. and when an attack was expected microsoft did take neccessary precautions to try and stop it...ie putting up a linux machine :P

    2. Re:Exactly. by RogueProtoKol · · Score: 1

      That we know of, because obviously microsoft operate such an open policy of breaches!

      Oh wait...

    3. Re:Exactly. by cscx · · Score: 1

      I think MS digitally signs the patches on there.

      I could be wrong, however.

    4. Re:Exactly. by technoid_ · · Score: 1

      yeah, we all know that MS has never had its credentials swiped.

      http://lists.q-linux.com/pipermail/plug/2001-Mar ch /004405.html

      --
      Two wrongs don't make a right, but 3 lefts do - Lew of GO magazine
    5. Re:Exactly. by cscx · · Score: 1

      Uh, those certs expired over two years ago. Also shame on the cert authority for allowing something like that to even happen.

    6. Re:Exactly. by Anonymous Coward · · Score: 0

      Some windows update servers at times displayed 'Hacked By Chinese', much like many other windows servers on the net during a certain period of time.

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

      Why compromise Windows Update when you can have Windows computers compromise each other?

    8. Re:Exactly. by Anonymous Coward · · Score: 0

      Who needs to compromise it? Microsoft is doing such a good job screwing up Windows Update crackers really haven't been interested.

      Of course, faced with an update system that actually works, like the Portage tree, they must have felt a challenge was at hand :-)

    9. Re:Exactly. by RzUpAnmsCwrds · · Score: 1

      It would do nothing.

      Microsoft's updates are cryptographicaly signed. Nothing will install without the proper signature.

      The real threat would be if Microsoft's private key were compromised. Hopefully, Microsoft is not stupid enough to keep the private key on a system accessable to the internet. And, if they aren't, they deserve what will eventually happen.

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

      Have you ever wondered why there's a goddamn preview button there?

  25. Why is Microsoft doing this? by Anonymous Coward · · Score: 0

    First the kernel root, then Debian, then Gentoo.
    Geesh...Microsoft black-ops is getting around alot this past month!

  26. How about a logging trail by phorm · · Score: 4, Interesting

    Leading to the hacking machine? Fixing the compromises on major linux servers is one thing, but why has nobody mentioned finding the perpetrators?

    Anything in these logs on the source of the hacks? Probably another hacked machine, but perhaps it can be traced to a source.

    Also, in any package that were compromised or attempted at, what is being inserted? Perhaps we can use it as a honeypot to catch a hacker?

    Perhaps 2.4.23 should have a kernel allowance for a log that tells when somebody was trying to use the =2.4.22 exploit (or does it)?

    1. Re:How about a logging trail by Anonymous Coward · · Score: 0

      with my Log Delete v4, I can leave absolutely no trace at all! And that's because I know the admin password for the Internic server! Artaxerxes

    2. Re:How about a logging trail by japhering · · Score: 2, Insightful

      Because it is d*mn hard to prove who was actually sitting at the keyboard when the attack was successful. One hacker has already escaped jail time by simply claiming his machine was hacked by a third party without his knowledge

    3. Re:How about a logging trail by SuiteSisterMary · · Score: 1

      That, and when you trace the next hop to some machine in Korea, good luck getting somebody there to care.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    4. Re:How about a logging trail by Anonymous Coward · · Score: 0

      Read up on the attack and use a firewall ruleset. No kernel mods required.

    5. Re:How about a logging trail by Chyeburashka · · Score: 1
      Perhaps 2.4.23 should have a kernel allowance for a log that tells when somebody was trying to use the =2.4.22 exploit (or does it)?

      Just put real tabs where indicated. Enjoy.

      --- linux-2.4.23/mm/mmap.c.orig Wed Dec 3 13:36:22 2003
      +++ linux-2.4.23/mm/mmap.c Wed Dec 3 13:41:55 2003
      @@ -1041,8 +1041,10 @@
      <tab>if (!len)
      <tab><tab>return addr;

      -<tab>if ((addr + len) > TASK_SIZE || (addr + len) < addr)
      +<tab>if ((addr + len) > TASK_SIZE || (addr + len) < addr) {
      +<tab><tab>printk(KERN_ERR "do_brk exploit attempt. Submit story to /.\n");
      <tab><tab>return -EINVAL;
      +<tab>}

      <tab>/*
      <tab> * mlock MCL_FUTURE?
    6. Re:How about a logging trail by Anonymous Coward · · Score: 2, Funny

      Oh sweet, so now IPTABLES can mangle, drop, and reject SYSTEM CALLS?

    7. Re:How about a logging trail by gnu-generation-one · · Score: 1

      "Fixing the compromises on major linux servers is one thing, but why has nobody mentioned finding the perpetrators?"

      Like the sort of thing microsoft would do. Let's have a bounty...

      Serious answer, the FBI doesn't give a damn about crackers and never will. $5000 damages? Sounds like a public-funded private police force for big business to me.

    8. Re:How about a logging trail by Anonymous Coward · · Score: 0

      +1, Funny !

    9. Re:How about a logging trail by kasperd · · Score: 4, Informative
      Perhaps 2.4.23 should have a kernel allowance for a log that tells when somebody was trying to use the =2.4.22 exploit (or does it)?

      It doesn't have, but would be trivial to implement. Here is my suggestion how a patch for that should look (untested):
      diff -Nur linux.old/mm/mmap.c linux.new/mm/mmap.c
      --- linux.old/mm/mmap.c 2003-12-03 23:20:57.000000000 +0100
      +++ linux.new/mm/mmap.c 2003-12-03 23:23:22.000000000 +0100
      @@ -1059,8 +1059,12 @@
      if (!len)
      return addr;

      - if ((addr + len) > TASK_SIZE || (addr + len) < addr)
      + if ((addr + len) > TASK_SIZE || (addr + len) < addr) {
      + printk("do_brk: %d (%s): uid=%d euid=%d brk=%08lx\n",
      + current->pid,current->comm,
      + current->uid,current->euid,brk) ;
      return -EINVAL;
      + }

      /*
      * mlock MCL_FUTURE?
      --

      Do you care about the security of your wireless mouse?
    10. Re:How about a logging trail by phorm · · Score: 1

      I wonder how far you could go in order to prove that he was at the machine. Perhaps supoena the ISP for logs, if he was like a lot of people (including myself) he may multitask... something showing email or web-browsing occuring at the hack might indicate he was at the computer and using it... making the "I was hacked" theory a little less believable (not totally disproving it, but making it less viable).

    11. Re:How about a logging trail by Anonymous Coward · · Score: 0
      • Serious answer, the FBI doesn't give a damn about crackers and never will.
      They are also not interested in hackers, i.e. people who break into computer systems. In fact I'd guess they'd be more interested in going after crackers as software piracy tends to hurt companies more financially.
    12. Re:How about a logging trail by You're+All+Wrong · · Score: 1

      if ((addr + len) > TASK_SIZE || (addr + len) < addr)

      This is why the linux kernel has bugs.
      That's the "fixed" version.

      If I were to see that in a code review I'd ask for it to be changed.

      Who proposed that patch? I'd like to know who I'm insulting the programming skill of!

      Nope, I'm not saying it's won't work, but I'm saying that it displays a fundamental ignorance of the language which was the reason the old code had a bug in the first place. i.e. the guy who did the patch is nearly as thick as the guy who coded the bug in the first place.

      These guys aren't gurus, they're just keen.

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    13. Re:How about a logging trail by Anonymous Coward · · Score: 0

      Maybe I'm dumb but ... what is the problem with the patched code? To me it looks like a standard bounds check and check against integer overflow. Is there more to it?

    14. Re:How about a logging trail by You're+All+Wrong · · Score: 1

      There's a simpler way.

      Remember the mantra - all externally provided data is not to be trusted, don't do anything with it until it's been checked.

      The most important word there is "anything".

      For reference, I've been in realtime comms for half of my life, and I wouldn't expect more than 10% of the people I've ever worked with to get it just from the clues I've given. I was the "Bob the Bastard" of code reviews at most companies where I've worked.

      My message is that just because they're submitting code to the kernel doesn't mean that they're gurus. Don't put them on a pedestal, that's all.

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    15. Re:How about a logging trail by Anonymous Coward · · Score: 0

      My message is that just because they're submitting code to the kernel doesn't mean that they're gurus. Don't put them on a pedestal, that's all.
      And fair enough, too.

      [...] and I wouldn't expect more than 10% of the people I've ever worked with to get it just from the clues I've given.
      Given that it's not obvious then, could you describe the correct correction? I (same AC as before) still can't really see the problem as regards that isolated code fragment. Are you suggesting reorganising the function implementation to have internal firewalls, where execution progresses only if known-secure/safe preconditions are met (or if the data has been constrained appropriately to meet them)?
    16. Re:How about a logging trail by kasperd · · Score: 1

      Because it is d*mn hard to prove who was actually sitting at the keyboard when the attack was successful.

      You don't need to be sitting at the keyboard to perform an attack. Of course successfull attacks can be tricky as it will allow the attacker to change the logs. But if attempts against secured systems were logged, there is no way to avoid leaving some trail. Whether the trail leads all the way to the attacker is doubtful.

      --

      Do you care about the security of your wireless mouse?
    17. Re:How about a logging trail by Cooper_007 · · Score: 1
      Why says they used this kernel exploit?
      Seems they got in through rsync (see the rsync advisory).
      If you want to run an rsync server, this server has to run with root privs (or at least be started with 'em. I'm going from the manpage, so don't consider this authoritive) if you want any of the following:
      - Have it run chrooted
      - Have it listen on a port below 1024 (default=873)
      - Have it be able to set file ownership

      It seems rsync never gives up any privileges (even though it could for the first 2 I think...). So I'd give it a fair chance that as they went in via rsync, it was already running as root and so they didn't even NEED the kernel hack.

      Cooper
      --
      I don't need a pass to pass this pass!
      - Groo The Wanderer -

    18. Re:How about a logging trail by gnu-generation-one · · Score: 1

      "They are also not interested in hackers, i.e. people who break into computer systems"

      Defining hackers as people who break into computer systems is like defining footballers as people who kill their wives.

    19. Re:How about a logging trail by 42forty-two42 · · Score: 1

      What's wrong with it?

    20. Re:How about a logging trail by You're+All+Wrong · · Score: 1

      The situation was where there was a prior value, a fixed limit, and a user requested delta.

      The delta value is not to be trusted.

      Therefore compare the delta value against a value that can be guaranteed not to cause overflows:

      if(delta > (limit-value))
      { /* value+delta too large */ }

      The invariants for the system should include
      limit>=0
      value>=0
      limit>=value
      and therefore (limit-value) is a positive integer less than limit.

      If delta is permitted to be signed then checking that it doesn't fall below a minimal value (0 maybe) should also be done.

      If the original check had been that single condition rather than the expression which uses (value+delta), the original root exploit would never have occured.

      It's subtle, I'll grant you, as most people consider "if(a<(b+c))" to be the same as "if((a-b)<c)", etc. however, they are different.
      (in most common languages, ones with silent overflows)

      If you want to check the value of delta, then really check delta, don't check some value derived from it. I've seen this kind of mistake a hundred times.

      If you don't know what a train's destination is, you don't jump on it to see where it takes you in order to see if it's the right one, do you? Then don't operate on any variables until after you've checked the values. (It's not always possible, as not all expressions are reversible, but most common arithmetic ones are.)

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    21. Re:How about a logging trail by phorm · · Score: 1

      Sorry, the point was more that two servers were hacked in rather quick succession... I didn't know enough about the rsync vulnerability to post an extra comment on it.

      Really, though, you could have a logging/warning hook for both fixed kernel exploit and rsync vulnerability (or anything else for that matter). I'm quite tempted to modify my kernel with a hook that will allow the server to email me in the event of attempted compromise, a little extra overhead but not really anything significant..

    22. Re:How about a logging trail by fizbin · · Score: 1
      Nope, I'm not saying it's won't work, but I'm saying that it displays a fundamental ignorance of the language which was the reason the old code had a bug in the first place. i.e. the guy who did the patch is nearly as thick as the guy who coded the bug in the first place.

      And you're a pompous blowhard. The behavior of integer overflow operations on unsigned values (which is what addr and len are in this function) is in fact prefectly strictly defined in the C standard. Your "language ignorance" comment rings hollow - either that, or more charitably you assumed that one or more of these variables were signed, which means you go spouting off about code which you haven't read even though it's perfectly available.

      Now, that said, as a purely stylistic matter I would rewrite the above if statement as:
      if ((len > TASK_SIZE) || (addr > TASK_SIZE - len))

      This is basically because this form matches the bounds checking code elsewhere in that same file, and it's easy to see that no overflows are happening anywhere. However, your implication that the previous code just happens to work because of quirky behavior on the part of the compilers involved is out of line.
  27. Re:"Reasonably Confident"? by cayenne8 · · Score: 1

    Well, like in the article...it appears that only 20 people sync'ed with this box...and if you're worried...just do emerge sync again...and you will be directed to another, non-affected box and that should take care of any worries you might have.

    --
    Light travels faster than sound. This is why some people appear bright until you hear them speak.........
  28. This reminded me that.... by Anonymous Coward · · Score: 2, Funny

    I needed to upgrade my kernel and I'm guessing that by the now deathly slow speed of kernel.org, I wasn't the only one that remembered its time to get the latest stable. There should be a new name for this effect.

  29. just inevitable by gearheadsmp · · Score: 2, Insightful

    It's just inevitable that a high-profile Gentoo server got broken into. I use Gentoo for my desktop, but if I were in a business environment, I'd stick with Redhat or SuSe. Gentoo has always been an enthusiast's distribution. I personally hold Gentoo and Debian in as high regard as one another, and Gentoo is just my personal preference. Both have excellent package managers. Behaving a as a Zealot, whether for Debian, Gentoo, Slackware, or for a religion just makes you look like a blind fool.

  30. leads... by happyfrogcow · · Score: 2, Insightful

    Leads? I'll just check with the boys back at the crime lab. They got 3 more detectives working on the case. They got us working in shifts!
    -The Big Lebowski


    Seriously though, I would hope that organizations like Debian or Gentoo would have the brain power and tech resources to find a few leads that results in arrests. But why do I doubt that anyone will ever be arrested for any of these types of attacks?

    1. Re:leads... by crucini · · Score: 1

      Probably a vagrant set up a warez ftp on the box, or perhaps just used it as a spam relay and moved on.

    2. Re:leads... by aquarian · · Score: 1

      Seriously though, I would hope that organizations like Debian or Gentoo would have the brain power and tech resources to find a few leads that results in arrests. But why do I doubt that anyone will ever be arrested for any of these types of attacks?

      Unfortunately, organizations like Debian or Gentoo are easy targets because they might not have the resources to track down the villains. Companies like Microsoft or Oracle could easily hire teams of security experts to do this. At non-profits or smaller companies, there's no money for it.

    3. Re:leads... by happyfrogcow · · Score: 1

      well it's also not money that brings a person to work for a non-profit in the first place (usually). It's some agreement with the goals of the organization. How cool would it be if Debian could say, "yeah, we got hacked, but we caught the bastard ourselves and prosecuted."

  31. Why is this not on front page of Gentoo's site? by Artifex · · Score: 1

    Some of us don't subscribe to lists, or don't check our list mails often.

    --
    Get off my launchpad!
    1. Re:Why is this not on front page of Gentoo's site? by Anonymous Coward · · Score: 0

      Why not write it in the sky in case you don't check the site? FFS what do you want them to do, send Linus round your house to check you're ok just like Bill Gates does every couple of weeks?

    2. Re:Why is this not on front page of Gentoo's site? by g2boojum · · Score: 1

      It will be fairly soon. I've already written the
      text, but I have to wait until somebody w/
      website permission can post the release and
      regenerate the site.

    3. Re:Why is this not on front page of Gentoo's site? by Anonymous Coward · · Score: 0

      I havent been able to get to packages.gentoo.org for a bit over a day now. is this a related issue?

    4. Re:Why is this not on front page of Gentoo's site? by keesh · · Score: 1

      Nope. packages is offline because of a totally unrelated bug. Seems it has a memory leak somewhere that .23 isn't happy with, so it's offline 'till someone tracks it down.

    5. Re:Why is this not on front page of Gentoo's site? by g2boojum · · Score: 1

      Now up

    6. Re:Why is this not on front page of Gentoo's site? by Artifex · · Score: 1

      Thanks, g2!

      --
      Get off my launchpad!
  32. Re:Linux Insecurity by Anonymous Coward · · Score: 0

    Security goes beyond patching servers.

    Fortress of Insanity

  33. Faking a forensic trail would make little sense... by Kjella · · Score: 2, Insightful

    IANAH (hacker), but isn't the first thing you do when you break into a system to 'fix' the logs?

    Yes, but I think SOP would be to do a little Jedi handwaving "There was no breach". So if they have a good forensic trail, it's either a) real or b) fake. But why create a fake one, if they could have erased it properly? The only reason would be to hope that the box would be apparently fixed, but in reality still rooted. However, as the article said, after the investigation is done it'll be wiped and rebuilt, which is how it should be.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  34. Silver Lining... by Comatose51 · · Score: 1

    This just means Linux is hitting the big times... :-)

    --
    EvilCON - Made Famous by /.
    1. Re:Silver Lining... by frission · · Score: 1

      reminds me of that commercial that was on some time ago, where everyone is in an all staff meeting and then they disclose that they've been hacked....
      everyone celebrates
      (it's supposed to be "whoohoo...we're big now, we've been hacked") :)

    2. Re:Silver Lining... by MarkJensen · · Score: 1

      Errrr... Does this mean that when my Linux box gets taken out by a Blaster-clone worm, it is good news? ;) hehehe

  35. so what was the remote exploit that was used? by Squeezer · · Score: 1, Redundant

    so what was the remote exploit that was used?

    --
    Does the name Pavlov ring a bell?
    1. Re:so what was the remote exploit that was used? by scosol · · Score: 1

      Uhm- yeah?

      We're talking about a *kernel* exploit that requires local access!

      Curious there's no mention of how the box was accessed in the first place...

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
  36. Information wants to be free. by pete-classic · · Score: 4, Interesting

    Does anyone have an old, cached copy of the DNS record for rsync.gentoo.org?

    Diff it against what's out there now and we're only a quick trip to http://arin.net/whois from knowing who it was . . .

    -Peter

    1. Re:Information wants to be free. by KentoNET · · Score: 1, Informative

      Uhh...it's a round robin. An rsync rotation server was compromised remotely, and one suid file was found. This was not a DNS hijacking or anything like that.

      --
      "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    2. Re:Information wants to be free. by someonehasmyname · · Score: 2, Informative

      He's trying to figure out what unnamed company provided the hacked box.

      --
      Common sense is not so common.
    3. Re:Information wants to be free. by zeeboy · · Score: 1

      It's a DNS round robin : rsync.gentoo.org. 1200 IN A 206.169.166.57 rsync.gentoo.org. 1200 IN A 128.227.212.225 rsync.gentoo.org. 1200 IN A 132.207.4.160 rsync.gentoo.org. 1200 IN A 146.186.218.75 ..meaning that if you have a cached copy of this dns entry, you can look up the missing one and figure out who it is...

    4. Re:Information wants to be free. by boredMDer · · Score: 1

      He never said it was anything like DNS hijacking. He merely proposes an idea for finding out what server was compromised, and finding the owner of said server.

  37. Re:I KNOW WHAT HAPPENED by Anonymous Coward · · Score: 0

    ACs aren't credible. Don't believe a thing they say.

  38. Ask Microsoft? by Nijika · · Score: 1

    Go ahead, send them some mail. I'm sure they'll answer immediately.

    --
    Luck favors the prepared, darling.
  39. DARL! Turn that computer off and go to bed! by pair-a-noyd · · Score: 3, Funny

    "I told you before to stop playing and go to sleep!
    You just wait until your father gets home!"

  40. I have a theory... by Ann+Elk · · Score: 1

    ...and it is mine!

    But seriously, the people attacking these Linux servers have shown a great deal of talent. I suspect they've become bored hacking their way into Windows systems. What better way to "raise the bar" and really display one's abilities than to hack the (mostly) unhackable? I think this is (sadly) an inevitable fact of life.

    1. Re:I have a theory... by Anonymous Coward · · Score: 0

      That's it fanboy, put as much spin onto this as possible. The boxes at the center of the Linux world are being owned and you guys are still trying to make out that this makes Linux better than Windows. Here's a question for you:

      How many smaller profile Linux boxes have these guys already owned?

  41. Payback? by Anonymous Coward · · Score: 1, Interesting

    Someone seems to be trying to get a trojan in Linux, probably to give it a bad name. Maybe it would be a good idea to try to do the same to the possible perpretrator(s) before they succeed, so we can point to them when (not if, when) they manage to do it?

    (Note: this is only an hypotetical question. I'm not saying anyone should do it except as a thought experiment.)

  42. MS behind this? nah.. by Tumbleweed · · Score: 1

    ...it's Major League Baseball. Hey, look, it's Mark McGwire! Hit us some zingers, Mark! :)

    1. Re:MS behind this? nah.. by murphyslawyer · · Score: 1
      • Hit us some zingers, Mark!

      Not to be a Simpsons/baseball snob, but I believe the term is 'dingers'. Although now that you mention it, seeing Mark McGwire hit some Zingers would be fun too...

      --
      I ain't evil, I'm just good looking.
  43. Re:"Reasonably Confident"? by ivanmarsh · · Score: 0, Troll
    Microsoft Windows is the best desktop OS money can buy.

    That's true... you don't have to buy Linux.

  44. Question from non-hacker by selderrr · · Score: 0, Redundant

    In my book, peeps who make distros are as far from my computer knowledge as me from my mom. I simply can not understand how those websites can be hacked.

    Did 'they' really get shell access ? Or did they manage to upload a file into the tree ? Is it not possible at all to secure a server ? Slashdot, being one of the most known websites in nerd-universe must be under attack practically all the time I suppose; How come they can secure the site while Gentoo can not ? Is it so difficult that it requires a fulltime job from someone ? I always thought that it was enough to apply the current patches.

    All this leaves me with a very uncomfortable feeling. I have some websites running on linux servers (not mine) from rackspace providers. Should I be worried ?

    1. Re:Question from non-hacker by BrianPM · · Score: 0

      Is it not possible at all to secure a server ? Not completely, no. I sat down and talked with a guy that works at the NSA once about this stuff. Trust me, _any_ machine can be cracked. You can be on any arch, any OS, behind any firewall, any router, and you _can_ be hacked if the right people want in.

      --

      cloudcity.com
      Collectible Star War
    2. Re:Question from non-hacker by pagaman · · Score: 2, Informative

      Simply put, Gentoo didn't own the machine, there are lots of "rsync" servers that people use (like web sites, but used for downloading files only). Because the people who run gentoo don't own the server, they aren't responsible for it. All this leaves me with a very uncomfortable feeling. I have some websites running on linux servers (not mine) from rackspace providers. Should I be worried ? No! Gentoo is really a desktop OS. Your websites will not be affected. In fact from the sounds of things no one will of been affected, just the 1 server.

    3. Re:Question from non-hacker by Anonymous Coward · · Score: 3, Informative

      Is it not possible at all to secure a server ?

      The old adage goes something like: the only safe computer is unplugged, encased in concrete, and buried at a radioactive waste site.

      It sounds like the admins at this place were doing a good job, hence catching the break-in in 1 hour and having a log trail of what happened. The interesting thing will be when they find out the exploit used to get in. The Debian rooting caused a new kernel version, because the flaw was found to be in the Linux kernel. Hopefully we'll soon know what weakness the attacker used in this case, and another hole will be filled.

      Security is never perfect. You worry based on your risk level. The defence department is not allowed to put any classified information on a public network for that very reason. This is why Slashdot panics over Internet-Ready weapon systems, and electronic voting: they put something significant or dangerous at risk. On the other hand, if it's just your blog and photo album, then are you worried about a compromise?

      There's also exposure level. There are hundreds of people trying to break into Microsoft, or the DoD. The very best people will put their best effort into it. Smaller sites mostly get script kiddies. The tools they use are based on known exploits, which have probably already been patched. So unless you really offend someone, patching will keep most of us out of trouble.

      This break-in will cause one more security flaw to be fixed, and the world will be a little bit safer, for now.

    4. Re:Question from non-hacker by Richard_at_work · · Score: 4, Informative

      There are several methods with which you can gain access.

      1. Buffer overflows, or out of bounds issues, with services running on a server, eg ftpd, httpd, sendmail, bind (dns). This is where it is discovered to be possible to send malformed data to a service which the service is not expecting and wont deal with naturally. This sometimes results in the ability to send it some executable code which is read straight into memory and executed. Very easy to code around, very easy to detect, fairly easy to detect and very easy to exploit. This is the sort of attack that normally occurs against MS Windows et al, although sendmail, bind and various ftpds (wu-ftpd) have a reputation for being full of them.

      2. Password sniffing. This is where someone sits between a user and their box and sniffs network traffic, etiher getting a password unencrypted (normal ftp login, pop3 etc etc) or a weak hashed. Fairly easy to do, and you have a login to the system when you do. Not normally seen these days as ssh is used, and you should always have a seperate restricted user login for other services which do not encrypt passwords (imap, pop3, ftp etc).

      3. Issues with web scripts, that sometimes allow you to insert data into a database which the owner doesnt want you to do (or get a copy of his database) via SQL Injection attacks. Also it has been fairly common in the past to be able to get a copy of /etc/passwd by passing certain variables to a script run on a webserver, and from there you can attack user accounts. Also certain scripts have the error of allowing you to run system binaries, which again can be exploited. Always run your database daemon and your httpd in a chroot environment, with minimal access to system binaries, and always as a non privileged user.

      The biggest problem these days is that a lot of services run as root, because they need to to bind to ports lower than 1024. This was done so it allows you to "trust" services on those ports as being proper ones, rather than ones run by a normal user. A way around this is to run all services as a standard user, on port ranges above 1024 and bound only to IP 127.0.0.1. This means that your services are no longer on the standard ports, but you can get around this by using ipfilter, pf or another port fordwarding tool to forward all traffic on external priviledged ports to the services on 127.0.0.1, allowing you to run services as non priviledged users while retaining compatability with the outside world.

      It is VERY difficult to secure a server to near 100% levels, although you can get pretty close if you want to constantly be working at it. The goalposts change rapidly from day to day, and it can be hard to keep up. If you only run the services you really need, in chroot environments, and ensure that those services are well known services (apache for httpd, exim postfix or qmail for smtpd, pure-ftpd or pro-ftpd for ftpd, DJBDNS or bind 9 for dns) then you can be assured that there are trusted people looking at the source for exploits to fix as well as the untrusted people doing the same to exploit.

      Good logging firewall rulesets, an IDS (intrusion detection system), and a remote logging facility are all plusses in the fight.

    5. Re:Question from non-hacker by Anonymous Coward · · Score: 0

      That's bullshit. You've been watching too much 'Hackers' or something.

    6. Re:Question from non-hacker by Anonymous Coward · · Score: 1, Informative

      Why doesn't anybody talk about FreeBSD security lockdown levels? My friend was telling me something about this. Supposedly it's possible to prevent some files from being written to, even by root. And you cannot go to a lesser security level, you can only go higher (until a reboot).

      There is supposedly some stuff out there that allows finer grained permissions, e.g. running a service as a normal user, but saying that it can create an open port of this number once and only once (that would normally require root privaledges). Sort of like setuid but for specific tasks.

      Buffer overflows and holes will continue to happen. But we need to get to a stage where even if an attacker gets in, they cannot do anything. What is happening with SELinux?

    7. Re:Question from non-hacker by Anonymous Coward · · Score: 0

      What do you think of vsftpd?
      I've heard that that's one of the most secure FTP daemons, but you didn't mention it in your post.

    8. Re:Question from non-hacker by Richard_at_work · · Score: 1

      Why doesn't anybody talk about FreeBSD security lockdown levels? My friend was telling me something about this. Supposedly it's possible to prevent some files from being written to, even by root. And you cannot go to a lesser security level, you can only go higher (until a reboot).

      I was talking about security in general, so that is why I didnt talk about the BSDs secure levels. Basically they allow you to set bits on certain files, and then move into a higher secure level where you cannot alter those files, so you can protect things like system binaries or the kernel very easily. Also you can look at append only filesystems, great for logs as they do what they say they do, allow appending only to a file, you cannot change what is already there.

      There are a few kernel patches out there that give root more and more control over what his users see and do, and limiting system calls is one of those. OpenBSD contains things like this by default.

      SELinux was closed last I heard, because of an internal conflict between the NSA and other govmnt depts. It was a nice hardened kernel, and you can still get ahold of it if you want it.

    9. Re:Question from non-hacker by viperblades · · Score: 1

      you can secure a linux server to a point, but the most important thing is logging and remote logging. instead of logging remotely over the network have a log box with a serial port or printer port. then just have an app that listens on that port and can only write new data to the logs. (true this application must be secure but it could be audited) this way even if the attacker knows your remotely logging all he can do is try to flood your log box with data. (you SHOULD have a script that monitors the free space on all your servers so you would get an alert)

  45. Seperate Log Server by EXTomar · · Score: 4, Informative

    There is no sure thing in security but there is a simple step to make things a bit more reliable for logging.

    If you really have a serious system where you want detailed logs you keep the logs for that system off that machine. Sure the machine that is logging could have been comprimized as well but that is twice as much work. Now you have to hack the machine but also the logger to erase the intrusion event.

    In fact one of the things I've seen done is that events are logged on the machine and the logger. The idea was to provide not only redundant logging but also provide a front for hackers. A hacker would see the local logs and be too busy doctoring up those logs to check to see if there is an external logger.

    In any event, the logging Gentoo did looks complete enough. They claim only 20 users did a sync against the server during the hour it was online and comprized.

  46. 'Cause of the 'severity' by Nijika · · Score: 4, Insightful
    In OUR community this is a major thing. For everyone else on the planet this crime rates just under Grandma Smith's lawn gnome being stolen and then used in a bizarre series of cross country photos. Even I tend to forget this often, but then I remember.. *sigh*.

    PS, full props for the Lebowski quote!

    --
    Luck favors the prepared, darling.
    1. Re:'Cause of the 'severity' by Anonymous Coward · · Score: 0

      that would be cross world photos to you ;-) and Pa's gnome - whoever heard of Granma mowing the lawn, let alone decorating it with gnomes!!

    2. Re:'Cause of the 'severity' by Zutroi_Zatatakowsky · · Score: 1

      Ooooh, an Amelie Poulain reference! On Slashdot! I can now die in peace. :)

      --
      All Hail Discordia. Hail Eris. Fnord.
  47. Re:"Reasonably Confident"? by Trigun · · Score: 1

    I'm not sure, but I think that was the inference.

  48. Re:"Reasonably Confident"? by RedHat+Rocky · · Score: 2, Interesting

    This would be fine assuming no software was emerged, if one of those 20 happened to 'emerge -u system' and there WAS packages amiss, that would be bad and not cleaned up by an emerge sync.

    Would be a good thing to see if notifying those 20 people was possible.

    --
    Anything is possible given time and money.
  49. laziness saves the day by thraxil · · Score: 1

    luckily, i've been too lazy to 'emerge sync' lately...

    --
    Smokey the Bear says, "Strip mining prevents forest fires!"
  50. The Empire Strikes Back by Anonymous Coward · · Score: 0

    You know, this is like TESB -- we're running high after finding and exploiting a vulnerability in the Death Star, we're partying, medals are being awarded, and R2's ok...

    Then The Empire goes after the rebels. Hoth is fscked, Han is carbonite, and Luke's missing a hand.

    After having a field day with all the Windows viruses/worms, we're getting highly publicized compromises to OSS. The conspiracy theorists are pointing to a possible Jabba-like "hacker bounty" to reel in OSS. Is it the SCO tractor beams? Is it Fett freezing distros in carbonite? Is it the press cutting up the limbs of the Open Source movement?

    ESR, it may be time to don the jedi outfit again. The rebels need their leaders out for at least a morale boost.

    1. Re:The Empire Strikes Back by Anonymous Coward · · Score: 0

      Ha ha. ESR is no 'leader'. He's a self-righteous jerk who talks far too much shit.

  51. I remeber this by 0xA · · Score: 1
    No he's not being a twit, this did happen. Somebody got in via an employee's VPN connected machine and it took them a while to notice. I'm not sure it was months however.

    If I can find a reference I'll post it.

    1. Re:I remeber this by pantherace · · Score: 1

      I think it was something like 6 months. And it was traced to Russia, but no further, and they apparently got the XP source code.

  52. Re:"Reasonably Confident"? by nearlygod · · Score: 1

    Assuming that OS X is free with the purchade of an iWhatever, I agree as well.

    --
    The Tools Of Ignorance wanna be a tool?
  53. I was with you.. by msimm · · Score: 1

    right up to the word smart.

    n0\/\/ i ph3@r j00. ;-)

    --
    Quack, quack.
  54. Doesn't surprise me... by Anonymous Coward · · Score: 0, Funny

    ...nsync gets compromised up the backdoor all the time. It was only a matter of time before rsync got a peice of the funky butt lovin'.

  55. gpg sign the bloody emerge files? by tomstdenis · · Score: 4, Insightful

    Why not?

    You take the keys of the developers [or even a cvs key] and then sign all the emerge files. There are only like 2000 new ones a day so at about 50ms a signature [for a really slow box] that's only 100 seconds of time [two minutes not much].

    That way if the end user downloads compromised emerge files they could detect them.

    Damn... I'm like a genius.

    --
    Someday, I'll have a real sig.
    1. Re:gpg sign the bloody emerge files? by keesh · · Score: 3, Informative

      This one's been in development for a while, and will be going live soon probably. Read GLEP 14,

    2. Re:gpg sign the bloody emerge files? by avenj · · Score: 1

      Actually this has been in the works (except just signing the Manifests - which is why Manifests were created) but hasn't had enough push behind it to actually finish the important implementation details

    3. Re:gpg sign the bloody emerge files? by Anonymous Coward · · Score: 0

      "Why not?"

      Because drobbins is a git. Someone else though of signing the ebuilds first, so instead of acknowledging the other person's good idea he decided to drag his feet and hope everyone forgot about it. Oops.

    4. Re:gpg sign the bloody emerge files? by seraph93 · · Score: 1
      but hasn't had enough push behind it to actually finish the important implementation details

      Maybe whoever is behind this was just trying to provide that "push"...

      --
      Ph-nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.
  56. I still say we have to adopt UNTRUSTED COMPUTING by pair-a-noyd · · Score: 0, Troll

    In that no computer trusts any other computer, ever for any reason.

    You're guarding an armored car. Another man approaches you wearing all the correct uniform and regalia, he evens looks familiar to you, you've seen his face at the armored car company. He has the password of the day.
    Can you REALLY trust him? How do you know that he's really who he says he is? And even if Bob the guard really is Bob the guard, how do you know that Bob the guard hasn't just all of a sudden decided to slip a few $$ in his pocket when you aren't looking or just knock you out from behind and take off with a sack of money?

    Traitors ALWAYS work from within.
    Who do you trust?
    Do you trust people you've never met with your computer security or do you take it upon yourself to handle your own security.

    If one computer gets comprimised in a "trusted computing" system, the game is over. Don't trust anyone or anything.
    Machines are easy to fool, they can't think.

    The only SECURE computer is one that is melted down into an ingot of pot metal. THAT computer can't be comprimised.

  57. Easy to use IDS? by petabyte · · Score: 1

    Anyone want to recommend an easy to use IDS to put on a stand alone workstation? When I move again and I deploy a BSD router, snort will be going on that machine. Until then what would this group suggest I put on this stand alone workstation that will require the minimum amount of headaches to setup/use?

    Thank you.

  58. What OS was the compromised box running? by Zapdos · · Score: 4, Interesting

    One of the servers that makes up the rsync.gentoo.org rotation was compromised. This box is not an official Gentoo infrastructure box and is instead donated by a sponsor. The box provides other services as well and the sponsor has requested that we not publicly identify the box at this time.

    While it may run Gentoo, it is not stated as such, and could be very well be something else.

  59. Not as big as previous posters make it sound. by jmanning · · Score: 5, Informative

    To correct a few misconceptions in the previous comments.

    It was not their server that was compromised, just a third party server in a round robin rotation. They don't own it, they don't maintain it - just someone else who donated server space.

    The primary or master server is not accessible to users, it was not compromised, and so none of the original source files had a chance to be changed.

    Only the 20 users that synchronized to this server even have a tiny chance of getting bad files. Having everyone sync now that this server is out of the rotation will immediately fix the problem.

    Full disclosure 24 hours later. I give them a lot of credit for such a quick response and disclosure. This is very, very minor.

    ~J

    1. Re:Not as big as previous posters make it sound. by Otter · · Score: 1
      Yup, I resynced and games-fps/doom3 isn't there any more. I wonder what I just emerged? The hard drive has been thrashing for hours, but that didn't strike me as anything unusual...

      Hey, a new gcc update!

  60. Re:What OS was the compromised box running? by Anonymous Coward · · Score: 1, Informative

    NetCraft reports Linux and Apache (Red hat version). http://uptime.netcraft.com/up/graph?site=rsync.gen too.org

    Fortress of Insanity

  61. Conspiracy, FUD, and Open Source by Jumper99 · · Score: 5, Interesting

    So I've been lurking around here long enough to spot certain trends. (Warning: generalizations ahead)
    OSS advocates love to hate Windows
    OSS advocates gloat when a new hole turns up in Windows
    OSS advocates point to the number of worms, virus, etc in Windows and say, "Never us"

    Then several OSS distros have a security breach in a short space of time.

    OSS advocates respond with "Must be a conspiracy against us by some evil entity", "Hey, look how quick we caught it", "It would have been much worse with Windows".

    Time to face facts gents. Windows is attacked FAR more than OSS. Why? Well, yes, it is full of holes. But downtown Philly is riddled with abandoned houses with no locks on the doors but they never get broken into. Why? No value in doing so. Not enough damage, headlines, misplaced glory, etc. But the main reason is that it is the dominant OS out there. I fear that we will see more and more attacks against OSS with it's growing popularity. If we all get our wish and 'nix takes over Windows dominant market position and is running on 90% of desktops, you will most likely find it a target for constant attacks like Windows has now.

    We all know in order for 'nix to make it to the desktop, it has to become WAY more user friendly. Can't have Grandma trying to recompile the kernel now can we? User friendly unfortunately translates into users being able to do things that comprise security. Like opening attachments, downloading Trojans, etc. Then the great security built into the OS goes right out the window. no pun intended).

    So before you all start crying about conspiracies, et al, just remember that we all may be victims of our own push to make the 'nix stuff more popular. By bragging about how secure it is, we just may be attracting the type of attack that is more sophisticated then the script kiddies attacking Windows. I imagine it's cool to brag to your friends that you broke into a Windows box. I imagine it's much cooler to brag that your rooted a Linux distro. Badge of honor and all that.

    --
    The opinions expressed here are not mine, but those of these dang voices in my head.
    1. Re:Conspiracy, FUD, and Open Source by oo_waratah · · Score: 2, Interesting

      While I don't disagree with the sentiments there are some fundamental problems with your argument.

      Linux/Unix is fundamentally secure, windows is fundamentally open designed as a disconnected workstation and slowly being secured. This is NOT Microsofts fault for marketting reasons they have to move the code base slowly or there are too many problems.

      The value in breaking into Windows is a staging point for other attacks. Kind of like a window above a presidental convoy. You can bet those downtown lockless doors would be secured if the head of state of anything wanted to drive through it. The point is that Internet snipers can hide anywhere.

      Gandma and gradpa will not compile the kernel. They will use the standard upgrade path of binary packages. They will trust the source computer has not been compromised as Microsoft users trust the Microsoft site is not compromised.

      There will be more holes found in Linux / Unix as they become more known. The reason, simply is honesty, FOSS sites report it and commercial entities hide it. I am not pointing at any one company it is a general truth.

      The line I like seeing with this breakin is that this was noted by a checking program. This is what we like to see, expect a break in and buy a burglar alarm. (Also remember a burgler alarm can be comprimised!)

    2. Re:Conspiracy, FUD, and Open Source by perf_monkey · · Score: 1

      Good Comments!

      My post just went up a bit after yours (look down the tree from yours) but it some similar points. Why is it that everytime a security exploit comes up for Linux, we have to point to Windows?

      I dislike the security inherent in Windows as must as the next sysadmin but one has nothing to do with the other. If there is a problem with the Linux kernel or another open source component, then it would be more productive to focus the discussion on the design and overall assumptions of the security process.

    3. Re:Conspiracy, FUD, and Open Source by greg_barton · · Score: 1

      But downtown Philly is riddled with abandoned houses with no locks on the doors but they never get broken into.

      I guess you haven't gotten your crack fix recently. :)

      And, if they have no locks, how do you know there are no breakins?

      By bragging about how secure it is, we just may be attracting the type of attack that is more sophisticated then the script kiddies attacking Windows.

      As our president is so fond of saying, "Bring 'em on!"

    4. Re:Conspiracy, FUD, and Open Source by Wehesheit · · Score: 0

      Predicting the future?

      There will be more machines with linux installed and I'm 100% sure there will be more exploits found but I don't believe that with increased usability comes more security holes.

      My grandma and my mom both run mandrake 9.1 (mostly because of the solitaire/tetris etc.. games included in KDE/GNOME) and they'd never once been infected by a virus or even had a crash. My mom was previously running mandrake 8.2 and updated to 9.1 HERSELF, just by popping in the cd's and rebooting like it said on the box.

      Linux is NOT 100% secure and probably never will be (nothing is 100%) but to say it will turn into windows as more people use it is baseless and untrue.

      --
      This P.I.G. will walk on the water, This P.I.G. will walk on the sea, This P.I.G. will walk whereever he wants.
    5. Re:Conspiracy, FUD, and Open Source by Beryllium+Sphere(tm) · · Score: 1

      >But the main reason is that it is the dominant OS out there.

      In some areas, but consider Apache vs. IIS in terms of number of deployments and number of exploits.

    6. Re:Conspiracy, FUD, and Open Source by Darth · · Score: 4, Insightful

      Linux/Unix is fundamentally secure, windows is fundamentally open designed as a disconnected workstation and slowly being secured. This is NOT Microsofts fault for marketting reasons they have to move the code base slowly or there are too many problems.

      I'm going to disagree with the absolute statement that this isnt Microsoft's fault. I agree that the design of Windows not taking into account network security issues at it's inception is not their fault. it wasn't on the radar as an issue facing personal computers when windows was originally written.
      However, building products you are going to market as a server that don't take into account network security is absolutely their fault.
      Building applications that are designed to be used across a network (like IE and Outlook) and not seriously considering the security threat to the system that they create is their fault. Actively adding features to those applications that hamstring any attempt to secure the machine is their fault.
      Claiming your stuff is secure while trying to crush anyone who exposes that it isnt; that's their fault too.

      So there's plenty of security related issues with Microsoft that absolutely are their fault.

      Gandma and gradpa will not compile the kernel. They will use the standard upgrade path of binary packages. They will trust the source computer has not been compromised as Microsoft users trust the Microsoft site is not compromised.

      This is a great reason why security issues with computers used in the upgrade path should be disclosed quickly and the clean up process should be transparent.

      The honesty of OSS groups to disclose information about vulnerabilities is one of it's strengths.

      --
      Darth --
      Nil Mortifi, Sine Lucre
    7. Re:Conspiracy, FUD, and Open Source by Anonymous Coward · · Score: 0
      • Linux/Unix is fundamentally secure, windows is fundamentally open designed as a disconnected workstation and slowly being secured.
      Actually there have been server and workstation editions of Windows NT (which was later 2000 and XP) since its conception. The security model in NT is more fine-grained than Unix-style systems too.

      The problem is not with Windows' security model per se, it is badly written code that allows such exploits to happen, and bad decisions in how to utilise the security model.
    8. Re:Conspiracy, FUD, and Open Source by __past__ · · Score: 1
      Linux/Unix is fundamentally secure
      Bullshit. The classic Unix model system is completly insufficient to build secure systems, one of the best examples of the worse-is-better approach of "the Unix philosophy" and how this will always come back and bite you. We badly need to get away from stuff like a pure uid-based permission system and, more than anything, from the almighty root.

      Even Windows is better than that, if it weren't for the many implementation bugs, the braindead default configuration and the fact that most app developers simply refuse to use it properly, out of sheer ignorance I guess.

      Fortunatly, there are projects trying to overcome the Unix limitations, like SELinux, the TrustedBSD project (mostly merged into FreeBSD 5), Trusted Solaris (which will be standard functionality in Solaris 10) etc. However, this stuff is not widely know, hard to set up and just doesn't feel native to a Unix system. But they will surely help until better OSes, like Eros for example, are ready to use.

    9. Re:Conspiracy, FUD, and Open Source by oo_waratah · · Score: 1

      Fundamentally secure.

      It requires sign on

      It provides for levels of security and automatically configures them.

      Generally the default is to NOT install unnecessary software.

      Under a standard sign-on a user is unable to overwrite the operating system or fundamental tools.

      Programs installed generally install with a minimum set of options and you turn on additional options to enable them, rather than turn them off.

      Now if you want to talk security tools, look to RACF and the mainframe for how to do it really well. However the USER/GROUP works well if you are willing to think about it. If this does not work then ACL's can provide that extra level. User/group security is certainly not a security "hole".

      I have yet to see a system without an all powerful user (windows admin, root, mvs systems programmer, ...). Like you said if the system is used badly it is insecure, for windows, for Unix, for anything. The trick is whether security was premise or bolt on, default or manually configured afterwards.

    10. Re:Conspiracy, FUD, and Open Source by hawkstone · · Score: 1

      ...
      Then several OSS distros have a security breach in a short space of time.

      OSS advocates respond with "Must be a conspiracy against us by some evil entity", "Hey, look how quick we caught it", "It would have been much worse with Windows".


      There's a fundamental distiction here, isn't there? I mean, the servers that host the distributions have been compromised, right? That's like saying Microsoft's source code repository got hacked, not like saying a MS box got hacked.

      The reason for a conspiracy theory is that in two months, the source code repos for three different distributions have been hacked. Reserving judgement on the validity of this theory, the theory would hold the same amount of water even if the servers were running Windows Server 2003.

  62. -1 Troll by Anonymous Coward · · Score: 0

    Moron moderators

  63. Not slackware... ! by morzel · · Score: 1
    Hey, there ARE advantages in not having a decent packaging system ;-)

    Almost all slackware users (slackies?) I know do their upgrades by doing the 'configure;make;make install'-mamba baby!

    (for the humor impaired: this was a joke -- albeit a lousy one from a slackie)

    --
    Okay... I'll do the stupid things first, then you shy people follow.
    [Zappa]
  64. Re:Debian, Gentoo.... who's next? - OpenBSD ??? by MerlynEmrys67 · · Score: 1

    Would be a prime target if you could take down www.openbsd.org - of course with one remote exploit in 7 years. But it would be a claim to fame

    --
    I have mod points and I am not afraid to use them
  65. Re:Switch to Mandrake. by Anonymous Coward · · Score: 0

    I wouldn't use GOATSE Linux if I were you. I hear it has a major security hole in the default install.

  66. MOD PARENT UP by Anonymous Coward · · Score: 0

    What's up with the moderators today?

    Pool of idiots I tells ya

  67. Re:I still say we have to adopt UNTRUSTED COMPUTIN by flafish · · Score: 1

    Guess you never've heard of a cutting torch? ;-)

  68. It must be all that SYS V code... by i_r_sensitive · · Score: 1

    that was stolen from SCO....

    --
    "Talk minus action equals nothing" - Joey Shithead, D.O.A.
    "Talk minus action equals /." -
  69. Given the chance.. by msimm · · Score: 1

    How many people would bend the law in order to make real money? How many spammers are out there? Do you think that the only members of our population with questionable morals are in the bulk-mail industry? Think about it. If all you had to do was wire some kid in Croatia some capital, not actually hurt anybody? I'm not saying it would work, but there are bound to be some unscrupulous people in the tech industry somewhere, right?

    --
    Quack, quack.
    1. Re:Given the chance.. by molafson · · Score: 1

      How many people would bend the law in order to make real money?

      I'm not saying it's beyond the realm of possibility that there are mercenary crackers out there. I just think they're far outnumbered by crackers who are in it for the glory.

      Besides, it seems that these days the best way for black-hat hackers to make money are (a) blackmail by threatening DDOS attacks against corporate websites, and (b) creating trojans to install zombie SMTP servers for spammers.

  70. Re:I KNOW WHAT HAPPENED by Dylan_t_p · · Score: 2, Insightful
    "I KNOW WHAT HAPPENED (Score:-1, Troll) by Anonymous Coward on Wednesday December 03, @03:01PM (#7621231) I know one of the gentoo developers and he has logs of the attack, and the attacker was using a compromised machine in Saudi Arabia for the hack. He actually left a trail in some of the files to say things like "jihad vs. gentoo and america" etc." looks like another islamist plot to overthrow linux

    MAN! if the terrorists are in on this, and since this is obviously a microsoft plot microsoft must be terrorists....... AH second hand information, "i know this guy who knows this guy who works at this company and this is what he said" :) by the way i know this is a troll but it's one of the funnier things I've seen today

  71. OMG! by msimm · · Score: 1

    Y0Ur 0n3 0f 7H3M!

    --
    Quack, quack.
  72. Gentoo! by PatrickThomson · · Score: 5, Funny

    rooted 1% faster than a binary install!

    With apologies to Torne, from whom I stole this quote.

    --
    I am one of many. My idea is not unique, nor do I expect my voice alone to sway you. I speak in a chorus of opinion.
  73. zealots? by Yggdrasil42 · · Score: 1

    Make me almost want to say:
    "where are all the Gentoo zealots now?"

    but being a Gentoo user myself, I'll just keep my mouth shut.
    Ahhhh, the irony...

  74. Wimps. I'll be really impressed... by alispguru · · Score: 1

    ... when somebody compromises Darwin.

    --

    To a Lisp hacker, XML is S-expressions in drag.
  75. They asked for it... by KentoNET · · Score: 1

    [15:49:30] hey all you -v users! quote me! quote me! i wanna be famous
    [15:50:05] oh, btw, all you anonymous -v people, the server was running minix!
    [15:50:06] ok, quote me: the box was running DOS. yes, DOS! dos 6.3 with a tcp stack stolen from os/2

    --
    "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    1. Re:They asked for it... by KentoNET · · Score: 1

      Err...The nicks in respective order are ciaranm, ciaranm, and bazik...

      --
      "You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
    2. Re:They asked for it... by bazik · · Score: 1

      Oh nooooo, you slipped secret info!! :D

      --


      --
      One by one the penguins steal my sanity...
  76. Uplink by meowsqueak · · Score: 1

    Hey, they told me Uplink was just a game!

  77. Re:"Reasonably Confident"? by BrianPM · · Score: 0

    That's not what Matthew J. Szulik says.

    --

    cloudcity.com
    Collectible Star War
  78. When, not if by Midnight+Warrior · · Score: 4, Insightful

    IDS is placed on a system to follow an attack. Audit trails on sensitive machines reveal all commands executed, to the detail you desire.

    Here is the point. Bruce Schneier says that the important part of security is not that you were compromised, but rather that you can react within a time frame to keep the damage to acceptable levels. If you can tolerate having your system compromised for weeks, don't invest in a lot of security. The short response time (2 hours at 11pmEST) here indicates that the Gentoo administrators care about responsiveness enough to check on it frequently.

    When the CVS gateway to Bitkeeper on the Linux Kernel was compromised, the developers of Bitkeeper were able to show that they care enough about security that they invested in many checks and balances that caught the error immediately. Since then, Bitkeeper developers, interested in protecting their good reputation (which is VERY difficult to replace), are considering even more drastic measures.

    As a bonus, some cracker spent a good few days or weeks writing this exploit. We get to keep it and deploy the solution with little hassle. And the compromised system, because good security practices are in place, was mitigated to minimize damage.

    Read Schneier's book Secret and Lies to find out how security is really a process. Yes, I know it's a plug, but I just thought the book hit-home to the real point - "When, not if" you get compromised.

    Several other posts here hint that the world will think less of Linux for this. False. True CIOs should see that Linux has the tools to completely identify and contain attacks. Every CIO knows attacks cannot be stopped, but rather they must be contained to acceptable levels.

    1. Re:When, not if by Anonymous Coward · · Score: 0
      • As a bonus, some cracker spent a good few days or weeks writing this exploit ..
      Wrong. The word you are looking for is "hacker". A cracker breaks copy protection on software.
  79. Re:"Reasonably Confident"? by Jesrad · · Score: 1

    And MacOS X comes bundled with the Mac.

    --
    Maybe we deserve this world ?
  80. Debian vs. Gentoo... by EvilTwinSkippy · · Score: 2, Insightful
    I know I'm going to be modded into the basement, but does anyone else note the extreme difference between when the Debian server was rooted and the Gentoo? Gentoo knew in an hour. They had all of the monitoring tools installed. They even had a list of everyone who had pulled from the machine, and a rough idea of what was done and not done on the server.

    Good luck catching your buglar. I want to know how to patch my box.

    --
    "Learning is not compulsory... neither is survival."
    --Dr.W.Edwards Deming
    1. Re:Debian vs. Gentoo... by Fubar420 · · Score: 2, Informative

      Not to criticize (and I am a Deb fanatic, so excuse if i get a little zealous), but the box wasn't gentoos'

      Don't get me wrong, they did a _FANTASTIC_ job catching the break-in, but at the end of the day, there's a good chance the IDS was installed by the people who OWNED the box, and not Gentoo proper.

      While I'd hope and expect the box was running gentoo, there's no evidence of this, nor of it having been Gentoo's work that caught on.

      I fully believe in full disclosure of break-ins (though a delay on revealing vuln's is fair in some MAJOR cases, it should still be done), and they did everything they should have.

      Debian caught it within 24 hours, GNU within a month, MS's last breakin that i can recall, took months.

      It's not about what OS, but the administrators.

      If your admin doesn't take proper precautions for a highly visible boxen, then these things will happen.

      Sure the breakin likely could've been prevented had they been uuber up-to-date, but really, the problem is inherent with OSS

      Again, I disclaim. OSS is a Very Good Thing, BUT, because of this, vuln's are posted far more often than with CSS (no, not style sheets).

      Because of that, the patch-turnaround time is much smaller with OSS, and we as admin's who love our linux/bsd/OSX boxen MUST stay on top.

      I dont have a regimented update schedule for my personal box, even though I should, but because vulns' are usually found and widely publicized very quickly in this world, the users do have to take more precautions.

      If nothing else, this indicates a need for a clearing house (other than ones that tend to be used exclusively by those that seek to find vulns), with links to patches, packages, etc for various distros could be a very good thing.

      Security.debian.org is a good example, but as recent times have shown, even debian isn't perfect (as much as I tell others it is :-D)

      Love your distro, tend to your boxen, but admin like you could be hacked tomorrow. As gentoo/gnu/debian/MS/*BSD have demonstrated in the past, it can and WILL happen to your box.

      I still see regular hist on apache for old IIS vulns. People wouldnt try it if there werent still vulnerable people, and the worms couldnt try it if they'd ever been cleaned properly.

      It's not about OS.
      It's not about vulns.
      It's not even about the hackers.
      It's the admin's who defend these boxes.

      So to the recent distros, Deb & Gentoo alike, I salute the admins who have done a great job keeping the public informed to potential problems. I only hope that when I finally get out of this bloody school, I'll be half the admin that these guys have working for them.

      --
      -- (appended to the end of comments you post, 120 chars)
    2. Re:Debian vs. Gentoo... by You're+All+Wrong · · Score: 1

      "Debian caught it within 24 hours"

      However, they left the system rooted for longer than that as they wanted to capture forensic evidence and didn't want to spook the attacker.

      The "friend of Debian" that was hacked at the same time as Debian was in an insecure state from wednesday night until the friday. Debian's sysadmins were working with this "friend", and I can only assume that the timelines were within minutes of each other for each stage (the rootings/oopsings were at almost identical times on the different systems for example).

      "I salute the admins who have done a great job keeping the public informed"

      The funny thing is that they couldn't give too much information away too soon, as they wanted to set up their own sniffers and stuff, to see if they could actaully trap incoming hacker connections. The info within this secretive other system was much more informative than the official Debian story, I can tell you ;-)

      YAW.

      --
      Your head of state is a corrupt weasel, I hope you're happy.
    3. Re:Debian vs. Gentoo... by Anonymous Coward · · Score: 0

      They have a list of who pulled? Isnt that a huge privacy concern? Why should we trust Gentoo with the knowledge that we got stuff from them?

  81. how is this insightful? by Anonymous Coward · · Score: 0

    These are breakins into closely monitored machines.

    The other (MS) breakins were essentailly equivalent to penetrating a firewall, not compromising a server.

    1. Re:how is this insightful? by Anonymous Coward · · Score: 0

      yeah, since we all know that once past the firewall the ms server is all hot and waiting :-D

      as Bill just said, it's all about the fire - and firewalls - with windows.

  82. Look at this in a positive way by perf_monkey · · Score: 4, Insightful

    Let's face it, no OS is 100% secure. Operating Systems that are more secure than others still need to be on their toes. One security exploitation on a Linux box can still be as dangerous as a thousand (an underestimated ratio I'm sure) exploitations on a Windows box. However, I will take the body of security knowledge surrounding an OS to be as valuable as the initial security design principles in the OS in the first place; with that in mind, many Open Source OS's come out looking pretty good. I trust the Linux community to grind down and fix security problems and not sit around and emphasize the numerous security in a Microsoft product. If you're concerned, then help out developers by testing the software and reporting bugs. You could even code a few patches yourself, that being the whole point of community-based development.

    Whether or not there is a deep and dark plot to root big Linux boxes is irrelevant. This is another opportunity to demonstrate the Open Source community's response to security issues to the rest of the computing community. If the heat is really on and this is not just another artifact of news gatekeepers getting over-zealous on a trend, then so be it. It is an opportunity to review and evolve Linux's security as well as the security processes that surround it.

    One of the things I admire most about Linus Torvalds is his steadfast commitment to the quality of his product. It is a commitment that is focused on constant improvement, not PR damage control. I'm sure the real security guru's are sitting with a bit more comfort knowing their servers are running Linux.

    Disclaimer: This post contains no constructive content whatsoever, swallow two tablespoons of salt and call me in the morning.

  83. I'm reminded of a cliche... by acidtripp101 · · Score: 3, Interesting

    The death of one is a tradegy, but the death of millions is a statistic

    For all of you that are curious, this isn't a BSD troll (although it could be...).
    My point here is that whenever a larger *NIX server is broken in to, there are ALWAYS people that comlain about "the insecurity of *NIX". Well, when ONE large *nix server is broken in to, it makes it to the front page of slashdot, whereas blaster/sobig/etc usually get a story or two.
    This is where the quote above comes into play.
    Linux might look insecure, but that's because we usually hear about breakins on a 1 server basis. When we here about Windows, it's usually in the HUNDREDS OF THOUSANDS (if not more). If there was a slashdot story for every one of THOSE servers, then it would appear the way it actually is.

    --
    Not Free(as in beer). Free(as in "I'm free to beat you over the head for being a dumbass")
    1. Re:I'm reminded of a cliche... by SomeOtherGuy · · Score: 1

      You are correct...However I do have a comment to add as to why 1 Hacked *nux Server looks just as bad (in some cases) than 100,000 hacked Windows boxes...And that is because you can assume that a majority of the Windows boxes are administered by "point and click, next and back button" type administrators OR even end users of desktop systems that have services turned on. In the case of a *nix box getting cracked that is used to distribute something as "comlex" as a whole *nix distribution -- one can maybe assume the box is adminstered by a solid Admin who knows what he is doing....and yet the OS was still vulnurable.....(VS. many of the MS exploits being "explained away" because of lackluster or no admin.)

      --
      (+1 Funny) only if I laugh out loud.
    2. Re:I'm reminded of a cliche... by liquidsin · · Score: 1

      ...MS exploits being "explained away" because of lackluster or no admin.

      But that's it. Almost every instance we see of "new trojan/virus X compromises thousands of windows machines" is taking advantage of weeks or months old exploits, automated, and set loose. The Debian job must have taken a good bit of legwork to sniff out a user account/pass then get in and drop the exploit, which was essentially custom-written for that specific purpose. The big linux breaches seem to be about days old, or even unknown holes, because most linux admins know how to keep their machines up to date. But when you start offering certification-in-a-cereal-box style MCSE (not that ALL MCSEs are clueless...) then you end up with admins who don't patch quickly enough, and who wouldn't know a breakin if it was humping their leg. Couple that with an OS as widely deployed as Windows, and you're just asking for trouble...

      --
      do not read this line twice.
  84. Re:I still say we have to adopt UNTRUSTED COMPUTIN by Anonymous Coward · · Score: 0

    Moderators on /. are RE-FUCKING-TARDS..
    Now that was not a troll, that was *flamebait*..

  85. Re:What OS was the compromised box running? by Anonymous Coward · · Score: 0

    Yes.. but think again.. rsync.gentoo.org runs a round robin type load sharing system so there could be a hundred servers under that domain. You just netcrafted one or the control host.

    As far as I know, it was a Gentoo Linux box, but it is NOT maintained by the Gentoo team. It also hosts other services and thats why noone is saying what its name is or what else its used for...

  86. Re:What OS was the compromised box running? by Anonymous Coward · · Score: 1, Funny

    It ran Longhorn, bought at Malaysia for $1.75

  87. The real question is... by beattie · · Score: 5, Funny

    ... did whoever did this steal any of our source code?

  88. Havening! Havening! (n/t) by Anonymous Coward · · Score: 0

    (George edits 95% of the /. copy.)

  89. Re:Debian, Gentoo.... who's next? - OpenBSD ??? by rosie_bhjp · · Score: 4, Interesting

    You'd think but www.openbsd.org doesn't run OpenBSD. Here's a link that explains why.
    In fact, just last year ftp.openbsd.org did get compromised!

    --
    A radio maverick jumps to internet only. The Future of Rock n Roll
  90. How about spammers? by swb · · Score: 4, Interesting

    If you buy the idea that spammers are behind many of the recent worm/viruses, designed to turn machines into spam zombies, it's also probably reasonable to conclude that Windows isn't exactly a reliable platform to trojan; I'd bet a lot of trojans fail to infect properly simply due to Windows problems. And then there's the problem AV software, many of the machines being behind firewalls/NAT and being unreachable. And then there's people turning their PC's off when they don't use them.

    OSS machines, however, are a much more reliable computing environment, meaning that any trojans are actually like to work, and work well. And I'd also wager that many OSS machines are used AS firewalls or bastion machines, and if compromised are easily accessable for spamming or use as stepping stones to other machines. And many of these machines are always on -- you don't have to worry about lack of reliability from disabled machines.

    This makes more sense to me than any other conspiracy.

  91. Re:"Reasonably Confident"? by IdleTime · · Score: 1

    Not really!

    You see, there is a difference between an rsync server and a distfile server. They are not the same, hence your scenario is not a problem.

    --
    If you mod me down, I *will* introduce you to my sister!
  92. Oh, geez by bonch · · Score: 1

    That's complete crap. Look how you're spinning this. A high-profile Gentoo Linux breach, and some Slashdotter STILL finds a way to bash Microsoft.

  93. Re:Thats right, go ahead and try to deflect the bl by Anonymous Coward · · Score: 0

    Okay.
    *Ahem*

    Microsoft did it.

  94. Re:"Reasonably Confident"? by RedHat+Rocky · · Score: 1

    The rsync server has the ebuilds, correct? There's not a lot of security in an ebuild, given that it's just a script, running as root.

    Granted, nothing probably happened. Reasonably, no one was affected. No big deal.

    Unless one of the 20 was me. :)

    --
    Anything is possible given time and money.
  95. How to fix it? by Nucleon500 · · Score: 1

    Chances are, nobody's Portage tree was affected. The bigger question, however, is how Gentoo's security could be improved. As a start, the md5sum of the important parts of a client's portage tree could be compared with one from gentoo.org, which would of course be signed, after each emerge sync. I wouldn't be surprised if something like this already exists, though.

    1. Re:How to fix it? by glwtta · · Score: 3, Insightful
      I don't get it. Why would Gentoo's security need to be improved? I can only remember two Gentoo compromises (though I'm sure there have been more), this one and a long time ago there was an exploit introduced into the build script for a package, this was caught (also within the hour) by the MD5 hash check that emerge does.

      Two compromises, both cought within an hour and with no (absolutely none) adverse effects on the users - there is just not much room for improvement here, this is what good security is.

      --
      sic transit gloria mundi
  96. Savannah.gnu.org was hit as well by presroi · · Score: 4, Interesting

    http://savannah.gnu.org/statement.html

    On December 1st, 2003, we discovered that the "Savannah" system, which is maintained by the Free Software Foundation and provides CVS and development services to the GNU project and other Free Software projects, was compromised at circa November 2nd, 2003.

  97. Infrequency? by Anonymous Coward · · Score: 0

    GNU
    GNOME
    Gentoo

    The list goes on. According to this, Linux is the one breached more often.

    1. Re:Infrequency? by yosemite · · Score: 1
      It's like the old saying "I rob banks 'cause thats where the money is"


      Maybe hackers prefer linux boxes, because linux is preferable?

    2. Re:Infrequency? by Anonymous Coward · · Score: 0

      Of course Linux systems are an attractive target.

      The purpose of this attack (and the other recent compromises) was most likely to gain the attacker a large army of Linux zombies w/ his/her trojan running and probably phoning home somehow (IRC?). Since Linux is powerful, flexible, and reliable, a largish number of Linux boxes that can be centrally directed (or even used individually as disposable attack platforms) is an incredibly powerful tool for accomplishing whatever a cracker's purposes are.

  98. Redmond Hard at Work by NEOtaku17 · · Score: 1

    Wow Debian and now Gentoo...Microsoft must be really busy now!(Sorry for that extreme sarcasm).

  99. Microsoft's OS choices by TWX · · Score: 1

    "IIRC the load balancing for Windows Update is carried out bu linux machines..."

    I would be very surprised if this were the case. I'd peg them to use BSD long before they'd touch anything that clearly GPL, and I'd not even expect BSD unless they were continuing their standard, "Embrace, Extend, Expand" approach.

    If they ever did actually use Linux for such a critical function and it leaked out, even if it were compromised, it would be like they came out directly to say that Linux is better for enterprise grade security than their own OS is. They couldn't risk that even if the machines went down daily.

    --
    Do not look into laser with remaining eye.
  100. Why it sucks by Overly+Critical+Guy · · Score: 1

    It sucks, because it makes fanatical zealots look like flaming hypocrites.

    The rest of us rational folks knew all along Linux wasn't perfect, but heaven forbid we mention it to the Mandrake and Gentoo kiddies on Slashdot. I've been modded down just for having this sig, which is ridiculous.

    Seeing Gentoo itself be attacked with a remote exploit--especially in light of the fact that Linux is the most breached as it is--is just not surprising to me at all. The reason is because no system is perfect, especially not OSS. And we've been reading about a lot of high-profile break-ins lately, which is just funny.

    Yes, it makes a lot of people look stupid when this stuff happens, and I do enjoy it, because I'm always branded as a Microsoft shill just for pointing out obvious truths. And then the news speaks for itself.

    --
    "Sufferin' succotash."
  101. Bad news - depends on your point of view by dpilot · · Score: 1

    Sure there have been security breaches, security breaches will always be with us. Anyone who can't accept that is probably a prime customer for Palladium, and deserves what they get.

    The real issue here is that Debian and Gentoo were both forthcoming about the breaches. They both did the Right Thing. Not only that, but they've both collected forensics, and if not identifying culprits, are at least contributing to improving the security of the Linux community.

    This is Real Security, as opposed to hiding the facts, and hoping nobody ever finds out.

    --
    The living have better things to do than to continue hating the dead.
  102. Honest answer by Overly+Critical+Guy · · Score: 2, Informative

    http://www.winnetmag.com/windowspaulthurrott/Artic le/ArticleID/41035/windowspaulthurrott_41035.html

    During an oddly-underpublicized security Webcast Monday, Microsoft revealed that hackers subject the company to 2500 to 3000 electronic attacks every day, or over 100,000 a month. Yet despite this massive number of attacks, the last successful intrusion occurred over three years ago, during the infamous October 2000 security breach. But the software giant says the biggest security risk to the company isn't external electronic attack of its Web properties, but rather its huge fleet of mobile workers and partners--some 60,000 strong--that access the company's 175 remote access points on a regular basis.

    We've taken a deep look inside Microsoft to see how we can improve security at every level," sad Mike Nash, the vice president of the Security Business Unit at Microsoft, during the Webcast. "A lot of the technology we use Microsoft applies directly to [customers'] work."

    Microsoft revealed some other interesting statistics during the Webcast. The company uses Computer Associates' eTrust security management suite to secure its networks. It uses two-factor authentication (user name/password and smart card) to better secure its intellectual property.

    --
    "Sufferin' succotash."
  103. Re:"Reasonably Confident"? by IdleTime · · Score: 1

    Yes, it has the ebuilds, but they need to be used by the emerge program or ebuild program. They can't be executed alone, i.e they are not shell scripts. They are basically instructions on how to configure the package, which tarballs to download from where and what pre and post requisuites. Those are all protected by md5 sums.

    --
    If you mod me down, I *will* introduce you to my sister!
  104. You don't remember correctly by Overly+Critical+Guy · · Score: 1

    You're thinking of when the first RPC vulnerability hit (which was patched two months before, by the way...to all those Debian-heads crying out how the kernel exploit was patched in September), and Microsoft used Akamai for a short while because the trojan was set to DDOS one of their URLs.

    The "threat" passed and everyone forgot about it.

    --
    "Sufferin' succotash."
    1. Re:You don't remember correctly by crschmidt · · Score: 1

      Not quite accurate:

      [crschmidt@peanut ~]$ host www.microsoft.com
      www.microsoft.com is an alias for www.microsoft.akadns.net.
      www.microsoft.akadns.ne t is an alias for www2.microsoft.akadns.net.

      Microsoft is still using Akamai. Which it seems like, from this comment, you think it isn't. Either I'm miunderstanding, or you are, but Microsoft definitely does use a level of OSS between them and their servers.

      Of course, this level of seperation has no affect on security - it simply passes on what needs to be passed on. However, it is still there.

      --
      -- Christopher Schmidt YouTube Quality of Experience
  105. five words and peace of mind by polyp2000 · · Score: 1

    emerge rsync
    emerge --update world

    peace of mind !

    --
    Electronic Music Made Using Linux http://soundcloud.com/polyp
  106. Yet again, someone tries to pin it by Overly+Critical+Guy · · Score: 1

    Why does everyone assume some one group is behind it?

    Couldn't it be that, as with every other public website out there, random hackers try to break in for fun and vandalism?

    Come on. I'm fully expecting someone to implicate Microsoft in some way, as they do in every OSS break-in article.

    --
    "Sufferin' succotash."
  107. Role model for us all. by Anonymous Coward · · Score: 0

    Wow, an admin who fesses up (within 24 hours of breach) when (s)he's been hacked. See, now that wasn't so bad was it? Now why can't other admins do this too? Or at least follow the donts of damage control.

  108. Simple by devphil · · Score: 1
    but why has nobody mentioned finding the perpetrators?/em>

    My opinion: for the same reason that officers of the peace make only vague handwavey-type sounds when asked if they have leads on the suspect of a crime.

    • If they say they have no leads, then they look like idiots.
    • If they say they have leads,
      • and they're bluffing, then they look like incompetent liars and fradulent idiots.
      • and they really do have leads, they won't possibly actually mention them because that would set themselves up for a slander/libel/defamation-of-character lawsuit if they can't make it stick.
      • and they really do have irrefutable proof, then they're not going to tip their hand before law enforcement breaks down the doors of the goatfuckers.

    So why brag about leads on /.? They have nothing to gain and everything to lose.

    --
    You cannot apply a technological solution to a sociological problem. (Edwards' Law)
  109. Hypocrisy alert by Overly+Critical+Guy · · Score: 3, Insightful

    I love it.

    I've pointed out before that Windows is way more widespread than Linux, and so is more attacked and vulnerable, but then zealots come on and say Apache is the most-used on the net and yet not the most breached. But to this, it's already the most-breached operating system.

    Hoot and holler about the reasons all you want, but them's the facts.

    We REALLY, REALLY need to stop with the "Linux is invincible, Windows sucks" attitude. It's flat-out not true, and it's severely holding the community image back in the minds of the rest of the rational computing world who just uses what they use to get the job done and don't treat operating systems like religious belief systems.

    --
    "Sufferin' succotash."
    1. Re:Hypocrisy alert by dmaxwell · · Score: 2, Interesting

      ...and don't treat operating systems like religious belief systems.

      I really don't want to be a smartass here but could this be a case of the pot calling the kettle black? You don't seem at all Overly Critical when something bad happens to Windows. Indeed, your posting history is largely criticisms of Linux. I could exchange every instance of Windows and Linux in a typical posting of yours and you would come off exactly like one of the "Linux religious fanatics" you claim to be above.

      You also seem to think the most vocal and rabid Linux users are typical users. Every community has extra obnoxious members and Windows is not exempt from the vocal religious fanatic problem. And yet, no one speaks of obnoxious Windows users being the biggest problem dragging Windows down. Could it be that telling amorphous groups like "Windows users" or "Linux users" how to behave is a largely useless activity? Could it even be that "the way members of foo act" is in no way a valid criterion for assessing a technology?

    2. Re:Hypocrisy alert by antiMStroll · · Score: 1

      Your link is to a short blurb about the mi2g study, the same company which tried to warn the US government of a pending cyber attack in the fourth dimension. The most cursory Google search unearths enough negative press about mi2g to disuade the most rabid True Believers, yet here you are using them to bolster your convictions about Linux security. Your depiction of Linux users is typical fantasy bordering on bigotry and I've never seen a single positive thing from you about Linux or OSS software, yet you continue to describe Linux users as religious believers. And here once again you appear to equate the comprimise of a single box with the global infrastucture damage of a Code Red or "I Love You". Hypocrisy indeed.

    3. Re:Hypocrisy alert by Overly+Critical+Guy · · Score: 1

      I really don't want to be a smartass here but could this be a case of the pot calling the kettle black?

      No, not at all. I don't treat operating systems like religions.

      You don't seem at all Overly Critical when something bad happens to Windows.

      Of course I am. But Slashdot is overly critical of Windows, ALL the time.

      Indeed, your posting history is largely criticisms of Linux.

      Because people have placed Linux on a silver platter in their minds. You want to know why I post? I created this account because I was sick of the close-minded bias. Slashdotters like to act as though they're really open, rational people, but when it comes to Linux and Windows, they wear blinders. There is so much fanatical Microsoft hatred that I wanted to, heaven forbid, counter it with rational commentary by pointing out the obvious--Linux has flaws like everything else.

      So, you see me posting more Linux criticism than Windows criticism, because all I see here is people spinning Linux flaws and ignoring them and bashing Windows for inane things like Outlook executable attachments.

      I could exchange every instance of Windows and Linux in a typical posting of yours and you would come off exactly like one of the "Linux religious fanatics" you claim to be above.

      No. Not really. My posts are all about pointing out the flaws that people ignore in Linux. If Slashdot wasn't so incredibly biased, I wouldn't be commenting on it.

      You also seem to think the most vocal and rabid Linux users are typical users. Every community has extra obnoxious members and Windows is not exempt from the vocal religious fanatic problem. And yet, no one speaks of obnoxious Windows users being the biggest problem dragging Windows down.

      Because they're not the biggest problem "dragging Windows down." But for Linux, that IS the problem.

      Could it be that telling amorphous groups like "Windows users" or "Linux users" how to behave is a largely useless activity?

      No. Just look at Slashdot. It is one big anti-Microsoft amorphous group. Especially the editors. A lot of Linux newbies come to Slashdot and formulate their operating system perspectives based on the +5 posts and editor commentaries around this place. Where do you think all those obnoxious anti-"M$" trolls come from? What is wrong with, instead of that, having calm rational folk who appreciate technology no matter the brand name, and who just use the right tool for the job instead of making another 90s-era BSOD or Clippy joke?

      Could it even be that "the way members of foo act" is in no way a valid criterion for assessing a technology?

      Who said it was? I never acted or implied such.

      As far as the technology goes, Windows crushes Linux in some areas, and Linux crushes Windows in others. The anti-"M$" bots want you to think Linux is flawless. That's why it amuses me so much when all these security breaches (let's see, what is it now--GNU, GNOME, Debian, FSF, and now Gentoo?) occur and people squirm and STILL try to bash Windows in some way.

      Microsoft hasn't had a breach since October of 2000. Why is it so damned hard for Linux guys to give credit where credit is due? It's like they're afraid to praise Microsoft for anything. And that's what I point out and react to, because I think it's ridiculous, and it's one major factor of many in the predominant attitude of this community that is severely holding back Linux in the minds of the professional world.

      Disagree if you want, but at least see where I'm coming from.

      --
      "Sufferin' succotash."
    4. Re:Hypocrisy alert by Overly+Critical+Guy · · Score: 1

      Single box? GNU, GNOME, Debian, FSF, and Gentoo are more than a single box.

      I've praised Linux and OSS software before, but the majority of wacky-ass criticism in Slashdot is towards Microsoft. It's just hatred and jealousy. So I reply to it.

      Does that frustrate you?

      --
      "Sufferin' succotash."
    5. Re:Hypocrisy alert by Anonymous Coward · · Score: 0
      And that's what I point out and react to, because I think it's ridiculous, and it's one major factor of many in the predominant attitude of this community that is severely holding back Linux in the minds of the professional world.
      And once more, OCG opens his mouth and spouts the Wisdom of the Ages, since he knows what everyone in 'the professional world' thinks about linux.

      You are the very definition of the word pretentious. You are not objective. You are not balanced. You are an astroturfer for Microsoft. Plain and simple. But apparently you're so blinded by your hatred for linux and open source that you can't see that.
  110. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  111. Re:What OS was the compromised box running? by MrHanky · · Score: 2, Interesting
    Yes.. but think again.. rsync.gentoo.org runs a round robin type load sharing system so there could be a hundred servers under that domain. You just netcrafted one or the control host.

    A Netcraft search for rsync.gentoo.org shows more than one server. Two of them run Gentoo, two run Red Hat, one runs Debian, three run unknown Linux, and one runs FreeBSD (some of the servers are listed twice). There are more servers (14, if one is to believe 'host rsync.gentoo.org|wc -l'), but Netcraft is only interested in those with web-servers.
  112. Do I speak for everyone else... by Overly+Critical+Guy · · Score: 1

    When I say, you're kidding, right?

    Random hackers attack things. Stop trying to pin it on some one mysterious group. It makes you look so incredibly paranoid.

    Yes, Linux servers are not perfect. Accept this, patch, fix, and move on. Microsoft did, and they haven't had a break-in since October of 2000. According to a recent article, they're attacked 2500 to 3000 times daily.

    --
    "Sufferin' succotash."
    1. Re:Do I speak for everyone else... by Aardpig · · Score: 1

      Yes, Linux servers are not perfect. Accept this, patch, fix, and move on. Microsoft did, and they haven't had a break-in since October of 2000. According to a recent article, they're attacked 2500 to 3000 times daily.

      Ah, but 99% of those 'attacks' were actually ICMP echo requests. Microsoft counts these probes as attacks because their operating systems have a history of crashing when pinged.

      --
      Tubal-Cain smokes the white owl.
  113. Write to CD by Flammon · · Score: 1

    You could waste a bunch of paper or you could just write to a CD. You'll run out of paper way before you run out of space on the CD.

    1. Re:Write to CD by Wehesheit · · Score: 0

      I wonder if you wrote to the cd every hour how many times per cd you could you could write the logs.

      --
      This P.I.G. will walk on the water, This P.I.G. will walk on the sea, This P.I.G. will walk whereever he wants.
  114. Re:What OS was the compromised box running? by Anonymous Coward · · Score: 0

    it DOES RUN GENTOO! That's what's making it worse.

  115. Emerge-sync by BigBuckHunter · · Score: 1

    For any Gentoo user running the latest and greatest (Accept ~X86), doing an emerge-sync and "Emerge -U world" is no small task. It requires a few Hail Mary's and a human sacrafice to have a working system afterward. Users running the stable builds shouldn't have a problem though. I have personally blown up my Gentoo installation seven times, and each time I learn more about the inner workings of linux. BBH

  116. Re:How Gentoo deals with users' concerns by omega9 · · Score: 1

    ...all Gentoo users deserve information about how this box, running Gentoo, got cracked remotely.

    I'm not argueing one side or the other, just mentioning this for the sake of completeness. The post makes no specific mention that the compromised machine was itself running Gentoo. It may have been, it just wasn't stated one way or the other. And there's the possibility that the rootkit was installed locally and taken advantage of remotely.

    I suggest immediate full-disclosure of the whole incident.

    Your feelings about how devs handle security issues are yours to raise, and potentially rightly so. But take another look at the posting. It states that the purpose of the box was not solely to act as an rsync server. It's a donated service by a sponser that also hosts other services on that same machine. After reading that post it's hard to even know for sure if it was rooted because it was a Gentoo rsync server or for some other unrelated reason:

    The box provides other services not related to Gentoo Linux as well and the sponsor has requested that we not publicly identify the box at this time. Because the Gentoo part of this box appears to be unaffected by this exploit, we are currently honoring the sponsor's request. That said, if at any point, we determine that any file in the portage tree was inappropriately modified, we will release full details about the compromised server.

    We don't like "security through obscurity"

    I don't see any unneeded obscurity surrounding this. It sounds more like you're just unhappy with whatever happened in IRC today.

    --
    I'm against picketing, but I don't know how to show it.
  117. That does it by Anonymous Coward · · Score: 2, Funny

    First it was Debian, now it's gentoo.
    I'm switching to my own home brewed OS
    You vulnerable Linux people don't deserve my support

    Asta la vista, I won't be back!

  118. could backbone admins be abusing their power? by Anonymous Coward · · Score: 0

    I always wondered if admins in big places abused the links they managed.
    One person could sniff MAJOR data from
    many diverse sources. This over time would result in some nice login/passwords.

  119. Re: Downtown Philly by Bernie+Fsckinner · · Score: 1

    What part of _downtown_ Philly has abandoned houses in it? These days, you gotta get at least a couple of miles from Center City to find an abandoned house.

  120. Or as the members of the Dinochrome Brigade say: by Anfo · · Score: 1

    Once is happenstance, twice is coincidnece, three times is enemy action.

  121. Re:How Gentoo deals with users' concerns by Anonymous Coward · · Score: 0

    heh, are you the daniel mettler fucktard who was spamming #gentoo? gotta say, i agreed with ciaranm on that one...

    -- roger55

  122. Hell ya man! by Anonymous Coward · · Score: 0

    Preach it brother!

  123. Dear mod by Overly+Critical+Guy · · Score: 1

    How am I trolling?

    I've unchecked my karma bonus and everything because I know this is offtopic. I was just curious?

    --
    "Sufferin' succotash."
    1. Re:Dear mod by Anonymous Coward · · Score: 0

      Having looked at your recent posts, you keep saying the same thing over and over. I supposed technically you weren't trolling but rather it should have been moderated as flamebait or redundant. It was a borderline call but I think you can come up with something a little more original and try not to get a flame war started. And yes I know that there are 100's of /.'s who do the same thing as you saying windows sucks, but that doesn't mean you have to do the same thing as they do.

    2. Re:Dear mod by Overly+Critical+Guy · · Score: 1

      You admit I wasn't trolling. All I do is post my opinion. If you disagree, you should reply and say so, and we can discuss. Not mod me down.

      --
      "Sufferin' succotash."
    3. Re:Dear mod by Anonymous Coward · · Score: 0

      You're right... it probably shouldn't have been a troll. It should have been marked redundant or flamebait. It's not that I disagree with your opinion, it's that you have been repeating yourself and it seems like you are more interested in starting a flame war than trying to convince people of your opinions. Tone down the rhetoric and stop telling people how they are all wrong and maybe you'll get some people to listen to you.

  124. typo by commodoresloat · · Score: 1
    The priests _were_ a bunch of vipers.

    You misspelled "are."

  125. It can be perfect by CedgeS · · Score: 1

    The log machine can very easily be perfect. There are two simple variations to this, one of you want it to work even after the box is rooted, one if you don't. The first is an inline network logger. It acts like a piece of copper wire, but records all the data going through it. The second is a serial or similar mass storage device that the computerrights its logs to. The device cannot be accessed for reading or reseting except through an interface not available to the computer.

  126. Here's what real security looks like by Beryllium+Sphere(tm) · · Score: 4, Insightful

    Cars are built out of steel, not glass. Glass is a very strong material. But hit it with a hammer and it shatters. Steel just gets dented.

    Gentoo had "ductile" security. They were able to limit the damage because they had some kind of Tripwire/mtree-like program running on the inside. Given the speed of the response, my guess is that they had a response plan ready to go.

    The lesson is that measures to limit the damage from a break are as vital as measures to prevent breaks in the first place. Fire prevention doesn't substitute for sprinkler systems, and intrusion prevention doesn't substitute for backups. You've got to have both.

  127. Re:How Gentoo deals with users' concerns by Anonymous Coward · · Score: 0

    only one user was kicked some obnoxious little twat h20 was flooding and generally annoying the hell out of me i say good for ciaranm

  128. So did it get synched up? by Anonymous Coward · · Score: 0

    So did it get synched up?

  129. +1, Funny by Anonymous Coward · · Score: 0


    Mod this up...

  130. Attack on the open source development methods? by Phil+John · · Score: 1

    I'm half expecting Gartner group or Microsoft or some such other party to now step forward and say..."SEE! They have to have their code holding servers open to the net so that their distributed developer base can update and add to the source, the open source model is inherently flawed, as these break ins have proven! When all of your developers are working on an internal network like at Microsoft this could never happen!".

    Not to sound all tinfoil hat or anything, but this could be another prong in the whole anti OSS FUD campaign.

    --
    I am NaN
  131. Re:How Gentoo deals with users' concerns by Anonymous Coward · · Score: 0

    Aww, poor baby. Got your little spamming ass kicked out of the IRC channel, eh? Dumb fuck.

  132. Re:Wimps. I'll be really impressed... by Anonymous Coward · · Score: 0

    It'll never happen, BSD's are to hard a target.

  133. Tripwire / AIDE by Asdex · · Score: 3, Insightful

    From the Gentoo Altert:
    • "However, the compromised system had both an IDS and a file integrity checker installed"

    Gentoo realized that they got hacked after one day.
    GNU Savannah realized that they got hacked after one month.

    It's time to propagate the use of file integrity checkers! They can detect the effects of any new exploit and can't be circumvented (when properly used!).


    AIDE
    Tripwire
  134. All 17 Linux Users Affected by Anonymous Coward · · Score: 0

    "Word is that all 17 Linux users were affected."

    1. Re:All 17 Linux Users Affected by glenstar · · Score: 1

      I think you confused Linux with the Hurd. On top of that, unless the Hurd acquired two more users in the last year, your user count is off.

  135. IDS was involved by ampersandTHORN · · Score: 1
    ...the compromised system had both an IDS and a file integrity checker installed.

    A group of people in the UK recently came to the conclusion that IDS is actually the problem rather than the solution first hoped for.

  136. Unix experience by Avihson · · Score: 1

    Microsoft Hiring Unix Admins

    Posted back in December 2000
    This is from Microsoft's jobs page. http://www.microsoft.com/jobs/search/jobDetail.asp ?fromPage=viewJobs&jobNumb er=906950&page=1&msid1=-2049921163&msid2=-49202693 8&msid3=-2123347170&msid4= 2105645115
    old link

    SYSTEMS ADMINISTRATOR [Job Code: N05rc-dc ]
    Required skills: Strong inter-personal and communication skills; high skill of most UNIX commands/utilities. Familiarity with most basic system administration tools and processes; for example, can boot/shutdown a machine, use backup programs and fsck, maintain system files (hosts, resolv. conf, etc). Fundamental understanding of a UNIX-based operating system; for example, understands job control, soft and hard links, distinctions between the kernel and the shell. Job also requires occasional 24x7 on-call availability. Required background: One to three years of system administration experience. Desirable: A degree in computer science or a related field. Familiarity with networked computing environment concepts; for example, can use the route command, add a workstation to a network, netstat, etc. Ability to write scripts in some administrative language (Perl or shell). Experience with Solaris and Sun hardware especially Enterprise series Familiar with RAID technology Windows NT experience Experience in a 24x7 data center environment Special Note: Whoever we hire will have to be able to function in a 24/7 production environment, be willing to be on call, and be able to learn how to fix all of the problems that come up with the site. The qualifications below give a good idea of what problems we find on the site. I cant get any more specific than that since we see many unique problems that we may have never seen before.

    Job Location: Mountain View, California

    they may know something now.

    1. Re:Unix experience by rainer_d · · Score: 1

      Bzzz.
      That was for hotmail.
      Most of these systems are gone now, I presume.

      --
      Windows 2000 - from the guys who brought us edlin
  137. SNORT is not an Intrusion Detection System by scosol · · Score: 1

    It is a *network* intrusion detection system.
    There's a big difference there.
    NIDS generally sniff packets and look for signatures of attacks.
    (on the *network*)
    A box level IDS keeps an eye on filesystems to see what has been modified, keeping its information in some more-secure place. (read-only media or something)

    --
    I browse at +5 Flamebait- moderation for all or moderation for none.
    1. Re:SNORT is not an Intrusion Detection System by Anonymous Coward · · Score: 0

      Sigh. SNORT is most definately an IDS.

      But there are two types of IDS Host and Network

      The article states that there was an IDS and a file integrity checker, which I'll take to be Tripwire /AIDE or similiar.

      So both are covered, and SNORT, Tripwire and AIDE can all log, and store their read-only databases elsewhere.

    2. Re:SNORT is not an Intrusion Detection System by Rich0 · · Score: 1

      Hmm - read-only media probably wouldn't do too much good in this regard.

      Perhaps you meant write-once media?

      Probably the best system out there is a printer - and that is purely write-only. That is assuming that the printer does not have the capability to reverse the page feed (like most dot matrix printers can do) - otherwise the hacker could have the printer overwrite the last 20 pages of logs with solid black ink...

    3. Re:SNORT is not an Intrusion Detection System by scosol · · Score: 1

      Generally after you stabilize the filesystem/config- you then run snort from, and keep it's configs on, a read-only media.
      (this is not to make sure your logs dont get modified, it's to make sure that nobody can mess with teh IDS config to coverup the filesystem changes they made)

      As others have said, remote logging takes care of that.
      I don't know why people keep bringing up the "dot-matrix printer"- I read that as well ~10 years ago when I was first getting in to security.
      I don't remember where, but it must have been somewhere, because everyone loves to talk about it- and it's always specifically "dot-matrix".
      Is it actually a feasible solution? No. Maybe back in the olden days of unix when you only had one box, sure- but today?
      Hell no.
      Unless you're doing remote-logging to one box, and then printing from there.
      When you setup a remote loghost, you have to be very careful about where it is.
      It needs to be in a fairly local location. Do you know anyone that rushes down to replace the paper in their log machine every week?
      Did they engineer some sort of endless-loop device with some scotch tape?
      Not likely- If you're accepting the minor additional risks that come with remote logging to begine with, then it's easy enough to lock that box down to the point where it is for all intents and purposes, impenetrable.

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
    4. Re:SNORT is not an Intrusion Detection System by Anonymous Coward · · Score: 0

      I agree that paper logging is an effective if not practical solution.

      Believe it or not, we have such a log running at work for a VAX. We only log relatively serious events though - not every time the equivalent of cron wakes up and spawns something.

      And yes - somebody does walk down once a week to replace the paper, and somebody does actually read it all...

  138. I'm going to get trolled for this... by reconbot · · Score: 3, Interesting

    But I'm glad that there has been so many attacks against linux and other oss projects.

    Kernel.org, debian.org, gentoo.org Gnu.org All of them had security holes and now those holes are plugged.

    I used to run a few servers. Mostly web-servers, but I had a few for mail and other things. Almost every single one was hacked all in the same 2 month period. I had kept up with updates and I figured I was secure. If I wasn't hacked I would have never known that I wasn't secure and I could have been seriously screwed down the line. It was a much needed eye opener.

    --
    I'm just this guy, you know?
  139. OpenBSD IS desktop ready, already... by bondjamesbond · · Score: 1

    I installed 3.4, did a xf86conf, got X just right, cd /usr/ports/x11/kde ; make && make install, the same with fluxbox, and have a suh-WEET desktop with fluxbox and all the KDE apps I need.

  140. Old dodge. by dmaxwell · · Score: 1

    I've heard that it is possible to make Ethernet cables with no transmit lines. Basically, you can write to a box connected that way but that box can't talk back. The best you could do then if there was a vulnerability is crash the syslog process on the dropbox.

  141. You don't get karma from "funny" posts. by MikeCapone · · Score: 1

    Ah!

  142. Dear asshat by Anonymous Coward · · Score: 0

    You were trolling. Whoever modded you as insightful is full of shit. Just like you are.

    1. Re:Dear asshat by Overly+Critical+Guy · · Score: 1

      Okay, Anonymous Coward.

      --
      "Sufferin' succotash."
    2. Re:Dear asshat by Anonymous Coward · · Score: 0

      That's Ms. Anonymous Coward to you, buck-o.

  143. Speacking of what .... by fferreres · · Score: 1

    I think something is wrong with my Gentoo or something...

    fede usr # netstat -n -t
    Active Internet connections (w/o servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State
    65.54.230.240:443 TIME_WAIT
    tcp 0 0 148.240.150.139:32834 65.54.230.240:443 ESTABLISHED
    tcp 1 0 148.240.152.95:34976

    fede usr # host 65.54.230.240
    Host 240.230.54.65.in-addr.arpa not found: 3(NXDOMAIN)

    fede usr # ping 65.54.230.240
    PING 65.54.230.240 (65.54.230.240) 56(84) bytes of data.

    --- 65.54.230.240 ping statistics ---
    2 packets transmitted, 0 received, 100% packet loss, time 1014ms

    fede usr # whois 65.54.230.240

    OrgName: Microsoft Corp
    OrgID: MSFT
    Address: One Microsoft Way
    City: Redmond
    StateProv: WA
    PostalCode: 98052
    Country: US

    NetRange: 65.52.0.0 - 65.55.255.255
    CIDR: 65.52.0.0/14
    NetName: MICROSOFT-1BLK
    NetHandle: NET-65-52-0-0-1
    Parent: NET-65-0-0-0-0
    NetType: Direct Assignment
    NameServer: DNS1.CP.MSFT.NET
    NameServer: DNS2.CP.MSFT.NET
    NameServer: DNS1.TK.MSFT.NET
    NameServer: DNS1.DC.MSFT.NET
    NameServer: DNS1.SJ.MSFT.NET
    Comment:
    RegDate: 2001-02-14
    Updated: 2002-12-05

    TechHandle: ZM23-ARIN
    TechName: Microsoft Corporation
    TechPhone: +1-425-882-8080
    TechEmail: noc@microsoft.com

    OrgAbuseHandle: ABUSE231-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-425-882-8080
    OrgAbuseEmail: abuse@microsoft.com

    OrgNOCHandle: ZM23-ARIN
    OrgNOCName: Microsoft Corporation
    OrgNOCPhone: +1-425-882-8080
    OrgNOCEmail: noc@microsoft.com

    OrgTechHandle: MSFTP-ARIN
    OrgTechName: MSFT-POC
    OrgTechPhone: +1-425-882-8080
    OrgTechEmail: iprrms@microsoft.com

    I am not using any SSL server right now...

    --
    unfinished: (adj.)
  144. Re:"Reasonably Confident"? by Anonymous Coward · · Score: 0

    Wow. 20 people, huh. That would explain why every file on my box was replaced by a picture of the goatse.cx guy.

  145. Netcraft confirms... by Anonymous Coward · · Score: 0

    *BSD is dying.

    Oh, wait... never mind.

  146. Re:On the bright side... x1488 by Anonymous Coward · · Score: 0

    not really...

  147. I'm still going conspiracy by Truth_Quark · · Score: 1



    Windows is attacked FAR more than OSS. Why?


    Recent Windows attacks (...notably and demonstrably Blaster...) have been because of the business model of (the criminal organisation) Micro$oft. There is a not insignificant reservoir of bad feeling about both their illegal use of monopolies, and the cost to business of finding solutions and workarounds to their bugs.

    On the other hand the recent attacks on Debian and Gentoo, follow a very different pattern.

    The break-ins were very sophisticated (in the sense that the venerability exploited was largely unknown), but then having broken in the behaviour was code-bunny - install sucKIT

    Why would a hacker who had presumably discovered the exploit one day when perusing the kernel, follow up with such an unintriguing response?
    and then, not completely bored yet, keep doing the same thing?

    This is a professional bounty job to backdoor open source development servers.

    You know it

    I know it

    Mr Gates and Mr Bush know it

  148. R'SYNC is my favorite boy band by eponymous+flower · · Score: 0, Redundant

    Don't they sing that song 'Bye Bye Bye'?

    --
    You say self-important egomaniac like it's a bad thing. - Peter Dragon
  149. anyone one know when cvs will be up? by gimpboy · · Score: 1

    i just tried to up date some sources on a project of mine and i noticed cvs hung for a while. i went to savannah and i saw the "statement". it mentions "minimal services back up by Friday". does anyone know if minimal will include cvs? i'm not trying to hurry them, i'm just curious.

    if there are any savannah folks out there reading this, let me say you do a wonderful job keeping everything up and running.

    thanks.

    --
    -- john
  150. "We are the same species" by Kashif+Shaikh · · Score: 1

    Speak for yourself. It's the Jews who committed the crime of slaying the 'person on the cross'. The same is being done today by the 'Big Guys' -- if something goes against what they believe it, they declare, "You are with us or against us".

    1. Re:"We are the same species" by zangdesign · · Score: 1

      Note: I said species, not race. More and more, the definite racial disctinction is blurring, either through mating or scientific revision.

      Like it or not, we're all Homo sapiens here. That includes me, you, and the Jews, too. History is filled with, nay, mostly composed of, man's inhumanity toward fellow mankind in some form or fashion, and NO race is exempt from that.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    2. Re:"We are the same species" by Anonymous Coward · · Score: 0

      Speak for yourself. I'm a Neanderthal. :-)

  151. Re:I still say we have to adopt UNTRUSTED COMPUTIN by Anonymous Coward · · Score: 0
    Wait, let me guess - it's all "M$" fault, right?

    BWAHAHAHAHAHAHAHAHAH!!!!!!!!1!!!!!!!

    How utterly bloody pathetic. Even your brethren don't like you and mod you down.

  152. Re:I still say we have to adopt UNTRUSTED COMPUTIN by pair-a-noyd · · Score: 1

    Fuck you dickweed.

    Did you see anywhere in the message any reference to M$?
    No, you stupid fuck.
    My post was about COMPUTER SECURITY.

    Now, go fuck yourself...

  153. More good news then bad by neopara · · Score: 2, Insightful

    Security is so much more then stopping the user at the door. There are always going to be 0-day exploits, which have no patches. The trick with security is mitigating your exposure. Getting root is not a successful hack, keeping it is. So what if someone rooted my box, if I can see it; I can deal with it. These latest big-profile comprises are actually good news because the attacks where not successful. It shows how well Linux can mitigate exposer, and how it layers it security. This is where Microsoft goes wrong with it's lastest methodology towards security. They think putting a firewall in place is all that you need, which is absolutely wrong.

    --
    Nothing more, For me to say; About my life, A life of dreams....
  154. RMS-like statement in all it's glory by theolein · · Score: 0, Flamebait

    In the interest of continuing cooperation and in helping to improve security for all essential Free Software infrastructure, and despite important philosophical differences, we are working closely with Debian project members to find the perpetrators and to secure essential Free Software infrastructure for the future.

    This just had to have RMS invloved, managing to get his bigoted statements in, even when the system has been compromised.

    Damn man, you've been rooted and you can think of nothing better to say than that you have "important philosophical differences" with the rest of the OSS world, but that you will be OH SO GENEROUS and actually bother to talk to some people who don't get all hyped up when they say Linux and not GNU/Linux.

    That is why your fuckshit GNU/Hurd is still where it is you pompous clown.

  155. Mac OSX R U by theolein · · Score: 1

    We all know in order for 'nix to make it to the desktop, it has to become WAY more user friendly.

    You mean like Mac OSX?

  156. rsync security update by boots@work · · Score: 2, Informative
    An rsync vulnerability has been identified.

    I was going to post it here, but the moronic lameness filter won't let me. So you'll need to look at rsync.samba.org.

    The rsync team has received evidence that a vulnerability in rsync was recently used in combination with a Linux kernel vulnerability to compromise the security of a public rsync server. While the forensic evidence we have is incomplete, we have pieced together the most likely way that this attack was conducted and we are releasing this advisory as a result of our investigations to date.[....]
  157. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  158. haha by Anonymous Coward · · Score: 0

    switch to freebsd!

  159. Could it be... by KinkyClown · · Score: 1

    ...that Microsoft is behind this? This is the second open source Linux distribution that has been attacked. It could also be some students that are paid by Microsoft to show how bad the security is on Linux. I have my doubts.

  160. Trust by Crazy+Eight · · Score: 1

    Yeah, I think Amgine007 said the opposite of what he ment.

  161. Trust? by Crazy+Eight · · Score: 1
    I think you did it again...

    Gentoo would be ideal with a web of trust...

    Don't you mean a web of distrust, or at least one that didn't rely on trust at all? Ultimately, one can't design a system without some level of trust somewhere, but if you want a web of something make it a web full of nodes that need not depend on the veracity of a centralized source.

  162. Proof by Crazy+Eight · · Score: 1

    I installed W2K under VMware and had it booted for 4 hours. The next day I got e-mail from my ISP informing me that other customers of my ISP had complained that I was broadcasting Blaster. Four Hours!

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

      It got into our corporate network and running an automated windows 2000 _INSTALL_ test in a VM (takes about 45 minutes) got infected. This is behind a firewall.

      Bad news.

    2. Re:Proof by Crazy+Eight · · Score: 1
      Uhh, do by any chance work for VMware? I recently discovered that an aquaintacnce runs Linux on his laptop. In the discussion that followed he mentioned that his brother works for VMware. Apparently they use a battery of W2k installs to stress test GSX server for bugs. IIRC it took 15 seconds (it could have been minutes, but I think he said seconds) for a completed installation to get infected.

      Do you happen to have a brother that works for Zoetrope?

  163. Hey! I worked at Microsoft. by Chemisor · · Score: 1

    > Come on. Do you really think Microsoft knows that much about security?

    Don't insult me. I worked at Microsoft too and know quite a bit about security. I also know why many Microsoft products don't have much of it, and it has nothing to do with ignorance of programmers.

  164. rsync 2.5.6 security advisory by Blademan007 · · Score: 1

    http://rsync.samba.org/index.html

    The rsync team has received evidence that a vulnerability in rsync was recently used in combination with a Linux kernel vulnerability to compromise the security of a public rsync server. While the forensic evidence we have is incomplete, we have pieced together the most likely way that this attack was conducted and we are releasing this advisory as a result of our investigations to date...

  165. Re:What OS was the compromised box running? by Rich0 · · Score: 1

    If running Gentoo, I wonder if they were using gentoo-sources for the kernel? It includes the grsecurity patches, which in theory make this sort of thing more difficult (although I'm not sure if they stop this particular exploit or not).

    I just can't wait until grsecurity is ported to the 2.6 kernels...

  166. Combined rsync + kernel vulns by Bytal · · Score: 1

    seem to be responsible for this breakin. The information has already been posted to Bugtraq by a gentoo team member. Here is the post text:

    Background

    The rsync team has received evidence that a vulnerability in rsync was recently used in combination with a Linux kernel vulnerability to compromise the security of a public rsync server. While the forensic evidence we have is incomplete, we have pieced together the most likely way that this attack was conducted and we are releasing this advisory as a result of our investigations to date.

    Our conclusions are that:

    - rsync version 2.5.6 contains a heap overflow vulnerability that can be used to remotely run arbitrary code.
    - While this heap overflow vulnerability could not be used by itself to obtain root access on a rsync server, it could be used in combination with the recently announced brk vulnerability in the Linux kernel to produce a full remote compromise.
    - The server that was compromised was using a non-default rsyncd.conf option use chroot = no. The use of this option made the attack on the compromised server considerably easier. A successful attack is almost certainly still possible without this option, but it would be much more difficult.
    Please note that this vulnerability only affects the use of rsync as a rsync server. To see if you are running a rsync server you should use the netstat command to see if you are listening on TCP port 873. If you are not listening on TCP port 873 then you are not running a rsync server.

    New rsync release
    -----------------

    In response we have released a new version of rsync, version 2.5.7. This is based on the current stable 2.5.6 release with only the changes necessary to prevent this heap overflow vulnerability. There are no new features in this release.
    We recommend that anyone running a rsync server take the following steps:
    1) update to rsync version 2.5.7 immediately
    2) if you are running a Linux kernel prior to version 2.4.23 then you should upgrade your kernel immediately. Note that some distribution vendors may have patched versions of the 2.4.x series kernel that fix the brk vulnerability in versions before 2.4.23. Check with your vendor security site to ensure that you are not vulnerable to the brk problem.
    3) review your /etc/rsyncd.conf configuration file. If you are using the option use chroot = no then remove that line or change it to use chroot = yes. If you find that you need that option for your rsync service then you should disable your rsync service until you have discussed a workaround with the rsync maintainers on the rsync mailing list. The disabling of the chroot option should not be needed for any normal rsync server.

    The patches and full source for rsync version 2.5.7 are available from http://rsync.samba.org/ and mirror sites. We expect that vendors will produce updated packages for their distributions shortly.

    Credits
    -------

    The rsync team would like to thank the following individuals for their assistance in investigating this vulnerability and producing this response:
    Timo Sirainen <tss iki.fi>
    Mike Warfield <mhw wittsend.com>
    Paul Russell <rusty samba.org>
    Andrea Barisani <lcars gentoo.org>
    Regards,

    The rsync team

  167. Mr. Pot, Meet Mr. Kettle by Anonymous Coward · · Score: 0

    A quick perusal of your posting history shows nothing but attacks on linux and praise for micro-sloth. Douchebag says what?

    Next.

  168. Re:"Reasonably Confident"? by RedHat+Rocky · · Score: 1

    Actually, the ebuilds are shell scripts.
    md5sum is no protection if they are never checked.

    Don't confuse ebuild with spec files from RPM, though RPMs can contain hostile scripts as well.

    --
    Anything is possible given time and money.