Slashdot Mirror


Novell OpenSUSE Server Hacked

abelikoff writes "Both LinuxWorld Australia and SuSE Linux Forums report that OpenSUSE website got hacked last night." This story was submitted quite a number of times.

29 of 329 comments (clear)

  1. *sigh* by the-amazing-blob · · Score: 5, Insightful

    I still will never understand why people do stupid things like hack websites.

    1. Re:*sigh* by jupiter909 · · Score: 5, Insightful

      Hacking websites is not stupid. It's proof of concept. It is often good when people hack/crack things, it forces for tighter control and security. If not for people hacking and cracking things we would not have things such as online shopping and ssh encrpytion etc. It is all part of a never ended life cycle. More often than not it is poor management/admin than the software/systems themselves. Human error.

    2. Re:*sigh* by the-amazing-blob · · Score: 4, Insightful

      But if nobody hacked anything, there wouldn't be a need for better security.

      I'm too idealist for my own good.

  2. ouch by Anonymous Coward · · Score: 5, Funny


    They could just run OpenBSD.

  3. How does this help ? by Anonymous Coward · · Score: 4, Insightful

    How does hacking this website help to put your voice ? Other than geeks, how many people check that website. If they had hacked CNN or BBC, it would have been noticed significantly. Soon this would go into oblivion. Makes me wonder what has nuclear progam to do with open source linux ?

  4. Rights or not by michaelzhao · · Score: 4, Funny

    The Iranian hackers should first learn English. I was banging my head on the table reading that grammatically incorrect junk.

    1. Re:Rights or not by meadandale · · Score: 5, Funny
      "All your uranium are belong to us!"

      Step away from the fissionable material...It is obviously causing you brain damage.

    2. Re:Rights or not by Otter · · Score: 4, Interesting
      Often, that's a good comeback, but this time...the crackers' message is in English. michaelzhao's response is in English. Where does Arabic come into the equation?

      Especially since Iranians a) speak Farsi, not Arabic, and b) aren't Arabs.

    3. Re:Rights or not by klykken · · Score: 5, Insightful

      You might have confused the Arabic language with the Persian language (Farsi). They share the same alphabet but are entirely different.

      --
      Looks like a fish, drives like a fish, steers like a cow.
  5. Re:Don't blame LINUX by grub · · Score: 5, Insightful


    Linux is near-flawless in terms of security.

    You don't follow security mailing lists, do you? Most Linux distros have decent security but "near-flawless"?

    --
    Trolling is a art,
  6. I'm convinced! by Necrotica · · Score: 4, Funny

    The US and EU better let Iran develop a nuclear energy program or these senseless acts of web terrorism will never stop!

  7. Details of the hack? by Trigulus · · Score: 5, Interesting

    Was this a targeted attack? Did they just fall victim to a script? Unpatched vulnerability? Weak password? what? Im just asking cause none of the links provided answer this.

    --
    If something exists that does not need a creator (god) then why must the cosmos need one?
  8. ssh scan by perp · · Score: 4, Informative
    This server probably had a weak root password and was hacked by one of the several automated ssh bruteforcers out there http://www.linux.com/article.pl?sid=05/09/15/16552 34

    I see these attacks all the time on all Internet facing servers.

    --
    There are two kinds of sysadmins: paranoids and losers. I'm both kinds.
    1. Re:ssh scan by jaclu · · Score: 4, Informative

      I have a hard time to see the gain in security by disalowing root but allowing users to login and then sudo.

      In the case of three admins, you would end up with three accounts that could be exploited, rather increasing if anything the risk of direct ssh exploits.

      Once the bad guy is in, he has all the local exploit possibilities to gain root, so your already in trouble if they get in.

      So as long as you do ssh with passwords, disalowing root-login dosent really buy you any security, but it hassels the admins each and every day.

      On the other hand, prefered method would be to login with keys and disallow passwords completely whenever possible.

    2. Re:ssh scan by Gogo0 · · Score: 4, Informative

      Part of the security comes from non-root logins being unknown.

      One could try to use a non-root user to bruteforce their way into my system, but they'll either get one (probably created by an application) with /dev/null as a shell or they will be trying usernames that dont exist.

    3. Re:ssh scan by despisethesun · · Score: 5, Informative

      I have a hard time to see the gain in security by disalowing root but allowing users to login and then sudo.

      You must not have much experience with sudo. One of the benefits of it is that it allows you to give root permission to people for specific tasks that they would need that access level for. While there are certainly a lot of people who set their sudoers file to "allow all" for everyone, if sudo is properly implemented no one should be able to do anything they don't NEED to do as root. Sudo also has the benefit of keeping track of what users used it to do what tasks, making it easier to trace the path an attack came from.

      Gogo0 also mentioned an added benefit to this scheme so I'm not going to repeat it here.

      --
      This poo is cold.
  9. different hacks, different times by sjvn · · Score: 4, Informative

    The LinuxWorld Australia story is actually about an earlier break-in of a Novell system that was being used for World of Warcraft related stuff, not the OpenSUSE site at all.

    Steven

  10. Re:Don't blame LINUX by dasunt · · Score: 5, Funny
    People always try to blame the software right away but usually it's poor administration.

    Isn't this the same flaw Windows has?

  11. OpenSUSE website Hacked? No. by blanks · · Score: 5, Informative

    The open SuSE website wasnt hacked, it was a damn gamming machine they had on their network.

    From TFA:

    "The employees that set it up apparently had no idea of security," Brandon said. "But what is really surprising is that Novell would allow employees to set up game servers on their corporate network and then allow the public to access it."

    "There was no major breach of security here," Barney said. "Needless to say, we are taking the appropriate steps" to address the situation.

  12. Hey, by Create+an+Account · · Score: 5, Funny

    Your logic and reason are not welcome here.

  13. Re:Oh sweet sweet irony... by ArsenneLupin · · Score: 4, Funny
    If a site running Windows Server 2003 was hacked, would it make the front page of /.?

    No, it wouldn't. People would get pissed about having to dig through 100000 stories of "Yet another cheesy Windows server hacked" until they found a real story.

  14. Re:Linux Secure By Design? by scronline · · Score: 5, Interesting

    Speaking from personal experience, 85% of all hacks come from poor administration. ie. not patching flaws, weak passwords, poor security measure such as file permissions and lack of firewalls. The remaining 15% come from a mixture of things, and like it or not, 14.999% of that is Windows. Security through obscurity doesn't work when you have thousands of people pounding at your code just trying to find a way in.

    All these Worms on the net is a perfect example. And when you get down to it, even some of the poor administration is Microsoft's fault for making it "so easy you don't need an experienced technician...." When in fact they bury stuff so deep unless you know where it is, the necessary changes don't get made leaving everything as default.

    I can't even begin to count how many times I've gone to a customer's location where they had an employee that was a self proclaimed geek that did all the setup and everything was not only wrong, it opened gaping holes on their network. Including things like having a USER logging in as Administrator on the server and using it as a workstation.

    Plus I won't go into all the people who hold an MCSE that never touched a computer until they went to a 2 week bootcamp on how to pass the tests.

    But, point in fact, any closed source application is subject to flaws that don't get patched because it's a small enough flaw that putting a programmer on it to fix it would cost more than keeping the flaw hidden.

  15. Maybe they were just tired of the poor performance by alhaz · · Score: 4, Funny

    The OpenSuSE server has been sucking wind for weeks, and i know for a fact that trouble tickets have been submitted about it within Novell.

    Maybe they were just trying to lend a hand with the administration . . . .

    --
    This is just like television, only you can see much further.
  16. Not Good for Iran by KidSock · · Score: 4, Insightful

    Dear Hackers,

    If you're going to hack websites, don't try to justify your idiotic hobby by turning it into a political posterboard. It has the opposite effect you're looking for. The thing that scares people most is unpredictable behavior. If Iran were calm, clear in stating there intentions, and followed all the diplomatic protocols with a smile there would be no way for anyone to stop them from builting reactors (wheather it be for processing fuel for weapons or not). But stupid stuff like this make Iranians look like evil subversives. Just look at the graphic they posted. It looks like the shadow of some kind of daemon with horns. This is not a good image for Iran.

    Or if it's a different group impersonating iranians, you're just losers.

  17. That IS the breach of security. by khasim · · Score: 5, Interesting

    Allowing "users" to setup their own box, on your network, outside your firewall, using your IP address IS a breach of security.

  18. Re:Practical upshot? Am I safe? by houghi · · Score: 4, Informative

    I'm running SuSe 9.3, and this morning, I let the automated update program do it's thing. Did I download and install any breached files?

    No. It was just the WiKi server that went down.

    --
    Don't fight for your country, if your country does not fight for you.
  19. Re:Don't blame LINUX by ScrewMaster · · Score: 4, Insightful

    The problem comes in when you are, yourself, an OS vendor. It's really hard (from a marketing/PR perspective) to have your site run a BSD when you happen to sell a major Linux distro. Or have a major online service you bought run Solaris when you happen to make Windows, for that matter. Customers (and potential customers) will rightfully wonder why you don't have confidence in your own product.

    --
    The higher the technology, the sharper that two-edged sword.
  20. The public image of the open source community. by CyricZ · · Score: 4, Interesting

    I think it is time for the open source community, as a whole, to better consider its public image. Incidents like this, involving one of the premiere Linux vendors, do unfortunately tarnish the image of our community quite badly. And then you have rogue open source developers publically insulting users. Such incidents make people remember open source software for all the wrong reasons.

    Now, perhaps this is just a case of amateurs being allowed to join a community that mainly consisted of academics and professionals. The high standards that the open source community once enjoyed are being degraded on a daily basis by developers who cannot write secure code (ie. many PHP developers), by developers who blatantly insult and ridicule their users (ie. the KOffice example earlier in this post), or companies that provide insecure, open source-based products.

    Is there much that can be done about this? I'm not sure.

    --
    Cyric Zndovzny at your service.
  21. Re:As you can see by LnxAddct · · Score: 5, Insightful

    It's a little worse than that. The IHS guys aren't just script kiddies, their lead guy's blog is here. He is apparently very active in writing exploits and gives code to all of them. He was just accepted into a university, but worse, one of his blog entries is about how he likes slackware and is trying to write some code to help the project out. Now I don't know about you, but I find that suspicious as hell. Unless someone goes over every line of code submitted with a magnifying glass than it can be fairly easy to sneak in a little area for a buffer overflow or something. (Preventive measures like SELinux and exec-shield are necessary and even they don't fully solve the problem). I can only hope that the slackware community does decent background checks on submitters, and also good code checking. The last thing we need is for Open Source to start being purposely made vulnerable and attacked from within.
    Regards,
    Steve