Slashdot Mirror


Ubuntu Servers Hacked

An anonymous reader noted that "Ubuntu had to shutdown 5 of 8 production servers that are sponsored by Canonical, when they started attacking other systems. Canonical blames the community, saying they were community hosted, and were poorly maintained. However, kernel upgrades couldn't be done because of poor backwards compatibility with the very hardware that Canonical had sponsored! While people point fingers at each other it is pretty clear that both sides are equally to blame, the community administrators for practicing bad security practices, such as using unencrypted FTP transfers with accounts, not properly maintaining the system. However Canonical should have been well aware of what they are hosting. The question remains, if any of the files distributed to users have been compromised. A major blow for Canonical though who are attempting to enter the business market with Ubuntu Server."

330 comments

  1. New distro name by Anonymous Coward · · Score: 5, Funny

    Spambuntu

    1. Re:New distro name by bshellenberg · · Score: 0

      Oh come on folks.... that's funny (considering the kbuntu, xbuntu etc). Have a sense of humour!

      --
      Karma: Neutered
    2. Re:New distro name by Anonymous Coward · · Score: 0

      Explaining a bad joke will not make it good.

    3. Re:New distro name by angrykeyboarder · · Score: 1

      Well I'm an Ubuntu user and fanboy and I found it funny. :0)

      --
      Scott

      ©20014 angrykeyboarder & Elmer Fudd. All Wights Wesewved
  2. Hacked... by andrewd18 · · Score: 5, Funny

    You keep using that word. I do not think it means what you think it means.

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

      You keep using that word. I do not think it means what you think it means. Truly, you have a dizzying intellect.
    2. Re:Hacked... by slightcrazed · · Score: 0

      Hallo, my name is Ubuntu Canonical. You hack my server. Preparrrre to die!

    3. Re:Hacked... by AHumbleOpinion · · Score: 1

      Hacked... You keep using that word. I do not think it means what you think it means.

      True, it has an entirely different meaning when applied to a FOSS organization rather than a commercial closed source company.

    4. Re:Hacked... by Anonymous Coward · · Score: 0

      Lord, I love The Princess Bride! The comedy is so original and unexpected! Let's recite it a bunch!

    5. Re:Hacked... by Lord+Ender · · Score: 5, Insightful

      Language changes with time. This particular word has changed meanings (or at least got a new meaning) in the English language. You don't have to like that fact, but bitching on slashdot isn't going to change that fact.

      People in the industry are aware that "hack" used to mean "cleverly manipulate a device into doing something its designers did not intend." People also know that "wherefor" used to mean "why." In both cases, the original definitions no longer apply.

      Language changes. You'll get over it. There are more important battles to fight.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    6. Re:Hacked... by KingKiki217 · · Score: 2, Informative

      The problem is that most people don't know these things. Most people seem to think that when Juliet asks "Wherefor art thou, Romeo?" she's asking after his location.

    7. Re:Hacked... by jZnat · · Score: 1

      This is Slashdot where everyone knows what hack really means. This isn't the mainstream media that caters to the lowest common idiot who thinks that the blue E is the internet.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    8. Re:Hacked... by Lord+Ender · · Score: 2, Insightful

      No. I'm saying that today, "hack" ACTUALLY MEANS "to bypass digital security." Insisting we use the older definition of the word because we are not "common idiots" is analogous to an English teachers' website requiring all posts be made in Olde English. Or worse, Middle English. I don't see you advocating we all write like Chaucer so that we can differentiate ourselves from "common idiots."

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    9. Re:Hacked... by Anonymous Coward · · Score: 1, Insightful

      Huh? who uses "wherefore" to mean something other than archaic 'why'? you can't claim linguistic shift just because stupid people tend to misuse a particular word.

    10. Re:Hacked... by Swampash · · Score: 1

      People also know that "wherefor" used to mean "why."

      I've never heard it used to mean anything else.

    11. Re:Hacked... by Hucko · · Score: 1

      Anyone I've ever met who didn't like Princess Bride were universally known to be lacking in the humour department, and thought sarcasm was suitable for each situation. Their favourite method was to add "NOT!!" to the end of a clearly false statement. Of course, my opinion of them in regards to comedy had the same quality.

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    12. Re:Hacked... by 1lus10n · · Score: 0, Troll

      Does that mean i shuld tipe lik dis ? U might th1nk sp33k n33ds to 3volv3 but i lik it just f1n3.
      Point taken ? Just because morons refuse to LEARN doesnt mean we need to cater to them, popular media be damned.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    13. Re:Hacked... by Loopy · · Score: 1

      Sarcasm 1, Lord Ender 0.

    14. Re:Hacked... by Lord+Ender · · Score: 1

      There is certainly a gray area while language changes. But I think "hack" has moved far beyond this gray area. For my entire adult life, almost everyone I knew, most of who are unarguably not morons, understood the new common meaning of the word "hack," not the old meaning.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
  3. Gentoo also recently disclosed security breach by ChazeFroy · · Score: 4, Informative

    This isn't the only Linux distro security breach being disclosed recently. One of Gentoo's web applications was compromised and they are investigating it:

    http://bugs.gentoo.org/show_bug.cgi?id=187971

    1. Re:Gentoo also recently disclosed security breach by dattaway · · Score: 1

      And instead of shooting the messenger and arresting him on terrorism charges, action was taken and he was given many words of thanks for helping to identify the problem.

    2. Re:Gentoo also recently disclosed security breach by jcgf · · Score: 1
      And instead of shooting the messenger and arresting him on terrorism charges

      and it's usually in that order too.

    3. Re:Gentoo also recently disclosed security breach by Anonymous Coward · · Score: 0

      If you read the bug, you will note that there was no compromise, only the discovery of a vulnerability.

    4. Re:Gentoo also recently disclosed security breach by Anonymous Coward · · Score: 0

      But there's a pattern with Debian distros. IIRC, that's 2 breaks in Debian itself, plus this one Ubuntu. There was also a similar problem with Savanah, and one with the FSF (I might be wrong on these ones). Anyways, all of them were with Debian (Ubuntu is Debian).
      You never read about these things with, say, OpenBSD ;-)

    5. Re:Gentoo also recently disclosed security breach by totally+bogus+dude · · Score: 1

      That's because nobody uses OpenBSD. It's too hard to find any boxes to hack!

  4. Don't worry by just_another_sean · · Score: 4, Funny

    This is just a transitional feature designed to make Windows users more comfortable using Ubuntu.

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    1. Re:Don't worry by Anonymous Coward · · Score: 0

      I was wondering how this was going to be spun as a failure for Microsoft. Good job, Sean!

    2. Re:Don't worry by Anonymous Coward · · Score: 0

      And I $ee twitter $howed up to make the $ame point, except that he'$ not joking!

    3. Re:Don't worry by just_another_sean · · Score: 1

      Hey, I yam whats me yams and that's all that me yams.

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    4. Re:Don't worry by jedidiah · · Score: 1

      ...while admittedly it is a bit of a stretch...

      Windows does give you crude and non-secure ftp client by default.

      Any Unix machine is more likely to have an scp client than ftp client.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    5. Re:Don't worry by ryanov · · Score: 1

      Have you ever seen a machine that didn't have an FTP client? Server, perhaps, but there are at least two ways on basically all UNIX machines, if not 3, to get FTP access. Surely that's not likely to change. Server? Perhaps, but I call BS on client.

    6. Re:Don't worry by bog_dan_ro · · Score: 1

      =)) Verrrry funnnny =)).
      This is the best explanation !!! :))

    7. Re:Don't worry by Anonymous Coward · · Score: 0

      I've seen one. Or in fact, many. None of my Gentoo-machines has come with FTP by default. Neither client nor server.

  5. I would like to read a report by QuantumRiff · · Score: 5, Interesting

    Since this is a community based, open source project, I would love in the near future (after the investigation and cleanup are done) to read about how they determined that the machines were compromised, what the attackers did, and more importantly, how Ubuntu cleaned them up...

    This could really help the community as a whole, and I know I would enjoy reading it..

    --

    What are we going to do tonight Brain?
    1. Re:I would like to read a report by Anonymous Coward · · Score: 1

      I suppose that other people contacted them saying "why are your servers attacking ours?"

      Your servers attacking other peoples is normally a good sign you have been compromised.. Didn't you even read the summary?

    2. Re:I would like to read a report by JosefAssad · · Score: 2
      I would love in the near future to read about how they determined that the machines were compromised

      Well. I mean, 5 of 8 machines were already totally owned by the time they worked it out. I don't think documenting the discovery process is going to do anyone any favors. Unless we're going to be composing a Linux Administration HOWTO: Best of Bloopers.

    3. Re:I would like to read a report by Frosty+Piss · · Score: 4, Insightful

      I don't think documenting the discovery process is going to do anyone any favors.

      Isn't that part of the Linux/Microsoft Double Standard? Now, if Microsoft this type of issue and had been less than totally open about the cause and methods, you know as well as I do that there would be a high-pitched wailing from the Slashdot World.

      --
      If you want news from today, you have to come back tomorrow.
    4. Re:I would like to read a report by gmack · · Score: 4, Interesting

      It's important to note that the servers may not have been actually rooted. There is a large number of ssh dictionary breakin attempts on every machine I administrate on several completely different ip blocks. The worst hit is usually my personal server that tended to get hit with several thousand attempts per hour(enough that legitimate logins were a problem) before I installed countermeasures. Even now the countermeasures are locking out 5 to 8 hosts per day.

      They have managed to get user accounts on a few occasions and most of the time they never even attempt to gain root. They just start scanning for new hosts.

      I'm now running a python script called DenyHosts to find and lockout dictionary attacks. "apt-get install denyhosts" for debian users. Even on much more liberal settings than the default it's lowered my cpu load considerably and locks out attacks in the first minute rather than the hour it would otherwise take me to notice.

    5. Re:I would like to read a report by discord5 · · Score: 5, Interesting

      Unless we're going to be composing a Linux Administration HOWTO: Best of Bloopers.

      I could fill about a 100 pages on my own from stupid things I've done and stupid things I've seen coworkers/customers do.

      The funniest one is still one where one of my coworkers nuked /lib on a fairly important machine unintentionally because he just loves his spacebar:

      rm -f /home/user/project /lib/*

      Upon which of course by he proceeded to ask everyone "Hey, suppose I deleted something like /lib, is there a way to get it back?", followed by 10 people laughing, followed by a minute of silence as soon as we realized what machine he just did that on. He never got a root password for an important server after that incident. In hindsight, that was a funny incident, and a valuable lesson to us all (we all became paranoid of rereading what we just typed).

      Yes, we had backups... Yes, tape drives are still slow

    6. Re:I would like to read a report by TheLink · · Score: 1

      On my personal server I just run my ssh server on a different port. One that's not likely for trojans or other stuff to scan.

      Others can go say "bah security by obscurity" for all they like, I think they're mostly stupid/ignorant anyway ;).

      Actually what I do is run the ssh server on 127.x.y.z:someport and internal.ip:someport.

      Then I have the firewall redirect all accesses to external.ip:extport to 127.x.y.z:someport.

      That way even if the firewall rules aren't present (or messed up), it's likely that people outside still can't ssh in.

      If you're paranoid you can skip having sshd listen on internal.ip:someport and do the firewall thingy for internals as well. But you better be careful ;).

      That said, no big deal for me even if i mess up the rules since the actual exposed machine is a virtual machine and I can still vmware console to it :).

      --
    7. Re:I would like to read a report by Anonymous Coward · · Score: 0

      Isn't that part of the Linux/Microsoft Double Standard?

      It may be part of HIS double standard, but a "universal" double standard? Do you honestly view the linux community as one borg-like unit which somehow thinks and acts in unison?

      Come on, this is getting really old. At least recognize that human beings are unique, thinking individuals with brains of their own. You've got one yourself, don't you?

    8. Re:I would like to read a report by Anonymous Coward · · Score: 0

      mod this one up I'm lucky that the one time I remember doing something similar it was of no importance. (though I have lost a drive that wasn't backed up that was important). Where is the extremely_funny_sad_and_educational moderation tag?

    9. Re:I would like to read a report by Nimey · · Score: 2, Informative

      Why the hell did he have root anyway? Only people with /need/ should have root, and then they should just use sudo anyway.

      Your server was poorly administered.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    10. Re:I would like to read a report by _Sprocket_ · · Score: 2, Insightful

      Isn't that part of the Linux/Microsoft Double Standard? Now, if Microsoft this type of issue and had been less than totally open about the cause and methods, you know as well as I do that there would be a high-pitched wailing from the Slashdot World. I'm not so sure this is any kind of double standard. The last time Microsoft was compromised there wasn't a "high-pitched wailing from the Slashdot World" demanding details. Nobody really expected to hear any details. And we didn't get any. I'm sure there were some who would have been interested in them... and others who didn't care. And this is the situation we're in now.

      Some people care about these details and some don't. The parent apparently thinks there's nothing to learn. I disagree. There might be something really interesting in this case. But even if its just a comedy of errors or highlights issues we've known about for years, there is still value. It serves as a reminder for why we take the additional effort to do things "right."

      And so... typical to Slashdot and other public forums... I voice disagreement with the parent poster. It seems we don't have a single voice on the issue. Sorry if that disrupts your concept of Slashdot.
    11. Re:I would like to read a report by u38cg · · Score: 1

      True, but there is only one way to learn that it is really good advice.

      --
      [FUCK BETA]
    12. Re:I would like to read a report by mickwd · · Score: 5, Insightful

      "The funniest one is still one where one of my coworkers nuked /lib on a fairly important machine unintentionally"

      "He never got a root password for an important server after that incident. In hindsight, that was a funny incident, and a valuable lesson to us all (we all became paranoid of rereading what we just typed)."

      I hope the decision to deny him root access was based on more than that one unintentional incident. It could have happened to any of you. After all, why else would it be a "valuable lesson" to you ? Isn't the person who made that mistake the least likely to make it again ? And you did also say you "could fill about a 100 pages on my own from stupid things I've done".

    13. Re:I would like to read a report by nuzak · · Score: 2, Insightful

      > you know as well as I do that there would be a high-pitched wailing from the Slashdot World.

      You mean the high-pitched wailing from the Slashdot World actually stops at some point?

      --
      Done with slashdot, done with nerds, getting a life.
    14. Re:I would like to read a report by gmack · · Score: 1

      Personally I'm not about to try and explain to my parents how to change their ssh port.. It's bad enough as it is trying to walk them through login problems. Also that server has paying customers on it and I have finally trained most of them to use winscp to transfer files.

    15. Re:I would like to read a report by Anonymous Coward · · Score: 0

      If he hadn't been stupid enough to use the root account to delete files in his home directory then the typo would not have done any damage. Yes anyone can make a typo like that, but a good admin would not be using the root account when they don't need it.

    16. Re:I would like to read a report by houghi · · Score: 1

      Another way is BlockHosts and an explanation can be found on this page

      No more then 4 password attempts per host and then playtime is over. For me a minute is even too much time.

      --
      Don't fight for your country, if your country does not fight for you.
    17. Re:I would like to read a report by houghi · · Score: 3, Informative

      That is why I use `rm directory -rf` instead of `rm -rf directory`. It saved me a few times already.

      --
      Don't fight for your country, if your country does not fight for you.
    18. Re:I would like to read a report by saintlupus · · Score: 2, Interesting

      Just to mention, there are some interesting attacks against DenyHosts; check the bugtraq archives for details. Spoofed source packets can be used to block login attempts from any network address, for example, which can be... problematic.

      --saint

    19. Re:I would like to read a report by xenocide2 · · Score: 1

      If you don't think the users are capable of handling the full measure of a given technology, to where it compromises security decisions, then maybe they shouldn't be using it? In other words, if you can't figure out how to change the ssh port, what are you using it for?

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    20. Re:I would like to read a report by Anonymous Coward · · Score: 0

      Doesn't work on all nixen :/

    21. Re:I would like to read a report by Anonymous Coward · · Score: 0
    22. Re:I would like to read a report by Cro+Magnon · · Score: 1

      The best way to learn such things is from someone else's mistake.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    23. Re:I would like to read a report by init100 · · Score: 1

      I hope the decision to deny him root access was based on more than that one unintentional incident. It could have happened to any of you.

      I agree. A couple of years ago, my boss told me about a mistake where he had accidentally struck the emergency power-off button in the server hall, realizing what he had done while hearing all noise slowly die out. I don't blame him, the button was awfully stupidly placed, on a box protruding out into one of the narrow aisles between the computer racks. In addition, it had no cover, and did not require any force to push. Touching it with his elbow was enough.

    24. Re:I would like to read a report by VGPowerlord · · Score: 1

      Aw, too bad I already replied elsewhere in this story. This deserves at least a Funny mod.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    25. Re:I would like to read a report by petermgreen · · Score: 1

      deleting /lib shouldn't be too hard to fix at least on a typical linux distro. All that is in there are very core libraries so you should be able to get away with just copying it accross from a fresh install of the same version of the same distro.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    26. Re:I would like to read a report by crabpeople · · Score: 1

      I dunno dude, granted my linux server at home is mostly personal use but one of the first things I do is change the ssh port. Its not like http where your going to have dumb clients that ports are hard to change in. Its as easy to put an IP in as a port using putty. I find it hard to believe that you are giving your parents a secure shell (with all the knowledge required to use it) and they are incapable of changing a port. I use to have relentless attacks on ssh before I changed the port. At work, all RDP ports that are through the firewall get a random high numbered port. Would you run RDP on its default ports as well?

      It doesnt really matter of course as you have a script based solution in place, but the bots that scan peoples machines are programmed for specific ports. I have never, not once, had a dictionary type attack on my ssh running on unstandard ports, and I use logwatch daily.

      --
      I'll just use my special getting high powers one more time...
    27. Re:I would like to read a report by rtb61 · · Score: 2, Interesting
      Technically speaking, if there was high pitched wailing every time a windows server got hacked (these were not Canonical servers they just pay for them for use and care by others), then nearby star systems would start complaining about the noise.

      Could you imagine the data load if everybody wanted the information about how every windows server that ever got hacked (I assume M$ takes greater care of it's servers than general users, just as Canonical does).

      --
      Chaos - everything, everywhere, everywhen
    28. Re:I would like to read a report by _Sprocket_ · · Score: 1

      Technically speaking, if there was high pitched wailing every time a windows server got hacked (these were not Canonical servers they just pay for them for use and care by others), then nearby star systems would start complaining about the noise. Microsoft's own servers... not just random Windows-based servers. You might have some knowledge I don't have... but compromises of Microsoft's IT assets don't make the public news too often. Which isn't to say its not happening. I know other large well-known organizations who've had plenty of incidents that don't make the news. I wouldn't be surprised if the same applied to Microsoft. But as I don't have inside knowledge and it doesn't hit the news often... to say they have routine issues seems to be, at best, speculation.
    29. Re:I would like to read a report by TheLink · · Score: 1

      Yeah, and when you do get a dictionary type attack on your ssh running on nonstandard ports, it's fair to treat it as a different scenario from the usual port 22 worms.

      It's more worth setting an "alarm" for such a situation than for the port 22 stuff.

      --
    30. Re:I would like to read a report by pAnkRat · · Score: 1

      Your parents should not have to ssh into your server.
      Your parents should not have to ssh into their own server using a differrent port setting.
      You should write a wrapper-script for your parents and stick it on their desktop if really needed.

      --
      we need an "-1 Plain wrong" moderation option!
    31. Re: I would like to read a report by Dolda2000 · · Score: 1
      Heh, speaking of having done stupid things... Not too long ago, a local user account got compromised on my home network because it had a weak password. The attacker hadn't managed to do any local privilege raising, so the attack was isolated to only that user's account. I, wondering what the attacker may be doing, was snooping around a bit in the directories he had created, and since they were 700, I had to be root. While snooping around -- as root -- I found a program he had left behind and wondered what it did, so I ran it. Yeah, that was stupid.

      Well, it gave me a great reason to finally replace the aging FC2 installation with Gentoo anyway...

    32. Re:I would like to read a report by JerkBoB · · Score: 1

      Unless we're going to be composing a Linux Administration HOWTO: Best of Bloopers.

      What an awesome idea! With an embedded MIDI of "Yakety Sax" (from Benny Hill, you philistines) playing in the background... That'd be great.

      --
      A host is a host from coast to coast...
      Unless it's down, or slow, or fails to POST!
    33. Re:I would like to read a report by chaosmind · · Score: 1

      nope - i disagree. the first thing anybody should be told before getting wheel access is "anytime you type something in as root, sit on your hands for a full minute before hitting enter."

      really, this guy sounds like a perfect candidate for limited sudoers access...

    34. Re:I would like to read a report by Anonymous Coward · · Score: 0

      I'm root all day on whatever machines that have trouble. I'm not going to sit on my damn hands for a minute between each command. I'm going to fix the box and be careful about it.

      What you say is just the mindless spouting off of an inexperienced person who reacts instead of thinking. IMHO.

  6. uh ho by FudRucker · · Score: 4, Funny

    Ubuntu made a boobootu

    --
    Politics is Treachery, Religion is Brainwashing
    1. Re:uh ho by everphilski · · Score: 1

      Mark Shuttleworth kiss it and make it all better?

  7. The real test by ZachPruckowski · · Score: 4, Interesting

    The real test is how they react to this, and how they clean up their mess. Everyone screws up, but what separates good people from bad is how they react to problems and screw-ups.

    It sounds like that part at least is still underway, with a meeting (FTA) in "#ubuntu-locoteams on Tuesday, August 14, 2007 at 2:00PM UTC". Seeing as that's yesterday, we should probably reserve judgement a day or two to see how they respond.

    1. Re:The real test by arevos · · Score: 1

      The real test is how they react to this, and how they clean up their mess. Everyone screws up, but what separates good people from bad is how they react to problems and screw-ups. I use Ubuntu, and I love it to bits, but let's not make excuses simply because they're a popular open source organisation/community. It was a screw-up of epic proportions, a complete lack of anything remotely resembling competent security, and if any other company messed up this badly, there'd be no shortage of people pointing out how stupid their mistake was.
    2. Re:The real test by ZachPruckowski · · Score: 1

      I'm not making excuses. This is a rationale, not a rationalization. I think of all security the same way. An occasional slip-up happens. In this case, it was a non-trivial one. If the organization (Ubuntu and its community) goes forth from here and fixes these problems and prevents them from happening again, then they'll be quickly forgiven. If they keep the same staff and the same set-up and don't change much, they'll be scorned.

    3. Re:The real test by xenocide2 · · Score: 1

      Screw up? 5 of 8 LoCo servers were hit. They're for use to organize local regional events, translate, and the like. This is the Ubuntu equivalent of getting your LUG webserver hacked. They were hosted away from the Canonical infrastructure, and have not compromised the internet upgrade delivery system directly, and while I can't be sure, I'd hope nobody was storing GPG keys or the like on a LoCo server.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    4. Re:The real test by arevos · · Score: 1

      Screw up? 5 of 8 LoCo servers were hit. They're for use to organize local regional events, translate, and the like. This is the Ubuntu equivalent of getting your LUG webserver hacked. Ah, my mistake. I saw "production servers" in the title, and the story link didn't do anything to disabuse me of my assumption that these were important servers.
  8. sorry... by cosmocain · · Score: 2, Insightful

    administrators, but:

    who the hell places such exposed servers like these on the net without applying security patches and following simple rules? yeah, the freaking old hardware, compab problems, i sure understand that. but then make a fuss 'bout it. threat to stop maintaining the hardware if the networks cards aren't changed. if that REALLY is the only problem with the hardware which prevented updates, then i just don't understand how the hell this could happen. NICs, even though this would be no consumer hardware, aren't that expensive. if my employees servers were hacked because i did not mind telling him that some crappy piece of hardware prevented me from keeping uptodate with security, i would kindly be removed from my desk. period.

    1. Re:sorry... by ZachPruckowski · · Score: 5, Insightful

      Oh, from the sounds of it, all that you say is well-warranted. They were running a version of Ubuntu from October of 2005, which was obsoleted in April of this year, and they weren't using encryption. This is security 101, and they didn't do it. This does sound a lot more like an administration problem than a software problem.

      Ultimately, I'd say that if this does wind up being an admin problem, then Ubuntu Server will not suffer. The bottom line is that a poorly administered server is a hacker target regardless of the OS.

  9. Update last week hosed my box by morgan_greywolf · · Score: 1

    An update last week hosed by /boot partition. I haven't found any mention of this happening in any of the Ubuntu Forums. Anyone know if this could be related?

    1. Re:Update last week hosed my box by morgan_greywolf · · Score: 1

      s/by/my

    2. Re:Update last week hosed my box by flyingfsck · · Score: 1

      Well, I guess nobody can report it from their hosed boxes...

      Jokes aside, my systems are working, so it probably another issue.

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    3. Re:Update last week hosed my box by Chandon+Seldon · · Score: 1

      Not unless you clicked through a "these packages aren't signed" warning. The package signing system is specifically designed to handle compromised repositories.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    4. Re:Update last week hosed my box by rvqbl · · Score: 1

      I don't think that it is related to the article. But my /boot partition was hosed as well recently. I had been doing several things on my box, so I was not sure if it was an update. You made me think that perhaps it was.

    5. Re:Update last week hosed my box by emj · · Score: 1

      But that kind of sucks, because there is no explanation why the packages aren't signed. So the risk of someone not caring about that warning is very high..

    6. Re:Update last week hosed my box by fdisk3hs · · Score: 1

      I'm the guy that hacked the ubuntu servers, and yes, I put in a glibc update that hoses /boot... now Here's your sign.

  10. sftp by SolusSD · · Score: 3, Insightful

    it amazes me that people even use the plain old ftp protocol for anything important. sftp has been around forever.

    1. Re:sftp by Anonymous Coward · · Score: 5, Interesting

      sftp and scp STILL do not allow anything like a REGET operations. Whenever anyone mentions this they got shot down in flames.

    2. Re:sftp by burner · · Score: 4, Insightful

      rsync works great for many use cases when transfers really need to be resumed.

      --
      MRSH-Recording device, corned beef sandwich with kraut, seafaring bird, and the foamy top of a beverage.
    3. Re:sftp by Anonymous Coward · · Score: 0

      That's because anybody that cares is using rsync over ssh anyway.

    4. Re:sftp by Deagol · · Score: 1

      rsync via ssh? That'll let you pick up where you left off.

    5. Re:sftp by Bacon+Bits · · Score: 1

      SCP doesn't allow it, but SFTP typically does allows resume. Along with directory listings and file deletion, transfer resuming is one of the advantages of SFTP over SCP.

      --
      The road to tyranny has always been paved with claims of necessity.
    6. Re:sftp by jd · · Score: 1

      FTP isn't really the problem, as it's the login part and not the data that needs authenticating usually. Using S/Key or Kerberos to secure the password would be perfectly acceptable in most cases. If you do want to encrypt everything, then what's so wrong with an on-the-fly IPSec session? Tunnel everything over an opportunistic IPSec connection and attackers won't even know what sort of connection you're running, and you still get all of the benefits of classic protocols such as FTP, FSP or rsync. (What? Never used FSP? How dare you call yourself a geek!) In short, there are plenty of ways of getting the same flexibility and power without compromising on security. Problems usually only happen when people assume they must suffer with a high level of risk in order to do what they want. There are always better answers - it only takes better questioners to find them.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    7. Re:sftp by linuxrocks123 · · Score: 1

      I don't think the official sftp client allows reget, but the protocol supports resuming file transfers, and psftp (from the PuTTY suite) does have a reget. A lot of people think of PuTTY as just a set of Windows tools, but the source code is actually quite portable and it runs on Unix-like OSes fine.

      --
      vi ~/.emacs # I'm probably going to Hell for this.
    8. Re:sftp by alphamugwump · · Score: 1

      It amazes me that we don't yet have anything better than the crude hacks that are ftp and sftp. What we need is an honest-to-god distributed, networked, filesystem.

    9. Re:sftp by init100 · · Score: 1

      It amazes me that we don't yet have anything better than the crude hacks that are ftp and sftp.

      SFTP is a crude hack?

      What we need is an honest-to-god distributed, networked, filesystem.

      May I suggest AFS? It is somewhat complicated to set up, but it is very good and used on many large and very large sites.

    10. Re:sftp by Almahtar · · Score: 1

      You can tunnel any protocol through SSH, so if FTP supports a feature they really need that SFTP doesn't, they can just tunnel it. Still no excuses.

    11. Re:sftp by Ben+Hutchings · · Score: 1

      The SSH file transfer protocol supports retrieving byte ranges, so it is possible to implement reget. I made a patch to add it to OpenSSH some time ago, though it has not been merged.

    12. Re:sftp by burner · · Score: 1

      FTP is going to have problems because it actually uses two ports. One for control, one for data transfer. The control channel should tunnel just fine, but you'll run into problems on the data channel.

      --
      MRSH-Recording device, corned beef sandwich with kraut, seafaring bird, and the foamy top of a beverage.
  11. Driver issue by Oddscurity · · Score: 1

    The article itself doesn't mention a lot more than the summary. What really puzzles me is this part: "and no upgrades past breezy due to problems with the network cards and later kernels."

    From the Breezy Badger release notes: Linux 2.6.12.6

    So how come there's a problem in getting that driver going under 2.6.22 (for example)?

    --
    Indeed!
    1. Re:Driver issue by Foktip · · Score: 2, Informative

      Heh, compatability with new hardware is part of the reason i started using Gentoo... even though Ubuntu uses new software, i've always had at least some problems getting either Broadcom or Nvidia network-cards working on generic-distro kernels. Were they using custom-made kernels, or the stock one?

    2. Re:Driver issue by Anonymous Coward · · Score: 0

      You do realize that the kernel development process and version numbering policy changed, a rather long time ago?

    3. Re:Driver issue by Technician · · Score: 1

      What really puzzles me is this part: "and no upgrades past breezy due to problems with the network cards and later kernels."

      I put together a new machine Core 2 Duo on a new Asus board. I put Fiesty Fawn on it. It works great. I did notice a networking problem with the built-in NIC when trying to transfer large files to my fileserver. (DVD ISO) It would start and then hang with less then 1K transfered. Web, small transfers and such worked fine. I finaly had to make a SMB share on the machine and use my Dapper Drake laptop to transfer the file from that machine to the fileserver.

      When I get some time, I'll stick in another NIC and see if that fixes the problem. I have a Intel card and a D-Link card I can try.

      --
      The truth shall set you free!
    4. Re:Driver issue by PalmKiller · · Score: 1

      What I don't understand is why they couldn't use the old kernel with the new release...the linux release should not necessarily tie them to a particular kernel.

      Or do as I do at times (and as Oddscurity was suggesting I think) and use the old network card driver with a newer kernel ... this normally works fine by building it as a module unless something major changed in the way the kernel works with network card drivers.

    5. Re:Driver issue by Oddscurity · · Score: 1

      Right, that is what I meant. I expected them to be able to make any changes necessary to the driver (if at all needed between 10 minor versions) and stick it in 2.6.22 with all relevant other patches. Now if as Bruce Perens suggests below the reason is a binary-only network driver, then that's a problem in its own right. Then you'd have expected the Ubuntu guys to shop around for a replacement mainboard, one who's NIC is well supported.

      But you're right as well on using the old kernel with the new release.

      --
      Indeed!
    6. Re:Driver issue by burner · · Score: 1

      In order to better support USB and general hotpluggable hardware, the kernel now moves fairly closely with the related userspace tools (udev, for example), so it may not be as simple as just booting the older kernel with a more recent set of userspace applications. This was particularly true in the 2.6.12 timeframe. It would be an unsupported configuration and, worse, largely untested.

      Now, whether or not this _should_ be the case is another matter, but it is a reason why this isn't necessarily a great idea.

      Don't forget, the old kernel may have vulnerabilities, too, and it won't be getting and updates. Certainly, it's not as bad as having the entire OS be unsupported with security updates, but it is problematic.

      The best thing would be to get the new kernel working by filing bugs and uncovering workarounds.

      I'm still waiting to hear what the exact problem was that prevented the upgrade to 6.06LTS. If they could have gotten there, they'd have security support for 5 years on the server...

      --
      MRSH-Recording device, corned beef sandwich with kraut, seafaring bird, and the foamy top of a beverage.
    7. Re:Driver issue by Constantine+XVI · · Score: 1

      This is a problem with OLDER hardware in newer kernels.

      --
      "I think an etch-a-sketch with an ethernet port would beat IE7 in web standards compliance."
    8. Re:Driver issue by makomk · · Score: 1

      IIRC, in some releases of Ubuntu udev didn't just require the latest kernel, it also required Ubuntu-specific patches that were only in the distro version of the kernel.

  12. Re:Comical by Anonymous Coward · · Score: 0

    ... because people who are PAID are "free from the evil of money"? Obviously such server hacks only occur where sysadmins aren't PAID. If your company server gets hacked it's because they're not paying your sysadmin enough. Hey, I like that one. I'm going to go tell my boss right now.

  13. Unencrypted FTP? by Anonymous Coward · · Score: 0

    Say what??? Are they nuts? Were they also using telnet?

    1. Re:Unencrypted FTP? by Mr.+Roadkill · · Score: 1

      Say what??? Are they nuts? Were they also using telnet?
      On their unpatched Ubuntu boxes? Of course not... they reserve that little treat for their unpatched Solaris boxes.
  14. updates last night by Anonymous Coward · · Score: 0

    So lets say that I installed a fresh copy of fiesty fawn last night, and was doing updates from about 8pm until 11pm EST (yes it took so long, the servers were THAT slow, and this is probably why). Should I be at all worried that the system might be compromised?

    1. Re:updates last night by mhall119 · · Score: 1

      Ubuntu's packages are all signed, so unless you agreed to install unsigned packages (there should have been a warning telling you that was what you were doing), you should be fine. From my experience, if the package signature has a problem (package doesn't match the signature, meaning it's been modified) apt will refuse to install it, and bail out with an error message saying that signature verification failed. So you should be fine. It seems all the hackers were doing was using the servers at drones to attack someone else, probably didn't even need root access.

      --
      http://www.mhall119.com
    2. Re:updates last night by LurkerXXX · · Score: 1

      He said he installed a fresh copy. If he did it from a copy he got from them, the package verifier could very well have been disabled so it wouldn't throw an error.
      If he trusts that install he's crazy.

    3. Re:updates last night by mhall119 · · Score: 1

      He could check his ISO against the MD5 hashes from Canonical. But regardless, the breach was in community outreach servers, not distribution servers, so he has nothing to worry about.

      --
      http://www.mhall119.com
  15. Kernel security flaw? by Anonymous Coward · · Score: 0

    However, kernel upgrades couldn't be done because of poor backwards compatibility with the very hardware that Canonical had sponsored!

    The poster is highlighting an almost completely irrelevant issue, how many security flaws are accessible in the kernel remotely? Its the applications on top, either incredibly bad administration leaving a hole, unencrypted passwords flying over the network, or regular easily guessed passwords.

    Yes, its going to be inconvenient administration wise, but its not that difficult to upgrade the distribution and leave the kernel behind. The caveat is having to be extra secure on admitting remote users to protect against known local exploits.

  16. Not like Debian by Bruce+Perens · · Score: 5, Informative
    This happpened to Debian once. I remember the very careful quality of the notifications, and the forensic analysis, and the fact that it was caught quickly and there thus wasn't much damage. It showed that a volunteer community can be right on top of this sort of problem with as much or more professionality than any paid staff. It's unfortunate that the configuration of Ubuntu and its loco teams has them pointing fingers at each other. And what about those systems that can't be upgraded? Are they, per chance, using proprietary network drivers? If so, well, folks should know better.

    Bruce

    1. Re:Not like Debian by simong · · Score: 1

      The Debian servers were down for what seemed like ages though, which was frustrating for me as I was trying to build a few machines on it at the time. When providing a public service, there has to be a balance between fixing the problems and making sure that the service isn't down for too long.
      I would assume that the Ubuntu source is safely stored offline somewhere and can be recovered but one of the lessons that has to be learned is the value of a standardised production environment that's been designed in a secure way. Horse and stable door for sure but these are the requirements that are paramount in a production system that is delivering what is becoming high profile software.

    2. Re:Not like Debian by soupforare · · Score: 4, Funny

      Maybe they should've been running deb stable. ;)

      --
      --- Do you believe in the day?
    3. Re:Not like Debian by un1xl0ser · · Score: 1

      There is no word on what was compromised exactly, but network drivers shouldn't affect their ability to update the userland portion of Ubuntu whatsoever. That is assuming that there was a remote exploit in one of the services that they ran, and that someone didn't just sniff their unencrypted FTP authentication.

      --
      v4sw6PU$hw6ln6pr4F$ck 4/6$ma3+6u7LNS$w2m4l7U$i2e4+7en6a2X h
    4. Re:Not like Debian by Anonymous Coward · · Score: 1, Funny
      It's unfortunate that the configuration of Ubuntu and its loco teams has them pointing fingers at each other.

      Who are you calling crazy???

  17. laziness and excuses by bl8n8r · · Score: 1

    It's all the same. You can lock up a system tighter than a dolphins ass, but no security in the world can mitigate pebkac.

    --
    boycott slashdot February 10th - 17th check out: altSlashdot.org
    1. Re:laziness and excuses by andrewd18 · · Score: 1

      You can lock up a system tighter than a dolphins ass
      How tight is that, exactly? Since you seem to have some experience, could you demonstrate for us?
    2. Re:laziness and excuses by k_187 · · Score: 1

      Simple, see that Cat5 cable coming out of the back? Pull it out.

      --
      11 was a racehorse
      12 was 12
      1111 Race
      12112
    3. Re:laziness and excuses by hahiss · · Score: 1

      Ah, the Troy McClure school of security metaphors!

      (You might remember him from http://en.wikipedia.org/wiki/A_Fish_Called_Selma )

      --
      "Every decent man is ashamed of the government he lives under." - H.L. Mencken
    4. Re:laziness and excuses by Fred_A · · Score: 4, Funny

      I've seen lots of dolphins but none of them had CAT5 coming out of their ass.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    5. Re:laziness and excuses by Anonymous Coward · · Score: 0

      I did see some with fricken' lasers on their hea... No wait, those were sharks.

    6. Re:laziness and excuses by Gabesword · · Score: 1

      Airtight.

    7. Re:laziness and excuses by Constantine+XVI · · Score: 1

      Me, to $RANDOM_EMPLOYEE: Hey, you see that machine there? I need you to plug the Cat5 cable back in for me (slides a jackson)
      ***$RANDOM_EMPLOYEE plugs machine back in, un-securing the machine.

      --
      "I think an etch-a-sketch with an ethernet port would beat IE7 in web standards compliance."
    8. Re:laziness and excuses by k_187 · · Score: 1

      If you're close enough to a machine to point at it, then you're close enough to do whatever you want to it, security be damned.

      --
      11 was a racehorse
      12 was 12
      1111 Race
      12112
    9. Re:laziness and excuses by stuktongue · · Score: 1

      ... or, presumably, at least water tight. :-)

  18. how ironic by Anonymous Coward · · Score: 4, Insightful

    had these been windows servers we would have heard cries of a flaky operating system being the problem. in this case, since they're linux servers, we hear that the fault lays on the administrators of the boxen for not hardening the systems?

    1. Re:how ironic by Ginger+Unicorn · · Score: 2

      perhaps it's true.

      --
      (1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
    2. Re:how ironic by deftcoder · · Score: 2, Insightful

      That's because with Linux, you actually *CAN* harden your system. (e.g. kernel-level security patches, exec-shield, SELinux, etc.)

      --
      Peace sells, but who's buying?
    3. Re:how ironic by Anonymous Coward · · Score: 0

      Well, considering if they had left the default install as is this wouldn't happen the fault does lie with the administrators. They opened up services that have notoriously poor security and did not take the proper steps to secure them. FTP services shouldn't even be available to install straight from CD anymore. You should have to apt-get it with warnings as to how insecure it is (plaintext, what?). It is a flawed protocol. Maybe they should go a step further and have SFTP replace FTP as the default "ftp" package and if you want a crappy old ftp client/server call it iftp/iftpd for insecure-ftp or iwannabehacked-ftp. Although with iftp you might have mac fans installing it thinking it must be the best possible ftp.

      --David

    4. Re:how ironic by Super_Z · · Score: 3, Informative

      If you had bothered to read the originating mail ( https://lists.ubuntu.com/archives/loco-contacts/20 07-August/001510.html ), you would have seen that these servers were hacked through unpatched 3rd party web-applications running on these servers - namely:

      art-web, gallery, drupal, phpmyadmin, wordpress, postnuke, phpbb,
      smf, moodle, planet, aspseek, moin, taskfreak, cms made simple,
      mediawiki, ...

      Your argument is whiny and offtopic.

    5. Re:how ironic by Goaway · · Score: 1

      You know, while that is true, it in no way refutes the grandparent's argument.

    6. Re:how ironic by Anonymous Coward · · Score: 0

      Naw. If these were Windows servers running regular unencrypted FTP, I think we'd know who was really to blame.

      Remember when that recent telnetd vulnerability in Solaris came out. Wasn't the response on Slashdot something like "who runs an unencrypted login server anymore"? It'd be like that.

    7. Re:how ironic by Super_Z · · Score: 0, Redundant

      And I am in no way going to be bothered refuting an argument that is based solely on someones general impression.

    8. Re:how ironic by Anonymous Coward · · Score: 0

      Yes sure this "absolutely" prooves that Linux is just as insecure than Windows, let alone the fact that low profile windows systems are hacked within minutes of going online while these hi-profile corporately hated wikies standed so many months with a 3 year old OS, no kernel pathes, faulty hardware and lazy; encryption unaware admins, no they are just the same fucking thing.

    9. Re:how ironic by Anonymous Coward · · Score: 0

      You know, while that is true, it in no way refutes the grandparent's argument.

      Precisely my thoughts.

      Posted as AC to avoid mods who believe the "me too" posts are redundant. (These posts show support and as such are NOT redundant, fools.)

    10. Re:how ironic by Goaway · · Score: 1

      Then why did you reply in the first place?

    11. Re:how ironic by Super_Z · · Score: 1

      Because I wanted to point out that his argument was whiny and offtopic?

    12. Re:how ironic by Goaway · · Score: 1

      If that's what you wanted to do, what was that whole spiel about?

    13. Re:how ironic by The_Skipster · · Score: 1
      Yes sure this "absolutely" prooves that Linux is just as insecure than Windows, let alone the fact that low profile windows systems are hacked within minutes of going online while these hi-profile corporately hated wikies standed so many months with a 3 year old OS, no kernel pathes, faulty hardware and lazy; encryption unaware admins, no they are just the same fucking thing.

      If you have never heard of the interesting topic of cognitive dissonance, this is a good example to start learning from.

    14. Re:how ironic by LingNoi · · Score: 1

      Mod parent troll

      If your hacked Microsoft operating system was Windows 95 no one would think it would be Microsoft's fault.

    15. Re:how ironic by Anonymous Coward · · Score: 0

      Windows is insecure by default. Linux has to be made insecure.

    16. Re:how ironic by Super_Z · · Score: 1

      If that's what you wanted to do, what was that whole spiel about?
      Spiel? You meant the quote from the mail which indicates that the grandparent was whiny and offtopic? Idiot.
    17. Re:how ironic by Goaway · · Score: 1

      The point here was, you know, that that quote indicated nothing of the sort, and was entirely irrelevant to the original post.

    18. Re:how ironic by Anonymous Coward · · Score: 0

      Posted as AC to avoid mods who believe the "me too" posts are redundant. (These posts show support and as such are NOT redundant, fools.) So you don't win an argument by being right, you win by having more sycophants behind you going "yeah! yeah!"? This isn't fucking recess.
  19. The plan. by Anonymous Coward · · Score: 0

    1. Accuse Microsoft of making insecure procuts and being bloodsucking capitalist vampires.

    2. Praise Linux for being secure and community-made, and hence non-profit.

    3. Shift blame around when security is compromised since nobody knows who's really accountable.

    4. ???

    5. Global Linux hegemony.

  20. Constructively by b1ufox · · Score: 1

    Seriously, better late than never.
    No software is perfect,no package is absolutely secure.
    Its good that these servers were compromised and detected too[i hope withing time].
    This means either admins are not doing their job properly or the culprit packages are buggy.
    Either way it is an eye opener to the community and especially Canonical.
    This calls for better auditing and more effort to be put into security on Ubuntu server systems as well as packages which make their way into Ubuntu.
    This may possibly mean more work for Ubuntu package maintainers and in turn a better product[not the perfect one but a better one].

    --
    -- "Genius is 1% inspiration and 99% perspiration" - TAE --
    1. Re:Constructively by plague3106 · · Score: 2

      I wonder if the tone would be so even headed if this was a recent MS operating system.

    2. Re:Constructively by jedidiah · · Score: 1

      Is there a similar sort of problem in Windows that was fixed 10 years ago and is now something you have to go out of your way to subject yourself to?

      Most Windows problems tend to be about what the system will do by default, not what sort of ways you can screw yourself up if you really try hard and insist on ignoring decades of other people's mistakes.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    3. Re:Constructively by Anonymous Coward · · Score: 0

      The difference is that in the open source community people have an opportunity to respond constructively and participate in solving the problem. In proprietary systems all I can do is complain and gripe. The best way to stop people from complaining and griping is to empower them to be a part of the solution. (Not that it always works- some people just like to complain)

    4. Re:Constructively by plague3106 · · Score: 2, Informative

      Is there a similar sort of problem in Windows that was fixed 10 years ago and is now something you have to go out of your way to subject yourself to?

      Ten years ago Linux was barely 1.0. The problem wasn't fixed as long ago as you pretend it was.

      Most Windows problems tend to be about what the system will do by default, not what sort of ways you can screw yourself up if you really try hard and insist on ignoring decades of other people's mistakes.

      The defaults have not been an issue since before that flawed kernel was released. Why do zealots insist on making themselves look stupid by not even being familar with that which they critisize?

  21. Re:Following the M$ example. Re:BWAHAHAHA... by abigor · · Score: 1

    "...but the M$ campus gets hacked all the time."

    Do you have evidence for this? Particularly for the "all the time" part.

  22. Panic, They Might Have Gotten the Source Code! by twitter · · Score: 4, Funny

    It's like NT all over again. God only knows what bad things they can do with that.

    --

    Friends don't help friends install M$ junk.

  23. Re:Comical by Anonymous Coward · · Score: 0

    ... because people who are PAID are "free from the evil of money"? No, if their company server gets hacked through their own negligence then their job is on the line. They have a good incentive to get it right.

  24. Who's next? by Anonymous Coward · · Score: 0

    Ten to one, we hear next week that some large repository of Student papers is vulnerable too.

  25. I'm sorry by thatskinnyguy · · Score: 1, Funny

    This doesn't sound like a hack at all. If "[they] started attacking the other servers", it sounds more like a virus than a hacker. That is, if the servers were genuinely attacking the other servers. It's an exploited weakness nonetheless.

    --
    The game.
  26. This is why packages should be signed by DaleGlass · · Score: 1

    With signatures in place, and verification by default when packages are installed, you'd need more than just breaking into a server to cause serious damage.

    Ubuntu seems to have something in place already, but from my look at it, doesn't seem nearly as insistent on security as it should be.

    1. Re:This is why packages should be signed by realdodgeman · · Score: 1

      Ubuntu 7.10 will come with AppArmor. It is a really good way to secure individual apps.

    2. Re:This is why packages should be signed by Constantine+XVI · · Score: 1

      The packages from the official Ubuntu repositories are PGP-signed, and APT will:
      a) If a signature is not present, it will cough up a big fat warning
      b) If a signature check fails (doesn't match the repo key), it refuses to install

      --
      "I think an etch-a-sketch with an ethernet port would beat IE7 in web standards compliance."
    3. Re:This is why packages should be signed by DaleGlass · · Score: 1

      As far as I can tell, the check isn't done in a default install, you've got to install an apt package and the keyring package for it to work.

      That's a problem in itself, 99% of people won't do that.

    4. Re:This is why packages should be signed by j0ebaker · · Score: 1

      You're right. The packages downloaded by the clients would alert the users that the signatures don't match. About the worst that we would expect is some malicious code to take advantage of the wget commands used from within apt-get to retrieve the packages. Those commands are probably running with root permissions, so if those retrival tools were hackable this could be a much bigger issue. -Joe Baker I Like Ron Paul for President in 2008

  27. Re:Following the M$ example. Re:BWAHAHAHA... by Mattintosh · · Score: 0, Troll

    So you're saying that Ubuntu is especially open to insecurity by association?

    Perhaps that's an attack vector that needs more attention. Sure, you can focus on FTP, but a system is more than the sum of its parts. How insecure is it to leave a system accessible to Windows users on any front?

  28. New NIC, Anyone? by BobMcD · · Score: 1

    no upgrades past breezy due to problems with the network cards and later kernels So wait, this old hardware has no PCI slots? No USB ports? Nothing that could allow one to simply NOT USE THE UNSUPPORTED NIC CARD???

    What the HELL is going on here? This isn't just an 'oops', this is really, really friggen lazy! Last I checked, 3Com and Intel still have about a billion NICs out there in the great wide world. Hell, I could mail them a few myself... ;)

    No?
    1. Re:New NIC, Anyone? by greedyturtle · · Score: 2, Insightful

      It's a lot harder to remotely install a PCI card than it is to complain about it on an internet message board.

    2. Re:New NIC, Anyone? by BobMcD · · Score: 1


      Admin: You see, boss, I wasn't there. I can't exactly reach through the pipes!

      Boss: I see. So should any hardware fail, it can never be replaced? No one has any kind of physical access to the hardware at all? I suppose the servers are encased in concrete??

      Admin: Well no. Not exactly...

      Sure, that'll fly. I'll use it on my boss. "I couldn't replace the drive from home, and didn't feel like driving in, sorry."

      Sheesh

    3. Re:New NIC, Anyone? by jedidiah · · Score: 1

      No it isn't.

      Call the datacenter. Scream at the staff. Scream at the staff some more if the NIC isn't installed after the first round of screaming.

      It's not as if the datacenter isn't dying to help you for a fee.

      That's not even getting to the mind numbingly obvious option of schlepping over to the datacenter.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:New NIC, Anyone? by Anonymous Coward · · Score: 0

      Actually, many servers - particularly the thin, blade type U1/U2 format servers - don't have any expansion slots other than for new HD's. You really only want one, maybe two network connections for a server at a time, and usually the second would be for redundancy.

      These NICs are often integrated into the motherboard and not upgradeable in any way. Unless something breaks or the whole server is very outdated, there is usually no need to upgrade the nic, as it's generally running at least fast ethernet these days, if not gigabit ethernet to its switch.

      Servers are definitely NOT anything like your home PC, you can only make the comparison in a general hardware sense. I.E., your home PC may have an intel mobo and an intel processor, and the server may have those as well, but just about all the details involved there are extremely different. For example, I bet your home PC doesn't sit a couple inches high and have two quad-core processors and gigabit ethernet ports in it...

    5. Re:New NIC, Anyone? by greedyturtle · · Score: 1

      Hence the word 'harder,' although I suppose tipping the hat for you guys and saying 'less convenient' would be more appropriate.

  29. Further proof.. by HerculesMO · · Score: 5, Funny

    Linux systems are only as secure as the admins who manage them.

    And for bonus "hate" points, even MS servers can be secure if they are admined probably. Don't worry though, I have my flame suit on. :)

    --
    The price is always right if someone else is paying.
    1. Re:Further proof.. by manifoldronin · · Score: 1

      ...even MS servers can be secure if they are admined probably. Don't worry though, I have my flame suit on.

      And evidently leaving your proofreading cap home. 8-)
      --
      Tyranny isn't the worst enemy of a democracy. Cynicism is.
    2. Re:Further proof.. by martinQblank · · Score: 1

      "... even MS servers can be secure if they are admined probably..."

      Pretty sure you meant to say "properly" but your version sort of works too...

      And as many of us would agree, an MS server CAN be secured against all attacks. So long as you never plugged it in.

  30. Re:Comical by blueZhift · · Score: 1

    Heh heh, the malicious person doesn't even need money as a motivator. In this particular case, I don't see how anyone would profit anyway, at least monetarily.

  31. Some clarification by joe_cot · · Score: 5, Informative

    As one of the people affected by this issue, I'd like to give some clarification on this. Firstly, the servers affected were Local Community (LoCo) Team servers, of which I maintain ubuntu-us.org While I'm personally annoyed that the site is down (given it was on the front page of Digg last week), these servers are far from "production" servers; they host LoCo team resources and websites. I'd like to know what "compromised" software would have been downloaded by users, given that these servers did not host user repositories, and for the most part hosted news pages, blogs, and localized documentation. The issues were twofold: the servers were not upgraded past breezy, leaving them open to vulnerabilities after Breezy's EOL; LoCo team users were running an array of web applications (Drupal, Wordpress, Mediawiki, etc), but not updating their systems with new security patches. Top that with ftp logins and no ssh keys, and you have yourself a problem. Canonical is moving the installs to their facilities, retrieving the data, and building the installs (including the aformentioned web applications) from scratch, assuming that everything has been compromised. Hopefully in the next few days this will all be over.

    1. Re:Some clarification by pembo13 · · Score: 1

      You all should have hosted those servers on RHEL with some tight SELinux policies.

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  32. Re:Following the M$ example. Re:BWAHAHAHA... by Anonymous Coward · · Score: 2, Insightful

    It has nothing to do with dumbing it down for Windows users making it insecure, although I admit, this case is again a demonstration that the bigest secuirty hole on a computer is the lump of carbon/hydrogen/oxygen located between the keyboard and the chair.

    They got arrogant, cocky and lazy. They let their security slip on things a Windows uers wouldn't use or care about (ex. FTP vs SFTP, from a user perspective, the difference is minimal).

    Does your reality distortion field go so far as to say that Windows is causing functional breakage in Linux now? Geeze. Lemme guess, you are gonna add global warming, wars, AIDS, ebola and the common cold to the list as well, right?

    Heck, fairly certain that ftp wasn't active by default on my last install of Ubuntu (I know SFTP was though).

    FTP vs SFTP - maintainer arogance/incompetance
    Kernel couldn't be upgraded given the hardware supplied by Ubuntu's owning company - the companies own problems

  33. Did they file bug reports? by khasim · · Score: 1

    Okay, maybe Canonical gave them hardware that was not ... or ... was ... okay, this is just difficult to conceptualize.

    The NIC's worked fine with version A.

    The NIC's did not work with version B. Where's the bug report?

    Breezy - this is where they stopped.
    + 6 months - Dapper - LTS, where is the bug report?
    + 12 months - Edgy - a bug report?
    + 18 months - Feisty - a bug report?

    If you just CANNOT apply a patch then you HAVE TO make sure that EVERYTHING else is locked down AND INCREASE YOUR MONITORING OF THAT SYSTEM.

    It looks like the admins made too many mistakes. I can fault Canonical IF there was a bug report filed and pursued.

    Everything else is the admins' fault. No matter how stable and secure a system is, and by default Ubuntu ships with no open ports, a bad admin can break it.

    1. Re:Did they file bug reports? by jhol13 · · Score: 1

      If you just CANNOT apply a patch Could it be so that the problem is exactly here? I mean WHY they could not apply. It was claimed that some of the hardware no longer worked. The only reason I can imagine is that some driver got broken and/or was not supported by later kernel.

      Hmm ... perhaps, just perhaps, this could have been avoidable by a stable binary interface in the kernel ... no, I would say it would be more than likely.
    2. Re:Did they file bug reports? by just_another_sean · · Score: 1

      Hmm ... perhaps, just perhaps, this could have been avoidable by a stable binary interface in the kernel ... no, I would say it would be more than likely. Or, even better IMHO, they could of spent a couple of hundred US$ on getting new NICs that used open source drivers.

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    3. Re:Did they file bug reports? by Anonymous Coward · · Score: 0

      What on earth makes you think they did not use NIC's with open source drivers?

  34. Re:Following the M$ example. Re:BWAHAHAHA... by Minwee · · Score: 5, Funny

    Well, if they _did_ get broken into all the time, then that would be pretty embarrassing. The last thing they would want to do is publicize the fact, so it only makes sense that they would cover it up and say nothing about it.

    Since nobody has _ever_ said anything about frequent break-ins, it's clear that they must be happening.

    Why am I the only person who can see how obvious this is?

  35. Nonsense. This story's a hoax. by Anonymous Coward · · Score: 1, Funny

    Linux servers don't get hacked. Period.

  36. In other news... by thatskinnyguy · · Score: 1
    I can see it now: Ubuntu pushing out a hacked patch that makes all the term screens read by default:

    [root@localhost]# All your Ubuntu are belong to us. Make your time. HAHAHA!
    --
    The game.
  37. Thank Goodness! by Anonymous Coward · · Score: 0

    I wonder if these are the same servers that Ubuntu users get updates from.

    If they were successfully attacked by the threat level of script kiddies, then it's likely that they were compromised earlier by higher threat levels, eg. large corporations or governments. Such a crude method of spreading speaks of a zombie net, and would have been harmless to Ubuntu's users, but the bad guys from other threat models may have created backdoors, keyloggers, and other rootkits on every updaters' computer.

    Not that the big fish won't be able to work their way back in once Ubuntu is back up, but at least we'll have a reprieve and they'll have to use more resources.

    Yes, I sleep in my tin foil nightcap.

    1. Re:Thank Goodness! by joe_cot · · Score: 1

      I wonder if these are the same servers that Ubuntu users get updates from.

      They're not. The repository servers are controlled and maintained by Canonical. These were community-run servers for hosting Local Community Teams. You can take the tin foil hat off now.

  38. It happens by popeydotcom · · Score: 4, Informative

    Firstly these servers were not "Canonical Hosted" as the anonymous readers suggests. They were hosted in a DC which Canonical paid for, but the community maintained them. So Canonical system admins had very little to do with them.

    My site - http://screencasts.ubuntu.com was one of them that was affected, so I was of course concerned that there might be some data loss. I only use SCP to copy files up to the site, and logon with my ssh key, so don't think that all Ubuntu community members are using FTP, weak passwords and really old software, it only takes _one_ though to naff it up for everyone else.

    The Canonical system admins (on top of the work they already do) migrated the services from those servers to their own DC very quickly. My site went down on Tuesday and was back by Friday. For free hosting and oodles of bandwidth, I'm happy with that downtime - for a community site.

    1. Re:It happens by a.d.trick · · Score: 1

      Why is FTP even enabled? For anonymous transfers it makes a little bit of sense, but having it available for authenticated users is a exploit waiting to happen.

    2. Re:It happens by popeydotcom · · Score: 1

      Good question. I don't know. I know it's a protocol that lots of web-newbies ask for. I guess someone made the duff decision to allow it.

    3. Re:It happens by Nimey · · Score: 1

      If you get root on the next box, you should be a BOFH and let nobody but yourself and one or two trusted people have root access via sudo.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    4. Re:It happens by Anonymous Coward · · Score: 0

      how about a screencast showing how to get wireless to work with Ubuntu. what a pain in the ass.

    5. Re:It happens by popeydotcom · · Score: 1

      It's in the works :)

  39. Re:Following the M$ example. Re:BWAHAHAHA... by twitter · · Score: 0, Flamebait

    "...but the M$ campus gets hacked all the time." Do you have evidence for this? Particularly for the "all the time" part.

    No, but if M$ can't guard their precious source code, what can they guard?

    --

    Friends don't help friends install M$ junk.

  40. Idiot by Anonymous Coward · · Score: 0

    Yes, it means exactly what he thinks it means. This whole thing with calling hackers "security researchers" is just silly beyond belief. Both of these little peccadilloes in terminology are reasons that no one who really counts takes the Slashsnot crowd very seriously.

    1. Re:Idiot by Anonymous Coward · · Score: 4, Funny

      And to think, the only reason I post here is so I can be taken seriously by the people who really count.

      Another dream shattered!

    2. Re:Idiot by Egdiroh · · Score: 2, Insightful

      Yes, it means exactly what he thinks it means. This whole thing with calling hackers "security researchers" is just silly beyond belief. Both of these little peccadilloes in terminology are reasons that no one who really counts takes the Slashsnot crowd very seriously.

      I don't think you know what he thinks it really means. I think he want's to use hacking as a generic term, for doing stuff as in "I hacked together a working PC form all the junk in my basement" or "I hacked that new feature into my existing code.", and so the poster and many people who like using the word hacker for themselves but don't want others to immediately associate themselves with criminal hackers, tried to coin a new term for those people, "crackers". And while that term never caught on people who want you to call criminal hackers crackers, will always make issue of calling them hackers in the hope that one day they might call themselves hackers, with out any of the negative connotations.

      Interestingly enough many people who take that position try to use defend their strictly non-criminal activity use of the word by citing the famous MIT non computer hacks. The irony of this of course is that many of those involved minor criminal activity like breaking and entering.
    3. Re:Idiot by Marty_Krapturd · · Score: 2, Insightful

      An individual or a group can try to make a term mean one thing or another thing, however until popular support for that definition is accepted it's still just wishful thinking.

      As long as I can recall, in the world of computers and main stream media, a "hacker" is a person attempting to circumvent security measures for nefarious purposes (i.e. a Black Hat). Does this mean that you can't tilt at windmills? No. Just keep in mind that you may never win that battle. Can't hurt for trying, though, right? I mean, it's not like anyone is being arrested for being a "hacker" or anything. Oh...wait...

    4. Re:Idiot by VGPowerlord · · Score: 2, Funny

      I propose we coin a new term, "hatters." However, that might make them mad.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    5. Re:Idiot by suckmysav · · Score: 1

      Well, I've worked in the industry since before the IBM PC. Back then, people used to build their own computers from kits and were referred to universally as "computer hackers". This was well computer networks were widely known of and hence well before computer security and the breaking thereof was considered to be an issue.

      The term "hacker" has since been hi-jacked by the popular media to refer to the aforementioned "criminal activity". It was originally used to describe do-it-yourself enthusiasts.

      And yes, I am that old.

      Now, get the hell off my lawn.

      --
      "You can't fight in here, this is the war room!"
  41. Re:Comical by Anonymous Coward · · Score: 0

    I think the answer to that is obvious:

    1. Hack Ubuntu servers
    2. ?
    3. Profit

  42. Sounds like by wytcld · · Score: 1

    It sounds like a compromise based on using a flaw in an ftp daemon to exploit a kernel flaw to escalate privileges. The question I'd have is which ftp daemon were they running? FTP - even the old, unencrypted kind - IMHO can be run with tight security if you choose a daemon that can run in chroot with virtual-account privilege separation for each user. A few daemons do that, and do it well, most don't. So was this a known-problematic ftp daemon that Ubuntu's Loco servers were running, or a fresh exploit against one of the better daemons?

    As for the suggestions that sftp is better, OpenSSH's version of sftp requires a shell account for each user - something good ftp daemon's don't. There are shells like scponly that are pretty good at chrooting each user's shell account - but not necessarily perfect. There are a lot more administrative steps in setting that up than for an ftp account, which if not quite done right can compromise security. FTP's maturity - again with the right daemon - can be a security advantage, over all.

    --
    "with their freedom lost all virtue lose" - Milton
    1. Re:Sounds like by Anonymous Coward · · Score: 0

      It sounds like a compromise based on using a flaw in an ftp daemon to exploit a kernel flaw to escalate privileges.

      Really? based on what? They were passing usernames/password in clear text. Someone doing the FTP'ing may also have had a SSH account on the machine. If they are dumb enough to be doing vanilla FTP for uploads in this day and age, I'll believe any other dumb thing they could do security-wise was probably done.

  43. "tighter than a dolphins ass" by Dystopian+Rebel · · Score: 3, Funny

    Sir, somewhere in the fully-indexed and data-mined future, your descendants will be publicly shamed and ridiculed because of your post.

    I suppose they'll have no choice but to flee to deeper waters.

    --
    Rich And Stupid is not so bad as Working For Rich And Stupid.
  44. Mod -1 please by greedyturtle · · Score: 3, Funny

    Please mod this -1, I don't agree with him.

    1. Re:Mod -1 please by thatskinnyguy · · Score: 1

      Mod this guy +1 please. He's funny for a smartass.

      --
      The game.
  45. Re:Following the M$ example. Re:BWAHAHAHA... by abigor · · Score: 3, Insightful

    Okay, so your assertion of fact was really just an enormous assumption. Thanks for the clarification.

  46. Soviet? by Jugalator · · Score: 4, Funny

    "Ubuntu had to shutdown 5 of 8 production servers that are sponsored by Canonical, when they started attacking other systems."

    In Soviet Russia, server attack you?

    --
    Beware: In C++, your friends can see your privates!
    1. Re:Soviet? by Anonymous Coward · · Score: 0

      In Corporate America, you are server.

    2. Re:Soviet? by Anonymous Coward · · Score: 0

      No, in Soviet Russia, attackers serve you...

  47. Re:Following the M$ example. Re:BWAHAHAHA... by DogDude · · Score: 1

    This dumb Windows user uses sftp to connect to all of his servers. I don't know where you're trying to go with this troll...

    --
    I don't respond to AC's.
  48. Re:Older cpmpatible NIC, Anyone? by Technician · · Score: 1

    So wait, this old hardware has no PCI slots? No USB ports? Nothing that could allow one to simply NOT USE THE UNSUPPORTED NIC CARD???

    I wonder if they could use some of my NE2000 NICs. They should be compatible. I'll even toss in some 50 ohm terminations.

    --
    The truth shall set you free!
  49. Re:Following the M$ example. Re:BWAHAHAHA... by laederkeps · · Score: 5, Funny

    No, but if M$ can't guard their precious source code, what can they guard?
    Well, I heard that Ubuntu isn't very good at that either...
  50. Ubuntu hacked! by sgholt · · Score: 0, Troll

    uhh...that's what happens when you try to make your linux distro work like windows....

  51. Re:This is a FAILURE of the OPEN SOURCE Community by mhall119 · · Score: 1

    Who said it was a bug? It could be as easy as someone password sniffing on a remote network saw a user log in to the Ubuntu server's FTP service. Once they had a username and password, logging onto the box and running a spam/DoS script against other servers is easy. It's not a bug, it's just an insecure method of accessing a box. Kind of like putting a huge lock on your front door, then leaving the key under the mat.

    --
    http://www.mhall119.com
  52. Turns out the whole reason for the attack was... by bealzabobs_youruncle · · Score: 5, Interesting
    to replace the horrid orange and brown default themes.

    I used to be an ardent Ubuntu supporter but since Dapper and the wider adoption there has been too much emphasis on making things more Windows-like and less on best practices throughout the Ubuntu community (note I said the community, not the developers). Stuff like Automatix and the general feeling that any script that or line of code that is posted on the Ubuntu forums is guaranteed safe has led to lax standards. I've brought this up a couple times and any valid discussion quickly descends into a flame-fest and the mods (rightly so) lock it down.

    The Ubuntu community has bent over backwards so far to prove they can include everyone they lost site of many of the things that make Linux a better choice for many people; time to get back to fundamentals and best practices, the sooner the better. Stop worrying about besting Windows at every silly thing (ahem, desktop transparency), stop trying to include aunt Tilly (who is never going to "switch" anyway) and remember that some things take more effort but are often worth it.

  53. Windoze access should be read only / password free by twitter · · Score: 2, Interesting

    How insecure is it to leave a system accessible to Windows users on any front?

    I won't give an gnu/linux account to any windows user because a minimum of 25% of them are part of a keylogging botnet. They are liable to access my machines from windoze and things go downhill from there, even if they use a better client. A system is only as strong as it's weakest link.

    Ubuntu itself is dangerous because it includes non free software like Adobe Flash, but this should not be of concern to business users. These dangers are orders of magnitudes smaller than those faced by windoze users, but Ubuntu needs more shelter and care than Debian itself. No gnu/linux system is in danger of being auto-rooted like a windoze machine. Business users should continue their move to gnu/linux systems like Ubuntu.

    --

    Friends don't help friends install M$ junk.

  54. "When linux boxen attack" by Anonymous Coward · · Score: 1, Funny

    Next on Fox...

  55. Breaks happens all the time by Pecisk · · Score: 4, Interesting

    It is just became obvious recently that open source publishes their breaks as they are, because they can't actually hide anything. I bet breaks in coorporation servers are so frequent that is common practise to be silent about them.

    In mean time, there is a tradeoff between having one, LTS release which has rather old kernel with old drivers and new one, which has 18 month support but has everything up to date, including also unstable stuff of course. But in fact it doesn't even mather, because admin is who in charge.

    So Linux is more secure than Windows? You bet. Then why such break-ins happens? Because of lazy or hobbist admins who have no time or maybe not enough knowledge to lock down server to protect it from attacks. To lock down such Windows server/workstation is much harder because of "black box" mentality such software has. But it is also possible.

    So in resume - those are admins who are gulty persons here. Ubuntu Dapper and Feisty are secure enough releases to keep them locked down without causing trouble for services. And ohh, be careful to which persons you give access to and have good password management system.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    1. Re:Breaks happens all the time by TheNetAvenger · · Score: 0, Troll

      So Linux is more secure than Windows? You bet

      And this is your 'opinion', as facts don't show this to be true for many years now.

      I have read tons of articles about *nix break ins over the past year, ranging from several Govts around the world to even BSD at Berkley and other universities. Losing everything from secrets to consumer identity information.

      The only Windows stories you hear anymore are when someone loses a non-encrypted laptop or a CD with names in unencrpyted MS Access format is stolen.

      Windows Server 'compromises' are not as 'normal' as you seem to think they are. In fact not since 2001 has Windows Servers even 'registered' on the hack/compromise radar. So after six years of doing a rather good job with high-profile security on some of the most high-profiles sites on the internet, don't you think it is time to let go of the 2001 mentality?

      To lock down such Windows server/workstation is much harder because of "black box" mentality such software has.

      Since when? Windows 2003 server installs by default locked tighter than almost any default *nix distribution, with less active server services. And this is a point and click Server OS, that is so easy to setup, idiots are literally getting by with normal installations without being hacked. Go talk to a company like ServerBeach, Rackspace or other large unmanaged hosting companies that offer both Windows and Linux servers. They confirm that any idiot can turn on Windows Server and be fairly safe.

      Linux has not proven itself to be 'inherently' or 'logistically' more secure than any other OS. Nothing in its design is ANYMORE evolved than any other OS.

      PERIOD.

    2. Re:Breaks happens all the time by TheNetAvenger · · Score: 1

      Just to follow from my post marked 'troll' stating that Linux is NOT MORE SECURE...

      http://blogs.technet.com/security/archive/2007/08/ 16/july-2007-operating-system-vulnerability-scorec ard.aspx

  56. Packages can not be authenticated by Anonymous Coward · · Score: 0

    Off and on over the past two months I would download packages and get that message. I wonder if the server compromise has anything to do with it.

  57. Re:This is a FAILURE of the OPEN SOURCE Community by LWATCDR · · Score: 1

    Well it is only a bug in that they where still using FTP. FTP should be as dead as Telnet. SCP is far more secure and should be the only way one can up load a file to a system. FTP is fine for downloads but that is about it.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  58. Re:Windoze access should be read only / password f by Real+World+Stuff · · Score: 1, Insightful

    You made a good argument, but when you use terms like "Windoze" you lose credibility.

    --
    If we don't fight for ourselves no one will.
  59. Re:Following the M$ example. Re:BWAHAHAHA... by gnn_geeknotnerd · · Score: 1

    Heh, so this is different from every day on /. how?

    --
    That is not dead which can eternal lie, And with strange aeons even death may die.
  60. Re:This is a FAILURE of the OPEN SOURCE Community by JohnBailey · · Score: 1

    why hasn't the community (that means you) spent enough time looking over the code and fixing all those bugs? As the servers were not updated, how exactly would that have saved them? A patch only works if it is applied to the computer in question.
    A past EOL OS, ineffective settings, and less than skilled admins. It couldn't get much worse no matter what system was being used. This is no more Ubuntu's fault than it would be Microsoft's fault if a Windows user gets hacked while surfing using an unpatched computer with the C:\ set as shared and no firewall.

    The exact same thing has more likely than not happened to countless businesses all over the world when they got someone who knew just enough to be dangerous to set up their network. I know of one small business that has their office computers networked over wireless,and the guy who set it up didn't have a clue about security, so I doubt the connection is that secure.
    --
    It is difficult to get a man to understand something when his job depends on not understanding it.
  61. To put this into perspective... by AndyCR · · Score: 3, Insightful

    Thousands of Windows machines get exploited every day, and there's barely a word said about it. 3 Linux machines are exploited, and it's "OH MY GOSH!!111". I don't know whether this is a good thing, a bad thing, or, my best guess, both.

    --
    If there's anyone I hate more than stupid people, it's intellectuals.
  62. Re:Following the M$ example. Re:BWAHAHAHA... by AndyCR · · Score: 2, Funny

    Indeed. I have to question the security of a software company which not only leaves it's source code in public FTP, but, after others discover this mistake, ASKS THEM TO MIRROR IT!

    It boggles the mind.

    --
    If there's anyone I hate more than stupid people, it's intellectuals.
  63. I am what I am and it is what it is. by twitter · · Score: 2, Funny

    I've seen this hundreds of times, but never bothered with it.

    You made a good argument, but when you use terms like "Windoze" you lose credibility.

    People who can't see though my wording probably won't believe the argument anyway. Brainwashing is strangely dehumanizing like that. The victims lose their sense of humor as well as reason. The term "windoze" implies both of those losses and that people who continue to use it are asleep at the wheel.

    --

    Friends don't help friends install M$ junk.

    1. Re:I am what I am and it is what it is. by Anonymous Coward · · Score: 3, Insightful

      What you are is a paranoid narcissist who is too immature to hold a rational discussion.

      Here we are, talking about a serious security breach at a prominent Linux distributor, and all you can muster is a hissy fit because not enough people are blaming Microsoft for it.

      It's not clever. It's certainly not constructive. Worst of all, it reflects poorly on the community you claim to serve.

      You're the rhetorical equivalent of a brick-throwing protester at a WTO meeting, foolishly believing that vandalism and insulting slogans will right the injustices of the world, while earning nothing but contempt from the very people you're trying to convert to your cause. Luckily for you, the "riot police" on Slashdot are only armed with Troll and Flamebait mods.

    2. Re:I am what I am and it is what it is. by Anonymous Coward · · Score: 0

      And name calling is such a constructive form of rational debate.

      Grow up.

    3. Re:I am what I am and it is what it is. by Anonymous Coward · · Score: 0

      Most insightful AC post ever! My compliments.

    4. Re:I am what I am and it is what it is. by Anonymous Coward · · Score: 0

      "Rational debate" is the first victim of any twitter post on Slashdot, so I fail to see how the GP did something wrong.

    5. Re:I am what I am and it is what it is. by Anonymous Coward · · Score: 0

      Hear, hear!

    6. Re:I am what I am and it is what it is. by Anonymous Coward · · Score: 0

      OMGWTFBBQPWND!

    7. Re:I am what I am and it is what it is. by Hucko · · Score: 1

      Well said. And some may say I'm just as pro-linux as Twitter et al and I have in the past fallen into the same trap. Unfortunately, if they say anything significant, it is destroyed by the childish manner in which they argue. The nature of humanity is such that mis-informed behaviours actually work against the proclaimed purpose. One does wonder if that may be the true intended purpose of such posts.

      On another note, I'm just about ready to take up the forms lu, lus, and lun
      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    8. Re:I am what I am and it is what it is. by crabpeople · · Score: 2, Interesting

      At least he had the courage to post under his own username.

      How are those peaceful protests working out for you anyway? Weed is still illegal, the war in iraq went on, and the disparity between the rich and poor is stronger than ever. If one person throws a brick, hes a vandal, if a hundred thousand do it, its a revolution. Thats actually my main problem with protests, their peaceful nature. Its almost like the people just want a shell of a protest to look "cool" while in reality risking nothing of substance for the cause they are fighting for.

      Thats also why I admire martyrs but now i've just gone and marked myself as an offtopic troll.

      --
      I'll just use my special getting high powers one more time...
    9. Re:I am what I am and it is what it is. by The+Bungi · · Score: 0, Flamebait

      At least he had the courage to post under his own username.

      More often than not the people who tend to post logged in to counter twitter's bullshit with, you know, arguments, get nailed by retarded fanboy moderators who think twitter's annoying hyperbolic "let me tell you how it is" tone and puerile creative spelling are kewl. So if at least once in a while a post that tells the truth about the emperor being completely buck naked comes up through the noise, I think that's just fine.

      So far in this article twitter has done nothing more than try to somehow blame some Linux servers getting p0wnd on "M$", probably because under his black and white "join us or die" mantra that simply cannot happen. Which is hilarious because he constantly complains about "paid M$ shills" astroturfing on articles about Microsoft to allegedly confuse and distract people "from the issues".

      You figure this type of behavior is worth defending?

    10. Re:I am what I am and it is what it is. by itlurksbeneath · · Score: 1

      Mighty strong words from an AC. At least GP had a pair and posted under his own name.

      --
      Have you ever considered piracy? You'd make a wonderful Dread Pirate Roberts.
    11. Re:I am what I am and it is what it is. by dedazo · · Score: 1

      I've seen this hundreds of times

      Yeah, for example here.

      Brainwashing is strangely dehumanizing like that. The victims lose their sense of humor as well as reason.

      Your poetic hillbilly effluvia is entertaining, as always.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    12. Re:I am what I am and it is what it is. by Anonymous Coward · · Score: 0

      His own name? You mean the name "twitter"? That's what you consider his "own name"? Unless he's attaching a verifiable full name, address and telephone number, then posting as "twitter" is not really different from posting as "Anonymous Coward".

      Who cares anyway what name they use? The content of the message is the most important thing.

  64. Prevent Windoze at the packet filter by SgtChaireBourne · · Score: 2, Insightful

    You can back up your policy in the packet filter.

    In iptables, look up osf and --genre.

    For pf, look up osfp.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  65. Re:It's "shut down",damn it. by Skrynesaver · · Score: 1

    No, it's a command as in shutdown -h now which is precisely what happened ;)

    --
    "Linux is for noobs"-The new MS fud strategy
  66. Re:Following the M$ example. Re:BWAHAHAHA... by Anonymous Coward · · Score: 0

    u don't think we went to the moon why not tell louis armstrong to his face .

  67. Your Conspiracy-Fu is strong, young Grasshopper! by Anonymous Coward · · Score: 3, Funny

    The last thing they would want to do is publicize the fact, so it only makes sense that they would cover it up and say nothing about it.
    "The complete lack of evidence is the surest sign that the conspiracy is working."

    - Jack Handey

  68. Re:I would like to be a dork by Anonymous Coward · · Score: 0

    "Since this is a community based, open source project, I would love in the near future (after the investigation and cleanup are done) to read about how they determined that the machines were compromised, what the attackers did, and more importantly, how Ubuntu cleaned them up..."

    What utter bollocks. It's pretty clear from even the limited information on the Ubuntu wiki that the root cause of the compromise was incompetent systems administrators engaging in extremely lax security practises - account based ftp access? In 2007?

    Can you spell "looser"?

  69. OT: Sig by XanC · · Score: 1

    Please don't post that signature. I caught a couple of words as I glanced by and nearly had to be rushed to the ER.

    1. Re:OT: Sig by Oddscurity · · Score: 1

      I'll be sure to replace it with Vogon Poetry on the next update. Thanks for the head's up.

      --
      Indeed!
    2. Re:OT: Sig by RESPAWN · · Score: 1

      There were zwei peanuts walking down der strasse. Und one was assaulted... peanut!

      --

      If Murphy's Law can go wrong, it will.

    3. Re:OT: Sig by XanC · · Score: 1

      My dog's got no nose!

      How does he smell?

      Awful!

  70. Re:Comical by MysteriousPreacher · · Score: 1

    With volunteers, they can work as long as the group is pretty well motivated. A volunteer admin can do a superior job if they feel that there is enough prestige associated with them doing things well. You do have to find the good people though, just as you would do with a paid employee.

    --
    -- Using the preview button since 2005
  71. Re:Following the M$ example. Re:BWAHAHAHA... by AvitarX · · Score: 3, Funny

    When someone hacked MS and got a copy of their source code it was headline news.

    I am surprised no one reports how oftem Linux source code is taken from company servers, they must get hacked constantly compared to MS.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  72. Re:This is a FAILURE of the OPEN SOURCE Community by mhall119 · · Score: 1

    Well yeah, you can say it's a "bug" in the process. But that's not something a code review is going to help with, which was the AC's contention.

    --
    http://www.mhall119.com
  73. Re:Windoze access should be read only / password f by somersault · · Score: 1, Offtopic

    That isn't very logical. Everyone knows that Windows is a poor OS, and the term Windoze has been around for well over a decade, for historical reasons (Windows is sloooow) that everyone can still identify with (when Windows runs sloooow even on decent hardware, while other modern OSes work fine) :(

    --
    which is totally what she said
  74. How right you are! by spun · · Score: 4, Insightful

    I've never seen a paid individual make a stupid mistake like this. The captain of the Exxon Valdez was a volunteer with the Red Cross on a humanitarian mission. The Challenger and Columbia were piloted by kids from space camp. The original Tacoma Narrows bridge was designed by volunteers with Habitat for Humanity.

    On the other hand, we all know that segregation & apartheid were both ended by paid professionals. If you want something big done right, only paid professionals can do it.

    --
    - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
    1. Re:How right you are! by Intron · · Score: 1

      To be fair, there was no piloting errors on Challenger or Columbia. Those failures were caused by the volunteer engineering designs of the tiles and boosters done by the Shriners.

      --
      Intron: the portion of DNA which expresses nothing useful.
    2. Re:How right you are! by orzetto · · Score: 1

      I've never seen a paid individual make a stupid mistake like this. [...] The Challenger and Columbia were piloted by kids from space camp.

      I wholeheartedly agree with your point, but do not blame the Challenger's (or for that sake the Columbia's) crew. The Challenger disaster was basically caused by launching the shuttle in too cold weather, so that one of the elastomer O-rings snapped.

      I had a PhD-level course in presentation technique a few years ago, and our two professors spent two whole lectures on "how not to present results" using both the communication that was sent to NASA by a concerned scientist the day before the launch (which lacked name, credentials, abstract, clarity and so on) and the investigation commission report, which incredibly also lacked the single, stupidest piece of presentation that was required: a simple failure rate vs. temperature plot of NASA data, that clearly predicted disaster.

      --
      Victims of 9/11: <3000. Traffic in the US: >30,000/y
  75. Hostage to fortune? by Anonymous Coward · · Score: 0

    Ubuntu 7.10 will come with AppArmor. It is a really good way to secure individual apps.

    Bloody wants to be with a name like that. I'd be sorely underwhelmed if I ran it and an ASCII cow just echoed my words back at me.
  76. Really! by porkrind · · Score: 1

    Yeah, NOBODY uses unencrypted FTP anymore... *sigh*

    -John Mark

  77. Re:Turns out the whole reason for the attack was.. by BobMcD · · Score: 1

    Stop worrying about besting Windows at every silly thing... stop trying to include aunt Tilly Not trying to flame you here, but genuinely curious:

    Isn't this what makes Ubuntu, well, Ubuntu?

    If it were geared toward 'more effort' it would be Debian, would it not?
  78. Re:Turns out the whole reason for the attack was.. by bealzabobs_youruncle · · Score: 1

    True, but it has gone a little out of balance, it walked a fine line in the early days but has gone off the "ease of use" cliff lately. This is mostly a community issue and can be steered back to the right place with some leadership. You can balance an easy introduction and not try to AOL-ify Linux.

  79. Re:Your Conspiracy-Fu is strong, young Grasshopper by value_added · · Score: 1

    "The complete lack of evidence is the surest sign that the conspiracy is working."
    - Jack Handey


    LOL!

    Ya know, I've probably read or owned and one time or another most of the works quoted in Bartlett's Familiar Quotations, but reading this makes me want to trade it all in a for single leather-bound edition of Deep Thoughts.

  80. Re:Windoze access should be read only / password f by Macthorpe · · Score: 1

    The term 'poopyhead' has been around for a lot longer than that. Does it make it any more or less mature?

    --
    "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  81. Re:Turns out the whole reason for the attack was.. by nuzak · · Score: 3, Interesting

    Do you have a specific complaint, or is just it that the uncool kids are getting into the clubhouse? If you think the interface has gotten oversimplified, switch to kubuntu.

    --
    Done with slashdot, done with nerds, getting a life.
  82. Re:This is a FAILURE of the OPEN SOURCE Community by LWATCDR · · Score: 1

    Probably not. But I have to wonder if they where using FTP where they also using telnet?
    FTP and telnet's time have passed. They are useful for a very limited sub set of users.
    SCP and SSH are the LEAST that anyone should do as far securly accessing a remote server.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  83. patch by treak007 · · Score: 1

    There is no patch for human stupidity.

    --
    Klingon Software is not released, it escapes, inflicting terrible damage onto the enemy as it does
  84. Re:Following the M$ example. Re:BWAHAHAHA... by vertinox · · Score: 1

    Since nobody has _ever_ said anything about frequent break-ins, it's clear that they must be happening.

    Lol

    Of course lack of evidence, doesn't mean it didn't happen either.

    --
    "I am the king of the Romans, and am superior to rules of grammar!"
    -Sigismund, Holy Roman Emperor (1368-1437)
  85. Re:This is a FAILURE of the OPEN SOURCE Community by Reapman · · Score: 1

    I've often wondered why we have this lingering hold on FTP and Telnet. I brought up switching to SSH instead of Telnet years ago at my company, our equipment could do it, but got shot down because "it may have it's own insecurities. "

    I'm sure it does, but hacking it is a lot less trivial then some cleartext crap. If they can hack SSH, they probably coulda hacked Telnet in half the time.

  86. Re:Windoze access should be read only / password f by Anonymous Coward · · Score: 0

    Especially when X continues to make my 3.2Ghz PC look like a 386 running Win3.1

  87. Re:I would like to be a dork by Anonymous Coward · · Score: 0

    Can you spell "looser"?

    I sure can. Can you spell "loser"?
  88. How about some XEN? by Britz · · Score: 1

    To everyone their own sever! Just kidding, but imagine that: Too old hardware so you can't upgrade? Never again with hardware virtualization. No I know that this probabely wouldn't work with very old hardware, because the performance loss would be too great, but remember this, when setting up your next system. Time to get into Xen! They promise almost no performance loss with the new processors.

  89. Re:They modded you as funny? GET THE LAST LAUGH! by Anonymous Coward · · Score: 0

    Fuck off spammer, nobody wants to hear about your shitty security site. Kudos for pretending your spam is some sort of hardcore throwdown.
      Me, I scored 438 whatzits on the whoozometer, and none of you rhesus monkeys can beat my score!

  90. Re:Turns out the whole reason for the attack was.. by bealzabobs_youruncle · · Score: 3, Insightful
    See, this is what I'm talking about, you automatically go on defensive if anyone has any honest criticism of Ubuntu. I think I stated some of my issues pretty clearly, but Ubuntu supporters now have thinner skin than Apple users in the 90s. I'm a huge fan of a simple and clean Gnome interface, but I'm against trying to bury the CLI and refusing to learn how to do things properly. I'm against mindlessly installing stuff via Automatix (especially close source and binary blobs) without honestly understanding what you are doing and what the implications are (note several Ubuntu devs agree with this point).

    Again, I am pointing at the community more than the developers, who have provided a great distro that has provided a much needed kick in the pants to other distros to improve their usability. Fedora is my favorite example, and my distro of choice again, since they had to face some stiff competition to stay relevant.

    Ubuntu was about a clean interface with best of breed apps, solid documentation and a community that balanced ease of use with best practices. When someone wandered into the forums with a "noob" question we avoided the "RTFM newb-sauce" stuff and helped them, as well as re-enforcing best practices and linking where to get better information. We didn't point them to untested scripts or recommend subverting security for ease of use, but that is a regular event these days. Shuttleworth wanted "free as in speech" software that was "free as in beer" for everyone, but now to court Windows users he considers installing binary blobs and distributing closed source software? The "Unofficial Ubuntu FAQ" used to handle this stuff very well while not polluting (or introducing possible legal issues) to the distro. I recall Shuttleworth at Debian conferences with his hat in his hand explaining how he wants to help and work with the community, but if you mention this on the Ubuntu forums you have people suggesting that they don't need Debian or the GNU tools? This is an ignorant and arrogant user base that needs to be educated, and in some instances policed.

    The original intent of Ubuntu was great, it just needs to get back on course. I much prefer apt to yum, I hope this wakes up the right people and I will gladly give Ubuntu a shot again.

  91. Re:Following the M$ example. Re:BWAHAHAHA... by An+ominous+Cow+art · · Score: 1

    Lack of absence of evidence may or may not be the same as lack of evidence of absence.

  92. Re:Windoze access should be read only / password f by Nossie · · Score: 1

    not a celeron per chance?

  93. How Ubuntu cleaned them up...Format install Vista by Anonymous Coward · · Score: 0

    LOL

    britches???

  94. Re:Turns out the whole reason for the attack was.. by krmt · · Score: 1

    Debian isn't geared towards 'more effort' or else tools like apt wouldn't have come out of the project. It's geared towards doing things at a high quality, which often necessitates some time and effort to get right. The grandparent's point about automatix is a valid one. Many Ubuntu devs are also Debian devs, and so they carry the emphasis on quality with them, which is why the restricted device manager is as good as it is, in contrast to automatix.

    --

    "I may not have morals, but I have standards."

  95. Lot of Gentoo Infrastructure offline as well by Pop69 · · Score: 1

    http://www.gentoo.org/

    Pile of stuff down at gentoo.org due to a possible command injection vulnerability in their webapp. This doesn't seem to have made any waves.

  96. Re:Turns out the whole reason for the attack was.. by BobMcD · · Score: 1


    Forgive me. What I meant to say was the inverse: Ubuntu is geared towards 'less effort'. Or at a minimum they tend to make as many decisions as possible on your behalf, more so than debian seems to, from my point of view.

    Better?

    My stint with debian ended when I answered a question incorrectly during 'apt-get upgrade'. My fault, to be sure, but the system was hosed none the less. Ubuntu has yet to allow me to make the same sort of critical error. And I appreciate that.

  97. Re:Windoze access should be read only / password f by PitaBred · · Score: 1

    Sounds like you need to upgrade your 4mb PCI graphics card

  98. Re:BWAHAHAHA... by Klaidas · · Score: 1, Insightful

    Uh-oh, he's emphasizing the irony of this, and the irony is towards linux!!! FLAMEBAIT, TROLL, OVERRATED, quick, mod him down untill someone sees it!!!
    /MAJOR SARCASM

  99. Re:Turns out the whole reason for the attack was.. by Zephyr14z · · Score: 1

    My aunt Tilly actually did switch, although only for a few weeks. Bought a mac after that.

  100. Re:Windoze access should be read only / password f by Macthorpe · · Score: 1

    Buzz off, adults are talking.

    --
    "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  101. Protect SSH by disabling password logins by samalone · · Score: 2, Interesting

    On my company's server, I solved the attempted SSH break-in problem by disabling password logins via SSH altogether. Only publicKey logins are allowed. The break-in attempts have completely stopped (or at least they are turned away so quickly that there's not even a security log message for them).

    Only a few computers have my public/private key pair on them (the private key is encrypted, of course), and I keep an extra copy on a USB thumb drive in case of emergency. If someone needs access to the server, I can use one of the existing logins to install their public key so that they can login.

    I highly recommend this solution to anyone who can manage it. It's much more straightforward than trying to maintain blacklists.

    --Stuart

    1. Re:Protect SSH by disabling password logins by init100 · · Score: 1

      On my company's server, I solved the attempted SSH break-in problem by disabling password logins via SSH altogether. Only publicKey logins are allowed.

      This is a very good method. I use it on my home server since I don't want anyone to be able to do a dictionary attack against it. Unless an attacker finds a buffer overflow that can be exploited, he cannot get in, as guessing the key is practically impossible.

      I wouldn't use this method on a large site though, as it would be far too much of a hassle. At work, which qualifies as a large site, we use Kerberos for authentication instead.

    2. Re:Protect SSH by disabling password logins by Anonymous Coward · · Score: 0

      Thanks, that's a really good tip.

  102. Re:Following the M$ example. Re:BWAHAHAHA... by anexkahn · · Score: 0

    Since when is it a problem for someone to gain access to the source code for something that is open source anyway? Is there any reason for Ubuntu to worry about how well guarded the code is?

    --
    Curious about Storage and Virtualization? Check out
  103. Re:OopsBuntu by Anonymous Coward · · Score: 0

    Just wait until _you_ get sued because something was not free/open.

  104. No Suprise by PacketScan · · Score: 1

    Something on this magnitude was bound to happen.. The real question will be how many end users will be afflicted, and what do this mean for relationships with dell and others?

    1. Re:No Suprise by frankenheinz · · Score: 1

      Please . . . say, are you Cort from Santa Monica, the M$ 'architect evangelist' ?

      --
      The law is not an ass. No really.
  105. Re:Turns out the whole reason for the attack was.. by nuzak · · Score: 1

    > See, this is what I'm talking about, you automatically go on defensive if anyone has any honest criticism of Ubuntu.

    No, honest criticism is about actually having specifics to point at, not "zomg, they winblozified it into AOL for all the n00bs!" I suppose I am too sensitive, since I let myself be trolled. Anyway, I'm not an Ubuntu user, I'm back to using vanilla Debian, because it fit my needs better on the server end of things.

    As for Automatix, I'd say the Ubuntu community at large is also quite solidly against using it.

    --
    Done with slashdot, done with nerds, getting a life.
  106. Re:Following the M$ example. Re:BWAHAHAHA... by stonedcat · · Score: 1, Funny

    Linking to your own comments instead of linking to TFA = Fail.

    --
    You can't take the sky from me.
  107. Re:Turns out the whole reason for the attack was.. by bealzabobs_youruncle · · Score: 1

    You aren't too sensitive, but you did ignore the examples I gave in both post. And up until last week the most frequent answer on the Ubuntu forums for many questions was "use Automatix". The only way you can say find trolling is if you completely ignore the rest of my post and seize on a single sentence.

  108. Re:Windoze access should be read only / password f by somersault · · Score: 1

    Poopyhead has no relevance or humour in this situation, unless perchance, someone had a bird shit on their head.. in which case it would be a little funny. Especially if their real surname was Poppyhead or something like that. So there. >_>

    --
    which is totally what she said
  109. Yes -GETTING THE LAST LAUGH!, as per usual... apk by Anonymous Coward · · Score: 0

    "Fuck off spammer, nobody wants to hear about your shitty security site." - by Anonymous Coward on Wednesday August 15, @02:47PM (#20239851)

    First of all: CIS Tool is not "my shitty security site", it's a program that's been noted by SANS & COMPUTERWORLD, as legit/valid & yes, useful.

    I found it INCREDIBLY useful, in helping me to secure my Windows Server 2003 SP #2 system here (above where I had it initially, around a 60.500 score, up to 76.500 iirc, later & FINALLY, to an 84.735/100 score)...

    In fact, I found it SO useful?

    That I did a post @ a widely travelled forums (techpowerup.com) to show Windows users HOW TO GET THE SAME SCORE & LEVEL OF SECURITY I HAVE, right here:

    APK "12 step program" 4 a secure Windows NT-based OS (2000/XP/Server 2003/VISTA):

    http://forums.techpowerup.com/showthread.php?s=4e8 acd2823a55216081bf694304b09df&p=375355#post375355

    (What's in that thread, is FAR MORE COMPREHENSIVE than you find in most articles on "how to secure windows" by FAR... & it just works & much of its based on what CIS TOOL had me do, though it helps only SO FAR, you can figure out the rest, based on that post of mine @ techpowerup.com!)

    PROOF OF MY SCORE ON CIS TOOL, a multiplatform test of security (noted by SANS & COMPUTERWORLD):

    http://img.techpowerup.org/070618/APK14SecurityPoi ntsCISToolResult84735.jpg

    (& I would like to see *NIX folks' results on CIS TOOL as well (it IS multiplatform & java driven - it runs on Solaris, FreeBSD, Linux of many kinds, & yes, Windows NT-based OS'))...

    A fair challenge & it is one, that EVERYONE here can learn by, in fact...

    "Kudos for pretending your spam is some sort of hardcore throwdown." - by Anonymous Coward on Wednesday August 15, @02:47PM (#20239851)

    No pretending @ all: Just facts... ones you can SEE/VERIFY, per my last post (parent to yours I am replying to now in fact), yourself & yes, above in THIS reply to you.

    As to others here who have used various evasions in taking the CIS TOOL test?

    Heh, want a list of over 27-30 of them by now??

    I can produce it, with relative ease (via my bookmarks/favs)... just ask!

    APK

    P.S.=> Yea, "great reply" that, full of technical know-how &/or insight... not (more like an exercise in profanity)!

    Ah... you're just "#31" in my list of evaders of taking the CIS Tool multiplatform test of security (by yet another *NIX user @ /.)... not unexpected @ all!... apk

  110. The only problem by rastoboy29 · · Score: 1

    is the fingerpointing.  I work at a major dedicated server hosting company in tech support.  We see hacked Linux boxen all day long--usually just relatively harmless PHP hacks, as opposed to actual rooting.  The usual solution is to "reprovision" the server and start from scratch--as opposed to analysing the attack vector, patching it, and THEN perhaps starting from scratch.

    No internet server box can ever be 100% secure.  The tale is told in how the owner reacts to the hack.  Fingerpointing is not helpful or encouraging.  Owning up to the problem and fixing it, is.

    1. Re:The only problem by Anonymous Coward · · Score: 0

      I fully agree. This may indirectly be the "fault of" Canonical, but the servers were community hosted. In either case, the details were publicly disclosed and the issue is being handled. There have been meetings held and resolves discussed. I think the situation has been handled as best as possible. Although this situation should not occur, it realistically will occur. I can only speak for myself, but after reading the information disclosed I feel I can at least trust that the issues will be resolved in a timely matter and absolutely will not be ignored.

  111. This is like watching Fox news. by Rick_Clark · · Score: 1

    What a load of misinformation. Both in the article and in the comments. Reading the comments, one would think that the core Ubuntu repositories were compromised, and that Canonical tried to hide it.

    This was published in the Ubuntu Weekly News before it hit slashdot and Canonical held a public meeting about it. The freakin' article links to an official Ubuntu wiki.

    This had nothing to do with the Security at Canonical, or Ubuntu Server, but everything to do with the processes around Canonical sponsorship of community servers.

    Full Disclosure: I work for Canonical, but know nothing about this issue, except what has been made public. I speak only for myself and do not represent the opinions of Canonical.

    Rick

  112. Re:Yes -GETTING THE LAST LAUGH!, as per usual... a by Anonymous Coward · · Score: 0

    You're just "#31" in my list of evaders of taking the CIS Tool multiplatform test of security

      OH I'M SO FUCKING PROUD! It's good to know your list of "evaders" is so easily expanded. I thought it might have been made up of real people who actually talked about how secure their boxes were but then backed down or something. Hah! I should have known it was just anyone who responded to you evar!
      Or did you include the people you posted this shit at, 'cause they "evaded" you by browsing at +5 and so not reading your posts at all? If you forgot to add them, do it now! It'll make your e-penis bragging number SO MUCH MORE IMPRESSIVE, DIPSHIT.

    (by yet another *NIX user @ /.)

      Says who? I'm glad to see I've become another phantom enemy vanquished in your feeble little mind. It gives me a real sense of accomplishment, you know? Like if I had posting long-winded rambling bullshit about some website and gloated about how many people I've imaginary-defeated with my longwinded anonymous score:0 posts that nobody sees.
      I feel so special. Please respond again and tell me how badly I lost! It's fuckin' HILARIOUS!

  113. Typical of Ubuntu by Master+of+Transhuman · · Score: 0, Flamebait

    A LOT of crap "falls through the cracks" with those people.

    Which is why I'm running openSUSE 10.2 now.

    Not QUITE as much crap falls through the cracks with Novell.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  114. Well Known Facts and Obvious Conclusion. by twitter · · Score: 0, Troll

    Okay, so your assertion of fact was really just an enormous assumption. Thanks for the clarification.

    Memory + pattern recognition = intelligence, and some assumptions are safer than others.

    1. M$ uses, or pretends to use, what it calls it's own "dog food" on hundreds of machines.
    2. A minimum of 25% of that dog food is part of a keylogging botnet, say Vint Cerf and Michael Dell
    3. There have been plenty of stories of M$ being burnt, besides the theft of their source code, that show their use is not much different from anyone else's.

    Given the above, it's fair to say that the chances that M$ is virus and botnet free on any given day is virtually no existant. Another way to put that is that someone on the M$ campus is hacked everyday.

    You can keep your denials to yourself because they contradict people's experience and common sense in an offensive way, better known as a bald faced and insultingly stupid lie.

    --

    Friends don't help friends install M$ junk.

    1. Re:Well Known Facts and Obvious Conclusion. by dedazo · · Score: 1
      1. One in ten men are affected by Erectile dysfunction
      2. You have nine neighbours
      Given the above, it's fair to say that the chances that you can get it up on any given day is virtually non-existant.

      You can keep your denials to yourself because they contradict people's experience

      Another way to put that is that they contradict your baseless claims and idiotic extrapolations.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    2. Re:Well Known Facts and Obvious Conclusion. by Anonymous Coward · · Score: 0

      Hahaha, poor twitter, he can't catch a break

  115. Teletubbies? Re:uh ho by Anonymous Coward · · Score: 0

    How old are you, sir?

  116. Re:Turns out the whole reason for the attack was.. by xenocide2 · · Score: 2, Interesting

    And up until last week the most frequent answer on the Ubuntu forums for many questions was "use Automatix". Possibly because web forum software is horrible on all fronts. It caters to a narrow, dangerous audience of experienced people who should know better. People who's been using the internet for long enough to know what a "web forum" is, but aren't familiar with mailing lists and IRC. So the forums were never planned for, but it eventually it was felt that the forums should be intergrated rather than continue to grow and divide the community.

    Automatix in particular is a fantastic story of why I avoid forums. Automatix began life as a bash script under a different title by someone other than "arnieboy", and shared by a sticky forum thread. A marginal step up from guides telling you what commands to run to enable various things, etc. Based on a fundamental misunderstanding of copyright, licensing and the GPL, Automatix was born as a fork of this script, featuring numerous dubious personalizations that might be okay for arnieboy to accept but aren't good suggestions (such as enabling a root account). The forum admins have regularly played an active role, playing favorites amongst the various tools. Automatix at one point had it's own 3rd party project sub forum, where apparently traditional Ubuntu Code of Conduct did not apply ("his forum, his rules"). Eventually automatix was blamed for the failed upgrade of a number of users, and some people took to abusing a "popular searches" front page widget to advertise the phrase "automatix sucks", which was eventually fixed by telling the software that "automatix" was too common a word to search for, I think at the author's request.

    As things stand now, Automatix has it's own forum and remains mostly antagonistic towards criticism. It's functionality has been largely dupplicated though it still serves a purpose, to commit copyright infringement via w32codecs etc. Ubuntu has tools that function very similar to Automatix' normal behavior, and in some cases improve upon it. The codec detection stuff in totem is helpful, as you don't need to know about Automatix to learn how to make things work, though it doesn't install w32codecs. And the most significant, repeated complaint has not been solved: Automatix has scheduled for themselves a single week with which to test all bugs and upgrade flaws -- they plan to release one week before gutsy is published.

    A number of forum posts relating to this history have gone missing, which I disagree with. The proper thing to do in the face of misconduct is confront it and denounce it, not hide it by deletion. You might have the right to be offended by what people say, but not the right to erase history. Instead of the forums, use mailing lists and IRC when you feel like being sociable with other linux users, and launchpad's bugs and answers services if you have a problem.
    --
    I Browse at +4 Flamebait

    Open Source Sysadmin

  117. Re:Turns out the whole reason for the attack was.. by bealzabobs_youruncle · · Score: 1

    Interesting details xeno, that fills in the historical gaps I missed when I left Ubuntu in early 2006, mostly due to the board riots. I could not agree more with your assessment of the board mods, disagreeing is one thing, deleting valid portions of topics is out of line.

  118. Re:This is a FAILURE of the OPEN SOURCE Community by I'm+Don+Giovanni · · Score: 1

    LOL
    The fact is, 99% of those that talk of a million eyes constantly pouring over OSS code haven't looked at even one line of code (of projects they don't directly contribute to) themselves. The million eyes thing is a myth. I guarantee you that 90% of slashdotters haven't looked at linux code any more than they have windows code.

    --
    -- "I never gave these stories much credence." - HAL 9000
  119. Re:Following the M$ example. Re:BWAHAHAHA... by Bandman · · Score: 1

    Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)

    -Linus Torvalds

  120. Re:Following the M$ example. Re:BWAHAHAHA... by AndyCR · · Score: 1

    I would do that, too, if I weren't so afraid of others seeing how ugly my working copy is...

    --
    If there's anyone I hate more than stupid people, it's intellectuals.
  121. 2000 called by Anonymous Coward · · Score: 0

    They want their joke back.

  122. Re:Following the M$ example. Re:BWAHAHAHA... by jwo7777777 · · Score: 1

    wrong Armstrong....

  123. Re:Yes -GETTING THE LAST LAUGH!, as per usual... a by Anonymous Coward · · Score: 0

    "OH I'M SO FUCKING PROUD! It's good to know your list of "evaders" is so easily expanded" - by Anonymous Coward on Wednesday August 15, @10:18PM (#20244641)

    I see you believe in strengthening your 'personal qualities', such as your mastery of eloquent speech. "Practice makes perfect"... note the profanity, yet again!

    "Says who? I'm glad to see I've become another phantom enemy vanquished in your feeble little mind." - by Anonymous Coward on Wednesday August 15, @10:18PM (#20244641)

    Ok, I suppose that your use of profanity every other word, indicates your mind is mighty? And, like I believe I stated in this exchange with you?? I can post the URL's of those, easily as evidence to the contrary... would you like those to examine???

    I wouldn't call it "vanquishing" anyone - more of an example of *NIX folks that like to say this, here @ /.:

    "(Insert *NIX variant here) is more secure or more securable than Windows"

    Type stuff, running when it comes time to 'back up their bluster' & put their monies where their mouth is, & taking a multiplatform test of security that tests analogs present in both systems (such as access control to configuration &/or state keeping files) types, *NIX vs. Windows NT-based ones.

    "It gives me a real sense of accomplishment, you know? Like if I had posting long-winded rambling bullshit about some website and gloated about how many people I've imaginary-defeated with my longwinded anonymous score:0 posts that nobody sees." - by Anonymous Coward on Wednesday August 15, @10:18PM (#20244641)

    Nobody sees? It's funny, I have one that is ongoing here with a fellow that is easily 50++-60++ or more replies now, on this very subject... here @ /. no less.

    His name's SanityInAnarchy, & I am overcoming every one of his objections in fact, as to his trying this test, & he's giving in on MOST of his "objections" already @ this point.

    Only 1-2 more to go in fact... & I'll overcome them as well, as I have his others.

    How can this be "imagination", if I post MANY examples anyone can check on, on that note!

    Such as SanityInAnarchy's exchange with myself, + others where I had to overcome various objections folks that use *NIX here had, & still, they in those kept evading posting a result on this multiplatform test of security in CIS TOOL (which has been noted by BOTH computerworld AND SANS, as to its purpose, validity, & usage)??

    Just ask - I can post those, if you like, as I stated before... I have most of all of the URL's on that note, bookmarked/fav'd here.

    "I feel so special. Please respond again and tell me how badly I lost! It's fuckin' HILARIOUS!" - by Anonymous Coward on Wednesday August 15, @10:18PM (#20244641)

    Well, now that you're done with your "f'ing rant" lol (you ARE done now, right?)... Well, why don't you download CIS TOOL, & see how your *NIX setup does on it?

    APK

    P.S.=> You MAY not like the result though, so, go easy on yourself on your *NIX rig... so you don't "blow a gasket" or something, because I strongly suspect your score on your *NIX rig will be substantially lower than mine is on the multiplatform test of security known as CIS TOOL... lol! apk

  124. Canonical was NOT hosting these servers. by angrykeyboarder · · Score: 1

    I don't see how they are to blame.

    --
    Scott

    ©20014 angrykeyboarder & Elmer Fudd. All Wights Wesewved
  125. Re:Turns out the whole reason for the attack was.. by xenocide2 · · Score: 1

    Frankley, I've never bothered paying attention to the boards, rightly recognizing them as instant newb magnets that are unfortunately a waste of my time. But the Automatix stuff prompted me to read more about this, and investigate. What I found was a string of quoted posts deleted, and plenty of bad grammar from developers telling people to take their criticism and shove it. Simply put, Automatix is software written by Poisonous People.

    --
    I Browse at +4 Flamebait

    Open Source Sysadmin