Slashdot Mirror


Cisco IOS Source Code Theft Story Continues

securitas writes "eWEEK's Steven J. Vaughan-Nichols reports that the source code for Cisco's 'main networking device operating system was stolen on Thursday' (May 13) according to the Russian company SecurityLab. SecurityLab says that criminals broke into Cisco's network and stole 800MB of source code for IOS 12.3 and IOS 12.3t, a pre-release variant. The purported culprit(s) then bragged about the feat in an IRC session and offered 2.5 MB of the code as proof. Industry analysts Dell'Oro Group says that 'Cisco owns 62 percent of the core router market.' More at the Sydney Morning Herald and Windows Network magazine." Our original coverage was here of this story.

318 comments

  1. the end is near.... by Anonymous Coward · · Score: 0

    ...just a few more days and all that modern geeky internet goes to hell. Thank u cisco and "franz" !
    omfg ;)

    1. Re:the end is near.... by Anonymous Coward · · Score: 1, Insightful
      Relax. It has been trivial finding openings without the source code. There have been plenty of known openings against cisco over the years. The only reason why they do not have a bad record is that they
      1. have a good design
      2. hire decent coders
      3. have a good qc
      . Otherwise, they would already have a track record similar to MS.
  2. Can you imagine... by Anonymous Coward · · Score: 5, Insightful

    ...if the entire internet was taken down? for an extended period of time? The world would fall into disarray. Although once upon a time the world functioned perfectly well without the internet. Amazing how technology makes us dependent just like junkies.

    1. Re:Can you imagine... by fbrain · · Score: 2, Redundant

      Even better, If a start exploded far away enough not to kill us and all devices that depended on anything magnetic broke down. BTW - I could be wrong about the science side of this... (Perhaps thats what the world needs?)

      --
      Avontech | Play dirty! They started it!
    2. Re:Can you imagine... by skasingularity · · Score: 5, Funny
      Sure there would be problems, but I think most people would opt for watching TV or going outside. Some businesses would stall, and slashdot users would probably try and hang themselves with their mice, but I think a relatively large part of the world would continue to operate.

      Just because you rely on the internet, doesn't mean the entire world does too.

    3. Re:Can you imagine... by iapetus · · Score: 5, Funny

      Personally I take offence at your narrow typecasting of Slashdot users.

      Some of us use wireless mice, and would have to resort to hanging ourselves with VGA cables.

      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    4. Re:Can you imagine... by Segway+Ninja · · Score: 4, Insightful

      But it would be fair to say that most businesses do rely on the internet, in some way or form. At least, they do in New Zealand. E-Mail would have to be a main source of internal communications (eg, within the company - but not the same building, as within the building would probably function without the net) - definately for technical resources on products and the like.

    5. Re:Can you imagine... by skasingularity · · Score: 1

      I figured that the only people with the strength to tie a noose would be the ones who had to drag a moused cable around. I suppose those of you who use battery powered mice could do it as well.

    6. Re:Can you imagine... by skasingularity · · Score: 1
      Well, while its true that everyone probably uses e-mail, but everyone probably has easy access to a phone as well.

      A lot of the time, many people forget that there are ways of communicating OTHER than the internet, but I think that if push came to shove, internet users could deal without.

    7. Re:Can you imagine... by tymbow · · Score: 3, Insightful

      A friend of mine used to regularly say that only IT and the illicit drug trade call people "users".

    8. Re:Can you imagine... by B'Trey · · Score: 4, Insightful

      Sure there would be problems, but I think most people would opt for watching TV or going outside.

      It isn't the Internet as an entertainment tool that's the issue. It's the Internet as a business tool. In some situations, there are alternatives - a phone call instead of an email, a printed report instead of one transmitted electronically. But there are a great many systems which have been converted to the Internet for which the old infrastructure either no longer exists or would be extremely difficult to reactivate. Inventory systems, ordering systems, tracking systems, etc.

      I'm in the US Military. Message traffic used to be transmitted via radio to teletypes. Now, it all rides on the Internet. The teletypes are long gone. Lack of an Internet wouldn't bring us to our knees - we have contingency plans. But it would seriously impact our operations.

      Just because you rely on the internet, doesn't mean the entire world does too.

      The world DOES rely on the Internet, whether you're aware of it or not. We would survive, just as we survive hurricanes and black outs and other disasters. But any significant disruption of the Internet certainly would be classified as a disaster and have significant impact.

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    9. Re:Can you imagine... by The+Evil+Couch · · Score: 1
      slashdot users would probably try and hang themselves with their mice

      I use a trackball, you insensitive clod!

    10. Re:Can you imagine... by 1u3hr · · Score: 2, Insightful
      A lot of the time, many people forget that there are ways of communicating OTHER than the internet, but I think that if push came to shove, internet users could deal without.

      Most companies still have a few fax machines, not to mention many printer/scanners that can be made to act like one. So we'd just go back to fax, phone, snail mail. Actually, unless you're Amazon or a similar web-centric company, most would find they were more productive for not pissing away time reading Slashdot, porn, sending chain mail and jokes, deleting spam.

    11. Re:Can you imagine... by banzai51 · · Score: 5, Funny

      I have stolen the entire source code for Lunix. I'm gong to distribute it and see how long before EVERY linux server is down.

    12. Re:Can you imagine... by ajs · · Score: 1

      Most important business functions rely on private lines which are not directly connected to the Internet.

      For the most part, the Internet is a luxury at this point, and I can't think of a single critical service that relies on it.

    13. Re:Can you imagine... by Khazunga · · Score: 1

      Just throw it real high, and close your eyes...

      --
      If at first you don't succeed, skydiving is not for you
    14. Re:Can you imagine... by sploo22 · · Score: 0

      You insensitive clod! I'm using a laptop!

      --
      Karma: Segmentation fault (tried to dereference a null post)
    15. Re:Can you imagine... by Depili · · Score: 1, Funny

      What about us laptop users with wireless networks, finding suitable cables to hang oneself from is hard nowadays.

    16. Re:Can you imagine... by Nuclear+Elephant · · Score: 1

      Looks like pretty clean code, a nice change from when Microsoft's source code was stolen.

      Isn't this a good thing, according to open source enthusiasts? Sure we'll lose a few thousand networks during the first couple of exploits, but we'll end up with much more stable code in the end. If these guys can hack Cisco's network, they don't need IOS's source code to hack everybody else's.

    17. Re:Can you imagine... by ThomaMelas · · Score: 1

      Power cord.

    18. Re:Can you imagine... by mustangsal66 · · Score: 1

      Yeah like the time a few years back when some idiot announced the route 0.0.0.0 0.0.0.0 via BGP ('97 or '98)...

      Or the MD tunnel fire that took down a nice chuck of the east coast for a day or so...

      --
      Why worry? Each of us is wearing an unlicensed "nucular" accelerator on his back.
      Sig changed for readability by G.W.
    19. Re:Can you imagine... by Suidae · · Score: 1

      Except many companies (including mine) have phone systems based on frame relay systems, which might be effected.

    20. Re:Can you imagine... by CoolVibe · · Score: 1
      Ha! My computers are powered by Tesla's wireless power transfer :)

      (just kidding, although hugging a tesla coil while earthing yourself would do the job just nicely)

    21. Re:Can you imagine... by 98jonesd · · Score: 0

      I use a laptop you insensitve clod!

      I'll go back under my bridge now....

    22. Re:Can you imagine... by drinkypoo · · Score: 1

      Let us not forget that many of us weigh entirely too much to be hung with the cable of anything less than a mainframe mouse. (I wanted to include pics of the mainframe mouse here but I can't seem to find any! What is the internet coming to?)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    23. Re:Can you imagine... by shachart · · Score: 1

      I have a wireless mouse, you insensitive clod!

      --
      Those who can, do. Those who can't, consult.
    24. Re:Can you imagine... by nightsweat · · Score: 1

      You're joking, right? Look at the VPN market and you'll see how many businesses rely on the internet to get communication back and forth to their offices. The headquarters accounting system might not go down, but the branches won't be able to query or update the system in real time.

      --

      the major advances in civilization are processes which all but wreck the societies in which they occur - A.N. White
    25. Re:Can you imagine... by morleron · · Score: 1

      You make an interesting point in a roundabout way. Why is it that whenever proprietary code is stolen the "security commentators" start predicting the end of the world? As you note, Linux code is available to anyone and there have been very few, if any, exploits that have brought down significant numbers of machines. Unless one postulates that F/OSS software is orders of magnitude better than proprietary code I don't see any automatic connection between stolen source code and security problems.

      I do think that it would be interesting, as an intellectual exercise, to perform a security audit of the Cisco IOS code. This would give us a baseline from which to begin an analysis of the quality of F/OSS versus proprietary software. Until we can get such an accounting of the problems with both F/OSS and closed source software the arguments over which is better will continue to be based on religion and not fact. Unfortunately, given the DMCA and other legal restrictions I suspect that anyone who openly makes such an analysis would be liable for fines and possible jail time.

      Given some of the things that have been in the news lately regarding IOS exploits I won't be surprised if we see some major attacks, but I don't think that's an automatic result of the theft. Let's hope that Cisco will be willing to allow the code to be audited as that will help out everybody in the long run.

      Just my $.02,
      Ron

      --
      Impeach Barack Obama for violating the Constitutional requirement to be a "natural born" citizen to hold the office of P
    26. Re:Can you imagine... by u-235-sentinel · · Score: 1

      I'm curious how quickly exploits will become available this being the case. It would be a good demonstration of why Open Source is a better development model than closed source.

      The unexpected release of the Win2k code was a good example of this. While only 15% was released, within 3 days we had a couple of exploits published on the internet. As Bill Gates put it, if the Windows code was released, we would have a serious national security threat to our country.

      Even he realizes it would be a serious problem.

      --
      Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
    27. Re:Can you imagine... by Anonymous Coward · · Score: 0

      oh, dont worry, I'll just haxx0r your lunix machine with my linux machine via DDoS

    28. Re:Can you imagine... by Anonymous Coward · · Score: 0
      Message traffic used to be transmitted via radio to teletypes. Now, it all rides on the Internet.

      I call "bullshit." Do you really expect us to believe that the military is dependant on the Internet for operations? I don't think much sensitive data is sent over the Internet (VPN or no) and I'm certain they have alternative ways to communicate that don't rely on the Internet.

    29. Re:Can you imagine... by JAgostoni · · Score: 1

      Then club yourself to death with your laptop and your giant Tesla coil.

    30. Re:Can you imagine... by DAldredge · · Score: 1

      So that multibillion dollar sat net and the seperate net that MCI has been building for DoD down exist anymore? What did you do, sell them on ebay?

    31. Re:Can you imagine... by Anonymous Coward · · Score: 0

      Yes, but they would not be watching TV, as Cable Companies rely on Cisco technology also, your cable boxes are two way IP devices on a network, there's probably some sort of Cisco appliance in there somewhere, and most likely, it's connected to a VPN for vendor support. Cisco also made Stat Mux's for a while, and there are cable companies still using them.

      Same goes for broadcast TV, if their equipment stops talking (commercial inserters, etc), you're SOL as far as watching TV.

    32. Re:Can you imagine... by Nonesuch · · Score: 1
      Sure there would be problems, but I think most people would opt for watching TV or going outside.
      Do you realize how much the TV networks rely on the Internet?

      Actually, most of the content (syndicated shows, etc.) is distributed using satellite feeds and some "Internet Protocol" connections over private peering, so that would not be disrupted immediately.

      OTOH, quite a bit of the newsgathering, commercials, and general business operations are handled using the public Internet as a transport, and if these fail, the stations might still stay on the air, but all they'd be able to afford to broadcast would be a bunch of talking heads whining about how the Internet is down.

    33. Re:Can you imagine... by infochuck · · Score: 3, Funny

      ...I think most people would opt for watching TV or going outside.

      Outside? What's the URL for that?

    34. Re:Can you imagine... by B'Trey · · Score: 1

      Are you referring to EDS and the NMCI (Navy Marine Corp Internet)? What do you suppose those backbones are made up of? Don't you suppose that a worm feeding off a new Cisco exploit that is capable of taking down the Internet would be capable of taking down that network too? Certainly, it's firewalled off from the main Internet backbone but how many of those firewalls are Cisco do you suppose?

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    35. Re:Can you imagine... by Anonymous Coward · · Score: 0

      True it would mean bad news for a lot of businesses. But those businesses that still know how to get business done the old way, through pre-internet channels would have an opportunity to shine. It would be nice to have an expert chime in on exactly how the modern world would cope with an extended internet outage. Certainly there are think tanks out there paid to wring their hands over this subject. If it hasn't already been, this would make a good Ask Slashdot topic.

    36. Re:Can you imagine... by HiThere · · Score: 1

      There's a difference. Linux & Unix were developed with the code out and available. Every time someone spotted a hole, it got patched. And lots of college kids were breaking into it regularlly at first (usually to get free account time). Closed source programs have never had that fire hardening. So Linux & Unix got their proof tests done while they were small and unimportant. (So what if a bunch of students got to play rogue for free. Computer time, even then, was *relatively* cheap.) But MSWindows, e.g., has never been though that process...until now. They've tried, probably tried quite hard, to fix the bugs, but programmers will never think of all the ways that a user can abuse the system.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    37. Re:Can you imagine... by DAldredge · · Score: 1

      Since the official military policy is that all mission critical systems/networks have to be on networks that have no connection the the internet I don't see how that could happen if all the rules and regs are being followed. If the regs aren't being followed arrest people and don't stop the arrests till they are followed.

    38. Re:Can you imagine... by ajs · · Score: 1

      Look at the VPN market and you'll see how many businesses rely on the internet

      I've yet to see one business that relied on the Internet for anything critical. Sure, we have VPNs all over the place and most companies do, but when push comes to shove, those are all for convinience (and home users, and folks connecting laptops from hotels, etc.), and the business could run pretty much forever without them, though with some degredation.

      Anything else would be irresponsible.

    39. Re:Can you imagine... by nightsweat · · Score: 1

      I think you'd be very surprised to look at the market for frame relay and point-to-point versus using VPN's to connect offices. Professional service firms, which tend to have many under 50 people offices that open and close in two or threee years often use VPN's exclusively.

      --

      the major advances in civilization are processes which all but wreck the societies in which they occur - A.N. White
    40. Re:Can you imagine... by B'Trey · · Score: 1

      On a ship at sea, NIPR rides as a VPN on SIPR. How does the NIPR traffic get to the Internet if there's absolutely no connection?

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    41. Re:Can you imagine... by DAldredge · · Score: 1

      Can the ship function in its combat role without access to those systems?

    42. Re:Can you imagine... by B'Trey · · Score: 1

      Certainly it can. I specifically said that the military has contingency plans. Loss of the Internet would affect routine, day-to-day operations. It wouldn't affect our fighting ability. "Military intelligence" is indeed an oxymoron at times but we aren't that stupid.

      I used the example of switching from teletypes to packet networks as an example of changing infrastructure because I helped implement the change (when I joined the Navy in 1985, we still had teletypes.) and it sprang immediately to mind. I didn't mean to imply that loss of the Internet would bring the military to its knees.

      There is usually an air gap between SIPR and NIPR, and SIPR is much more important to tactical operations than NIPR. However, there are points where NIPR and SIPR touch. And of course there's the human element. We've been bitten by worms and viruses on SIPR before. There's a real possibility that a rapidly spreading worm preying on an unknown Cisco vulnerability would take down both the public Internet, the military's NIPRnet and manage to jump to SIPRnet.

      (For lurkers, SIPR is either Secret or Secure Internet Protocol Routed, while NIPR is Non-secure... SIPR is a classified, world-wide intranet. NIPR is a non-classified intranet that connects with the public Internet. The term NIPR is often used to include the Internet as well as the military's private backbone.)

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    43. Re:Can you imagine... by Anonymous Coward · · Score: 0

      A friend of mine works heavily in both.

    44. Re:Can you imagine... by Anonymous Coward · · Score: 0

      There's a difference.

      There's a bigger difference. IOS runs on 60% of the core routers of the Internet. Linux runs on maybe 6% of the end nodes. If you're going to hack someone, you're going to pick on the big, shiny, famous target and make a big splash in the news, not just annoy a few geeks for a while.

    45. Re:Can you imagine... by martixer · · Score: 1

      Well, fortunately (or perhaps, the scary thing is) that you probably cannot 'shut down' the internet. First of all, if Cisco owns 60% of the market, that means 40% is not Cisco. Also, in the core, it is unlikely that 12.3 is used but a stable or GD train (though I'm not saying that those releases are free of bugs and vuln's, and with common code, 12.3 code will probably give some clues of those ;-) ). The point I'm making is that the (auto) routing mechanisms, intelligence, all (inter)connected devices, backup scenarios etc are probably the closest thing to artificial intelligence that currently exists. Though crippled, and perhaps (if even) with severy diminished capacity (let's say for argument's sake, 40% at worst?), the core with continue to function. (impact will most likely occur at the edges, specifically with devices administrated by half-ass nitwits who don't know what they're doing and running "cutting edge" releases and such). Companies running mission critical connectivity over public (cheaper) accessible and "exposed" infrastructure should probably have some vital limbs chopped off in public on the town's market square anyways. (although I appreciate that for some this is their very livelyhood and core business. (For most, it's probably an additional feature/service to customers). "(Artificial) Life will find a way"

    46. Re:Can you imagine... by ThaReetLad · · Score: 1

      You could alway try to beat yourself to death with a wireless mouse.

      --
      You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
    47. Re:Can you imagine... by ajs · · Score: 1

      Professional service firms, which tend to have many under 50 people offices that open and close in two or threee years often use VPN's exclusively

      This conversation started around the critical services that people rely on, and how a wide-scale Internet outage would result in disaster to modern life. I don't think having "professional service firms [...] that open and close in two or three years" go away for multiple hours or a day is going to cause that level of havoc for the world.

      Let's try to stay on topic.

    48. Re:Can you imagine... by nightsweat · · Score: 1

      Sparky, this is on topic.

      The offices open and close but the firms go on. Client-specific offices are a huge part of the new service economy. Those firms employ people who live and spend in the area which affects local businesses ad other firms. If those firms can't service their clients, they go away and that hurts everyone.

      --

      the major advances in civilization are processes which all but wreck the societies in which they occur - A.N. White
    49. Re:Can you imagine... by kulack · · Score: 1
      a phone call instead of an email

      Yeah, but ya know. I can't even find the phone numbers of people I work with without being online to the company intranet and this would probably hit there too. Suddenly, 2^12 calls to the main lobby asking for phone numbers. Oh crap, that network just went down to.

      --

    50. Re:Can you imagine... by Anonymous Coward · · Score: 0

      I heard rumors that they're moving to Windows 2003 Embedded. So, nothing to worry about.

    51. Re:Can you imagine... by Anonymous Coward · · Score: 0

      If someone missed the link.
      Go to google and search for "ipv6_tcp.c -- IP version 6 support functions for TCP" and click on the first link where it says cached... Gotta love Google's cache.
      Also do a search for: "ipv6_discovery_test.c -- Neighbor Discovery unit tests" and do the same as stated above

  3. backdoor by sleepnmojo · · Score: 5, Funny

    They could have at least posted the code for the backdoor in all the routers.

    1. Re:backdoor by NickeB · · Score: 2, Funny

      Indeed, the world needs anything, it's more scriptkiddies...

    2. Re:backdoor by thpdg · · Score: 5, Funny

      Have you ever tried to configure any Cisco equipment? Even if you had the password, you'd give up in frustration after a few minutes. The only ones who can do it, are the ones who have a lot of experience with it. That's the real security of the plan!

      --

      -Patrick

      "They never stop thinking about new ways to harm our country and our people, and neither do we."

    3. Re:backdoor by Gsus411 · · Score: 4, Insightful

      Honestly, what is so difficult about configuring cisco routers? You just configure the passwords, interfaces, set up a routing protocol, set a gateway of last resort, and you're set. You can learn how to do all this in 30 minutes!

    4. Re:backdoor by Gsus411 · · Score: 1

      Errr.. and copy run start at the end to save your work.

    5. Re:backdoor by rjfan · · Score: 1, Insightful

      uhh.... You must not deal with routers much. Otherwise, you'd see other products such as Bay Networks/Nortel and sprinkle your words on your shoe for seasoning. A novice can have a Cisco router up and going in less than a minute. A decent guy can break into one in 3.

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

      You refer to basic setup...

      You ignore:

      Access-lists

      Frame-shaping

      IPSec

      Priority Queuing.

      BGP route summarization and reflection.

      just to name a few...

      You know nothing of how little you know!

      The wise man knows he is a fool, the fool does not know he is not wise...

    7. Re:backdoor by David+Horn · · Score: 1

      Who the hell cares if the code has been stolen? It just means that everyone's routers will crash every 3 hours, instead of only the Cisco ones...

      --
      PocketGamer.org - For the gamer on the go!
    8. Re:backdoor by k12linux · · Score: 1
      Do you think an attacker who wants to do a DoS cares about cisco configuration? They just want to find a flaw in the code that they can abuse and then write a program to exploit it. IOS config commands be damned.

      Not to mention that someone capable of hacking Cisco and of understanding the source code is sure as hell likely able to config IOS.

    9. Re:backdoor by whats_a_zip · · Score: 1

      I disagree. I know just enough to render a router inoperative. I've had 2 classes, not a lot of experience, and I'm quite dangerous. Now if you want me to make one of the darn things work... that's a whole different story.

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

      Although they are owned by the same company, its not like setting up a Linksys router.

    11. Re:backdoor by luke923 · · Score: 1

      Errr.. and copy run start at the end to save your work.

      That's too many keystrokes. Type "wr" and hit enter. SIMPLIFY, MAN!

      --
      "Good, Fast, Cheap: Pick any two" -- RFC 1925
  4. The internet seems faster today. by JPriest · · Score: 4, Funny

    I notice this morning that since the code leak the Internet has been faster, more stable, and I get packeted less often. Since the code leak I also lost 5 pounds and I swear my erectioin this morning was larger. *phone rings* That must be my bank calling to tell me they lowered my intrest rates.

    --
    Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
    1. Re:The internet seems faster today. by Anonymous Coward · · Score: 1, Funny

      I notice this morning that since the code leak the Internet has been faster, more stable, and I get packeted less often.

      Well of course it is. This is just a testament to the efficiency of open source software.

    2. Re:The internet seems faster today. by System.out.println() · · Score: 4, Funny

      And on top of all that, I just saved a bunch of money on my car insurance by switching to Geico!

    3. Re:The internet seems faster today. by gosand · · Score: 1, Funny
      *phone rings* That must be my bank calling to tell me they lowered my intrest rates.

      Nope, sorry, they are calling to tell you that your Mor@tgage hav baen d.e.nied

      --

      My beliefs do not require that you agree with them.

    4. Re:The internet seems faster today. by Anonymous Coward · · Score: 0

      I lowered my colesterol.

    5. Re:The internet seems faster today. by Anonymous Coward · · Score: 0

      I don't understand..... how is this trolling?

  5. Please remove code by fearlezz · · Score: 4, Funny

    Please, everybody! Please remove the source code from the internet ASAP before SCO sees it and claims ownership!!

    --
    .sig: No such file or directory
    1. Re:Please remove code by HeX314 · · Score: 0

      Dibs on copyright!!!

    2. Re:Please remove code by LizardKing · · Score: 1

      It's OK, the code will probably be covered by the BSDi settlement. After all, Cisco's software is descended from code written at Berkeley and then commercialised by ex-university staff.

      Chris

    3. Re:Please remove code by Anonymous Coward · · Score: 0

      I'll save you comment for historical reference.

  6. 800MB?? by Anonymous Coward · · Score: 0

    800MB of source code? for a router? WTF?

    1. Re:800MB?? by SmackCrackandPot · · Score: 5, Informative

      You've got a real-time operating system, a basic file-system, the TCP/IP and all the other protocol stacks, the SNMP/MIB support and proprietary routing algorithms. Presumably, the source code would be documented to some extent, along with SCCS archiving. All of this could easily add up to over 800 Megabytes.

    2. Re:800MB?? by Anonymous Coward · · Score: 0

      Still, how big is the Linux kernel? 50MB? How big is Win2K? Probably still smaller than this thing.

    3. Re:800MB?? by Anonymous Coward · · Score: 0

      Linux kernel supports about 20 processors architectures, 20-30 filesystems, lot of other protocols like Appletelk and IPX, beside TPC/IP.

      In addition it has tons of various drivers (sound cards, usb devices, framebuffer devices, etc..). Still, unpacked source cose is less than 200MB.

    4. Re:800MB?? by Anonymous Coward · · Score: 0

      Dumbass, we're talking source code here. Go back to school.

    5. Re:800MB?? by Anonymous Coward · · Score: 0

      The article does not say that the IOS source code was 800 MB. It says 800 MB of source code was stolen.

      Maybe they got the PIX, switch and VoIP source code as well.

    6. Re:800MB?? by Anonymous Coward · · Score: 0

      Windows source code runs in the 40+ gig according to Ballmer.

    7. Re:800MB?? by mwood · · Score: 1

      The Linux 2.6.0 source tarball is about 40MB.

    8. Re:800MB?? by CelloJake · · Score: 1

      Or maybe its big because they got several revisions.

      -Jacob

  7. Secure ? by cyberfunk2 · · Score: 5, Insightful

    Forgive my ignorance, but if the code is truly solid code, without buffer overruns and the like, shouldnt this theoretically not matter (just as the code for stuff like ipfw is open)?

    I realize however that Cisco code is likely more complex than the relatively simple stuff ipfw does.

    1. Re:Secure ? by flying_mushroom · · Score: 5, Insightful

      The problem is that, with 800 MB of code it's virtually impossible to be sure that there are no serious bugs somewhere.

      Sure, it might be more solid than Windows (!), but no large software project nowadays can presume to be bug-free. It's just too much code and possible scenarios to say that it all has been tested.

    2. Re:Secure ? by Anonymous Coward · · Score: 5, Interesting
      Forgive my ignorance, but if the code is truly solid code, without buffer overruns and the like, shouldnt this theoretically not matter (just as the code for stuff like ipfw is open)?
      I presume that by ipfw, you're speaking of the BSD IP firewall. In which case, yes, you're right, Cisco's IOS does a bit more in terms of advanced processing.

      Having had a look at some of the source code, I'm generally impressed. Cisco's code is solid. It's perhaps a bit more simplified than what you'll see in BSD's ipfw source, but simpler is better when you're talking about mission-critical applications. IOS is responsible for switching packets on a fair amount of heavy links; ipfw is responsible for switching packets at your average LAN.

      I don't think the IOS leak is going to lead to any new vulnerabilities. Cisco produces solid code. The only real interesting thing we may see is backdoor-style commands to IOS that the public is not aware of.

      --
      Free Naked Pics
    3. Re:Secure ? by Anonymous Coward · · Score: 2, Interesting

      "A previous major source code theft of parts of Microsoft's NT 4.0 and Windows 2000 has not led to any security violations."

      Uhh...wasnt there a serious problem in the code for parsing bitmap files discovered? wasnt there a virus that started spreading whenever a bitmap was viewed based on the exploit found?

    4. Re:Secure ? by xchino · · Score: 3, Interesting

      Sorry, but if this is true and the full source code has been released to the public, I can pretty much gurantee you there will be vulnerabilities found. The likleyhood that in the entire codebase, there exists not a single flaw is scientifically insignificant. We may not see any vulnerabilities the likes of "print 500 A's on login: " but you can bet there's something that will let someone do something they aren't supposed to. The chances of vulns coming from this are alot greater than the chances more vendor implemented backdoors are found, and that wouldn't suprise me in the least.

      --
      Everyone is entitled to their own opinion. It's just that yours is stupid.
    5. Re:Secure ? by gnu-generation-one · · Score: 4, Insightful

      "The problem is that, with 800 MB of code it's virtually impossible to be sure that there are no serious bugs somewhere."

      Well, let's say that cisco has allocated x people for code-auditing, and that they've had y years to do so (something like 15 and 15, probably?) And because their products need to be secure, they fixed anything those people found wrong.

      Surely that means that to find a vulnerability, any would-be cracker would have to spend at least as long on auditing as cisco did themselves unless they happen to be very lucky, or unless there are problems easily-visible in the source-code that cisco haven't fixed. So we wouldn't expect any exploit to be seen in the near future?

    6. Re:Secure ? by lewp · · Score: 0, Insightful

      Unless, of course, the thieves have a P-P-P-Powerbook at their disposal. Then we're all fucked.

      --
      Game... blouses.
    7. Re:Secure ? by CompWerks · · Score: 1
      Are you implying that just because the code was leaked that there will be vulnerabilities?

      Where does that leave the open source community?

      --
      If you can read this sig - the bitch fell off.
    8. Re:Secure ? by INeededALogin · · Score: 1

      Having had a look at some of the source code, I'm generally impressed.

      Did you come to this conclusion from looking at the 1996 header file?

      Cisco produces solid code.

      Maybe they do, maybe they don't. Looks like it gets its first real test. I am betting on no. In fact, I am betting on god awful code. Why? Because companies can get away with writing bad code when nobody is there to call them out on it.

      IOS is responsible for switching packets on a fair amount of heavy links; ipfw is responsible for switching packets at your average LAN.

      Come on now, that has got to be some sort of argument fallacy. People don't use it, so it must not be as good. Anyone who has ever dealt with Cisco routers is most likely aware at how downright annoying they can be. Nothing like finding a router that crashes every 20 minutes, or finding that everything goes to the shitter because of too large of a routing table.

      backdoor-style commands to IOS

      I disagree. An application like Cisco's ios should be one application that should be nearly free of this. One would not be able to open a port for a backdoor because it would be noticed. Any source control edits of the login code would surely be audited. It is a lot more likely that the new features would have a bug.

    9. Re:Secure ? by Anonymous Coward · · Score: 1, Interesting

      Here's my prediction of the effect that this will have on Cisco's sales, and on Cisco's share price. Zilch.

      I don't know anyone who's choice of Cisco products was predicated on the closed source nature of IOS. IOS will work the same as always, except that now Cisco might be motivated to go on a massive bug squashing expedition. They might also be compelled to close some back doors. I expect the next version of IOS to be better than ever.

      Which leads to the question: Why is IOS closed source in the first place?

    10. Re:Secure ? by The+Evil+Couch · · Score: 1
      the open source community has its source code open for review so that any flaws can be found and fixed, by the maximum number of people.

      cisco has a reputation of excellence, however, their code has not yet stood up to the scrutiny of tens of thousands of people, yet. the possibility of them finding *something* exploitable is very much there.

    11. Re:Secure ? by Anonymous Coward · · Score: 0

      should have use Mac OS9 (never ever hacked once)
      nor has mac os 8.x ever had an exploit on the internet in entire internet history.

      The reasons are many, despite millions of macintoshes in usage, including as servers for large secure networks including the us army.

      Cisco made a mistake using unix to secure their files.

      Cosult bugTraq (securityfocus) and search for mac os.

      i am *NOT* discussing unix based os x which has had over 80 exploits. I am talking about Mac OS9 and os 8.

    12. Re:Secure ? by banzai51 · · Score: 1

      That assumes that those tens of thousands are qualified to accurately review the code. I'm convinced they are by and large not.

    13. Re:Secure ? by su2ge · · Score: 1

      IOS is responsible for switching packets on a fair amount of heavy links; ipfw is responsible for switching packets at your average LAN.

      Come on now, that has got to be some sort of argument fallacy. People don't use it, so it must not be as good. Anyone who has ever dealt with Cisco routers is most likely aware at how downright annoying they can be. Nothing like finding a router that crashes every 20 minutes, or finding that everything goes to the shitter because of too large of a routing table.


      Now see, if you were actually doing everything the right way, you wouldn't have that problem. You either don't know what you're doing or do and are just ignorant. There is a solution to large routing tables, and it's called route summerization. The only thing that causes it to not work so well is using Variable Length Subnet Masks. If you are a stub network off of an ISP, your routing table should only really consist of one route anyway....... A default route saying that any network that is not yours goes out blah/blah interface or to blah.blah.blah.blah. I've been dealing with Cisco routers for about a year now and have not had a single problem with them aside from the occasional slip up on the user end(me). If your router is crashing every 20 minutes like you say it is, maybe you should try using one of the more stable IOS releases. Cisco does release solid code, but if you're using a release that isn't known to be stable in a production network, that's your fault. That's like trying to use yesterday's dev build and asking for it to work perfectly. It just doesn't happen.
    14. Re:Secure ? by SolidGold · · Score: 1

      I don't think this release makes much difference at all. There will be very few extra exploits as a result, and Cisco won't lose any money from it either as nobody will incorporate the code into their products anyway.

      --

      --SolidGold
      Everything you know is wrong. Or more accurately, inaccurate.

    15. Re:Secure ? by sckeener · · Score: 1

      I'm sure more eyes are going to be looking at this than 15 for 15 years.

      Heck, even decent people are probably going to look at it to see how to improve or tweak.

      --
      "Only one thing, is impossible for god: to find any sense in any copyright law on the planet." Mark Twain
    16. Re:Secure ? by Phleg · · Score: 2, Insightful

      You're assuming that code is static. New bugs are introduced with every release, and with every commit. Just because a group of Quality Assurance folks have been scanning the code for decades doesn't mean they'll catch the new bugs within a few hours.

      --
      No comment.
    17. Re:Secure ? by LnxAddct · · Score: 1

      Well I'm convinced that they are. I've spoken with quite a few devs, many are very intelligent academics, or get paid by corporations like IBM and RedHat to do such things. The great thing about open source is that you only work on a project if you know what you are doing and you enjoy what you are doing (implying you have a well founded understanding of what the project is trying to achieve). In companies, someone makes you code something and pays you whether or not you have any interest at all in what you are coding. In the OSS world everyone on the project has interest in it and its because of this that OSS succeeds so well. I'd rather have Linus check my code then Bill Gates. There is a reason people are switching and government agencies are realizing that its more secure. If you dont think IBM has audited many open source projects then your nuts, a corporation like IBM can't support something that it doesn't know is supportable, stable, and secure. Have you ever looked at the kernel code? Its damn nice.
      Regards,
      Steve

    18. Re:Secure ? by gosand · · Score: 4, Insightful
      Well, let's say that cisco has allocated x people for code-auditing, and that they've had y years to do so (something like 15 and 15, probably?) And because their products need to be secure, they fixed anything those people found wrong. Surely that means that to find a vulnerability, any would-be cracker would have to spend at least as long on auditing as cisco did themselves unless they happen to be very lucky, or unless there are problems easily-visible in the source-code that cisco haven't fixed. So we wouldn't expect any exploit to be seen in the near future?

      Except that Cisco has no real incentive to find bugs in their code, whereas a cracker does. Motivation makes a huge difference. And why would Cisco need to do strict audits on their code? Nobody outside the company will ever see it. Right?

      --

      My beliefs do not require that you agree with them.

    19. Re:Secure ? by The+Evil+Couch · · Score: 1
      even assuming you're 100% spot on, it only takes one code ninja genius to point out fatal flaws and get it fixed. so even if a majority of the OSS community is a bunch of bone-heads, the one that knows what he's doing is more than enough to make it worth doing.

      there's less assurance than that about salaried coders, simply because the company in question cannot logistically interview tens of thousands of applicants to fill just one position.

    20. Re:Secure ? by Anonymous Coward · · Score: 0

      uh, sorry.. but you're a fucking moron

    21. Re:Secure ? by MesiahTaz · · Score: 1

      Just because proportionally, a large number of people can examine the source code, and many of them are not qualified, does NOT mean that there will not be a significant enough number of qualified individuals. The whole point of free software is that the more people that have an opportunity to see code, the greater the chances of enhancements/fixes are.

      --
      Are you an open source warrior?
    22. Re:Secure ? by INeededALogin · · Score: 1

      if you were actually doing everything the right way, you wouldn't have that problem

      uh oh:-) No, I have watched some pretty experienced Cisco admins deal with some crazy stuff in companies that I have worked for.

      The routing thing dealt with routing tables received through bgp. The routing table grew to something like 60,000 routes which used up all the memory in the router. I would of expected a little more from Cisco gear in that scenario.

      Router crashing every 20 minutes... certain features cause certain problems. Memory leaks do occur. Booting up a Cisco router and giving it the simplest of configurations, it may stay up for 2000 days. Start throwing in VPN, NAT, VLANS, packet shaping, BGP routing updates... things get a lot more complicated. Cisco is just like any other software/hardware... it isn't perfect, thinking it is... well that is just naive.

    23. Re:Secure ? by johne_ganz · · Score: 5, Interesting
      Forgive my ignorance, but if the code is truly solid code, without buffer overruns and the like, shouldnt this theoretically not matter

      Yes, provided it's solid code. So the obvious question is: is it solid code? What makes for solid code? I'm of the opinion that it is far from 'solid' code for two main reasons.

      The history of the code base.

      It's monolithic nature.

      IOS started out on the same CPU board as Sun (and SGI) computers: The Stanford 68000 board. Remember what Sun stands for: Stanford University Network. These three companies all started from the same hardware design. Cisco took this design and the original software for running the Stanford networks (some allege they stole it) and kept adding on to it. The 68000 had no MMU, and therefore provided no protection of one process from another- any process could write to any part of memory.

      The problem is that the software still has this in its genes. While IOS will make use of modern MMU's to do some level of protection (such as marking read-only the text segment), at its core its still a "every process is fully trusted" design. Now, this does have some advantages- in the old days when the forwarding was all done on the CPU in the interrupt context this was a huge win. Saving all the state and MMU context switches could really lower performance.

      The drawbacks, however, are pretty bad IMHO. Since there's no separation of processes, any one process can bring down the system. If BGP was running under Unix, and it ran in to a problem where it would seg fault, under IOS the entire system would panic and reboot. IF it happens to catch the error, which is much less likely to happen because there's no separation of processes and what memory resources belong to that process as opposed to other processes.

      The monolithic nature of IOS also tends to breed lax programming practices. Who needs to ensure that everything is tip top when everything is self contained? There's a certain darwinian pressure that gets placed on a system when anyone can write code for it and expects the system to stay up and running like Unix. Under IOS, none of that exists. As a matter of fact, the pressure is in the opposite direction- when you write something that crashes the system- don't do that. Furthermore, the code tends to largely interact with only a few other implementations, and the one it interacts with the most is itself (cisco's talking to cisco's). Not a lot of pressure to find those odd ball corner cases and fix them... Just the kind of corner cases that are the most likely to result in exploitable bugs.

      So, are there security problems with IOS? You'd better believe it. All you have to do is peruse the BugTracker database and look for bugs that cause a crash. Things like "malformed SNMP request causes crash" are prime candidates to exploit.

    24. Re:Secure ? by gnu-generation-one · · Score: 1

      "You're assuming that code is static."

      And more to the point, assuming an equal level of interest in different types of code. A cracker could concentrate their resources in one area, while cisco would have to dedicate their time to all areas.

    25. Re:Secure ? by Not_Wiggins · · Score: 1

      Given your scenario of 15 people (yes, I know you just picked a number at random, so I'm not picking on that), it might take 15 years.

      However, how long would it take a community of crackers to find an exploit?

      The news that Cisco has had its router software ripped-off is relatively old news (!). Cisco sued Huawei Technologies for ripping off their router. I'll give you a hint: if you're using a router from Huawei, you use the Cisco manual.

      Nobody believes in the mythical "man-month" anymore (ie, throw twice as many people at a task and it'll get done in half the time... WRONG), but with 15 THOUSAND people looking at this, I think they'd be able to not only find flaws in the code, but find flaws in the underlying architecture of how the software works (ie, protocol weaknesses). And these people would be looking to "mess with the internet," not just rob Cisco. 8/

      --
      Diplomacy is the art of saying, "Nice doggie!" until you can find a rock.
    26. Re:Secure ? by Almond+Tree · · Score: 0

      So who's router was the code hiding behind when it was "liberated"? Ta Da! I rest my case.

      --

      bau bau chicka chicka mau mau

    27. Re:Secure ? by Anonymous Coward · · Score: 0

      There will almost certainly be bugs found, but not necessarily ones that can be exploited as vulnerabilities.

      Most bugs with security implications that are found in general purpose operating systems are not related to the processing of network traffic, but with the end-applications handling the content of the traffic. This is natural due to the nature of the tasks.

    28. Re:Secure ? by WaldoJMU · · Score: 1

      Except that Cisco has no real incentive to find bugs in their code, whereas a cracker does. Motivation makes a huge difference. And why would Cisco need to do strict audits on their code? Nobody outside the company will ever see it. Right?

      Wrong. FOR EXAMPLE, Cisco goes after numerous certifications for their devices, such as FIPS 140-2 for their crypto and Common Criteria for their IA features. Both of these certifications require an in-depth code-review to be performed by an accreditated testing laboratory.

      Now, granted, the source code for IOS (or for any other mature software application or OS) is *HUGE*, and thus the code reviews for these types of certification efforts are in reality targetted to only the source code that implements the major features of interest to that particular certification... but (as a FIPS and CC consultant) I have seen these code reviews (for certain unnamed vendor(s)) get waaaaaaaay out of scope when the source code of interest was just plain BAD: when a problem is found the lab tells the vendor what to fix, but when the code is very messy or buggy I've seen the lab personnel say "Gack! This code is so bad, we don't trust that your fixes to this particular code will provide ANY security, because the rest of the code is probably equally bad! We're going to need 6 more months and $100,000 more in order to fully review ALL of your code." THAT is when you know that the whole certification effort is f00bar. :)

    29. Re:Secure ? by Ironica · · Score: 1

      Here's my prediction of the effect that this will have on Cisco's sales, and on Cisco's share price. Zilch.

      I don't know anyone who's choice of Cisco products was predicated on the closed source nature of IOS.


      True, but... Cisco has just started up a massive ad campaign about their self-securing networks. The fact that they got hacked *at all* will have an effect on their sales, most likely... if they can't keep their own source code secure, why should you trust them with your network?

      --
      Don't you wish your girlfriend was a geek like me?
    30. Re:Secure ? by Anonymous Coward · · Score: 0

      Except that Cisco has no real incentive to find bugs in their code, whereas a cracker does. Motivation makes a huge difference. And why would Cisco need to do strict audits on their code? Nobody outside the company will ever see it. Right?

      How does Cisco have no real incentive? Their incentive is to protect their customers and the equipment they use. If Cisco didn't give a shit about security in their products, then I think we would hear about alot more buffer overflows and other holes in their equipment. Unless you can cite some specific examples of them showing no incentive...

    31. Re:Secure ? by bluesnowmonkey · · Score: 1

      Except that Cisco has no real incentive to find bugs in their code, whereas a cracker does. Motivation makes a huge difference. And why would Cisco need to do strict audits on their code? Nobody outside the company will ever see it. Right?

      Um, no, you got it backwards. Crackers have no real motivation -- you couldn't even brag if you brought down the internet for a day (well, unless you LIKE jail). Cisco has a multi-billion dollar business built on the security of their products.

    32. Re:Secure ? by banzai51 · · Score: 1

      So by extension of your arguement, you believe large companies innovate at a larger rate than smaller companies? By your (and the OSS arguement) they should. Thoughts?

    33. Re:Secure ? by gosand · · Score: 1
      How does Cisco have no real incentive? Their incentive is to protect their customers and the equipment they use. If Cisco didn't give a shit about security in their products, then I think we would hear about alot more buffer overflows and other holes in their equipment. Unless you can cite some specific examples of them showing no incentive...

      If they are like 99% of the companies out there, they have released their products with known issues in order to meet deadlines. And they don't have time to go back and fix anything but the critical ones. Of course, this is just the bugs that they know about, not the ones they haven't found. My definition of "bugs" also includes any backdoors or hardcoded values in their products.

      That kind of stuff happens all the time, when you don't think anyone else is going to see your source code. THAT is what I meant by incentive. Most companies release code with a certain known risk in order to meet schedules. They make compromises that they would most likely not make if the source code was viewable by everyone. So the code gets leaked, and now they are probably going to have to scramble.

      Even if they do perform strict code reviews, I am guessing that there are a few uncomfortable people over there now that the code is out in the wild.

      --

      My beliefs do not require that you agree with them.

    34. Re:Secure ? by Bill+Privatus · · Score: 1

      I'll let someone far more erudite say it for me:

      There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies and the other is to make it so complicated that there are no obvious deficiencies.
      - C.A.R. Hoare

      'nuff said.

      --
      Redundancy is good; triple redundancy is twice as good! - Me.
    35. Re:Secure ? by HiThere · · Score: 1

      "They" have lots of incentive. But that's not the problem. Programmers don't think the same way the hax0rs think. They think about what the program is supposed to do. Sure, they try to cover all the bases, but .... "it's impossible to make something foolproof, because fools are so ingenious". There are always holes. Count on it. Even Linux has holes. Even BSD has holes. But you only see the holes if you are thinking about it in a way that causes them to show up.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    36. Re:Secure ? by prisoner-of-enigma · · Score: 1

      Except that Cisco has no real incentive to find bugs in their code

      Oh really? And I suppose avoiding a major public relations nightmare is no "incentive" at all for Cisco to check their own code? Did you never stop to think that Cisco has a very BIG incentive to check their code for possible exploits, namely the risk of losing lots of customers if security holes start popping up all over the place?

      Some people just won't give a company any credit for doing any kind of fiduciary duty whatsoever. You just assume that the greedy, heartless megacorp is purposefully trying to make the shoddiest product it can and sell it for the highest price it can. While Cisco undoubtedly tries to charge a premium for its products, it does put these products through one helluva QA cycle. How many exploits on Cisco gear do you regularly hear of? Not many, and it's not for want of trying.

      Give Cisco some credit, even if they are a capitalistic company. They aren't out to steal candy from babies and enslave the human race, they're trying to make a good product for people and turn a profit at the same time.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    37. Re:Secure ? by 3l1za · · Score: 1

      Ahhh but it's the asymmetry.

      A would-be hacker just has to find one bug...

      Ross Anderson describes it much better... -- *.pdf format

    38. Re:Secure ? by su2ge · · Score: 1

      But of course. There is no perfect solution. I can understand what you mean about BGP though, but you can buy more memory for the routers and that'd probably be the best solution for that. I understand that certain features cause certain problems, but if it were me, I'd be using some slightly older tried and true IOS versions including those features. Also, if something doesn't work, they count on you to report it so they can fix it and provide you with better service.

  8. unlikely by beware1000 · · Score: 4, Funny

    In other news, Microsoft, Valve and Cisco to give free seminars on network security!

  9. I may be ignorant, by slycer9 · · Score: 1

    Or merely misinformed, as I'm not much of a Cisco fanboi, but...

    Aren't their routers basically embedded *nix boxes? I can understand them developing their own frontend for such, but isn't the majority of the underlying code *nix based? If so, how detrimental can it be for that code to be leaked? Conversely, if it's the frontend code which has been stolen, how many security hole....oh yah, Windows 95...ne'er mind...

    --
    Don't park drunk, accidents cause people.
    1. Re:I may be ignorant, by cyberfunk2 · · Score: 1

      You do however appear to be a fan of Avril Lavigne (sp?)

      Look ! Look ! He likes something popular ! Lets get em' !

    2. Re:I may be ignorant, by slycer9 · · Score: 1

      >>You do however appear to be a fan of Avril Lavigne

      OK, I can easily claim ignorance on this one.

      To quote Jay (Of J&SB):

      "What the fuck are you bitches babbling about?"

      Seriously, how are you extrapolating Avril Lavigne from my post?

      --
      Don't park drunk, accidents cause people.
    3. Re:I may be ignorant, by JayAdams · · Score: 0

      When you said Fanboi...

      That little punk-ass beotch Avril Lavigne has a song called Sk8rboi. (Skater boy)

      On an unrelated (sorry, directly related) matter, I would really like to punch her in the face.

    4. Re:I may be ignorant, by Anonymous Coward · · Score: 0
      Seriously, how are you extrapolating Avril Lavigne from my post?
      Uhh ... I'm not sure if this is what cyberfunk2 had in mind, but perhaps it's because you basically quoted the chorus from the song Slipped Away (track 12) from her new Under My Skin album more or less verbatim?

      I may be ignorant
      Or merely misinformed /
      I'm not a fan, but
      I sure can understand...


      Nahh, that couldn't be it. ;-)
    5. Re:I may be ignorant, by slycer9 · · Score: 1, Funny

      >>Uhh ... I'm not sure if this is what cyberfunk2 had in mind, but perhaps it's because you basically quoted the chorus from the song Slipped Away (track 12) from her new Under My Skin album more or less verbatim?

      I may be ignorant
      Or merely misinformed /
      I'm not a fan, but
      I sure can understand...

      Nahh, that couldn't be it. ;-)

      Wow, that's weird as all Hell, and of course there's no way to verify, but I've never heard Avril Lavigne that I know of before. For some reason I'm assuming BritneyPop? My tastes run a bit more along 'Nick Cave' lines.

      Gotta admit, this is a Hell of a way to start my day, I feel like Dali is peeking over my shoulder now, waiting for Rod Serling to step from behind the daisies.

      *shakes head*

      --
      Don't park drunk, accidents cause people.
    6. Re:I may be ignorant, by jx100 · · Score: 0

      ..and the fact that he knew the song well enough to actually recognize it when someone says the lyrics says nothing.....

    7. Re:I may be ignorant, by johne_ganz · · Score: 1
      Aren't their routers basically embedded *nix boxes?

      No. IOS isn't based on any operating system. IOS has very little in the way of modern opperating system services. As a matter of fact, it's a cooperative multitasking system- any one process can lock up the system or stamp on the memory of any other process.

      It's because of it's historical roots- these types of embedded systems were easier to write (at the start) and faster (less overhead, faster context switches). Today, I think it's a huge liability.

    8. Re:I may be ignorant, by MCraigW · · Score: 1


      Averil Lavigne has a song called "Skater Boi". You spelled "fan boy" as "fanboi".

    9. Re:I may be ignorant, by cyberfunk2 · · Score: 1

      It was actually a two pronged jab, both that and the Sk8trBoi Refrence.

  10. no, you misinterpreted their intentions... by Anonymous Coward · · Score: 1, Funny

    They plan to fork the 12.3 tree and release SOI 12.3 server as a free, open-source alternative to IOS.

  11. 800MB of source code? by Anonymous Coward · · Score: 0

    How big is this IOS anyway?

  12. And the secret backdoor password is... by 192939495969798999 · · Score: 2, Funny

    1...
    2...
    3...
    4...
    5!

    I always thought the big company that would have this happen is Microsoft, but I guess people got ahold of win2k's source a while back... it's still really surprising to see this happen to Cisco. Does it impress anyone else that they have an 800 MB source on the O/S? That's a lot of code!!

    --
    stuff |
    1. Re:And the secret backdoor password is... by Janek+Kozicki · · Score: 1, Insightful

      linux kernel source unpacked takes 150MB, compare yourself. Maybe they have stolen several versions of the source?

      --
      #
      #\ @ ? Colonize Mars
      #
    2. Re:And the secret backdoor password is... by Alranor · · Score: 0, Funny

      12345??

      That's the combination to my luggage ....

    3. Re:And the secret backdoor password is... by Anonymous Coward · · Score: 0

      Yeah it dosn't help anymore to have locks on luggage going to the airport. First thing the security people tell you when you checkin your luggage is to unlock it so we can search it.

    4. Re:And the secret backdoor password is... by thpdg · · Score: 0, Offtopic

      "That's the stupidest combination I've ever heard in my life. That's the kinda thing an idiot would have on his luggage."

      --

      -Patrick

      "They never stop thinking about new ways to harm our country and our people, and neither do we."

    5. Re:And the secret backdoor password is... by jpmkm · · Score: 1, Informative

      Have you been reduced to only reading the slashdot headlines? If you had even read the writeup you would have seen that the person got two versions(12.3 and 12.3t). And you said it yourself - linux is just a kernel. Imagine how big the source code is for a full GNU/linux operating system. 800 megs does not sound entirely unreasonable for two versions of an operating system.

    6. Re:And the secret backdoor password is... by Anonymous Coward · · Score: 0
      Does it impress anyone else that they have an 800 MB source on the O/S? That's a lot of code!!


      Pffft... unsavory wimps!

      Microsoft purports that their source code is over...
      (pinky to the edge of mouth)
      FORTY BILLION BYTES.

      Unless of course you're in the Europe, in which case the OS shrinks to a more reasonable number...
    7. Re:And the secret backdoor password is... by LnxAddct · · Score: 2, Insightful

      The thing that I find the most interesting is that first this shows that whatever security products they are selling obviously aren't good enough because there is someway around them(assuming Ciso would be using their own best products). But more importantly, if this were an open source project like Gnome, then we'd have up to the second details on what happened, why it happened, how it happened, what was accessed, whats at risk, etc... In the closed/proprietary world this doesn't happen, we are all just basically left in the dark and have to accept whatever they tell us. All the more for linux based routers!
      Regards,
      Steve

    8. Re:And the secret backdoor password is... by Anonymous Coward · · Score: 0

      I think you mistyped OpenBSD.

    9. Re:And the secret backdoor password is... by Janek+Kozicki · · Score: 1

      too much work to read everything :) I barely keep up with /.

      --
      #
      #\ @ ? Colonize Mars
      #
  13. If IOS was Open Source... by pdaoust007 · · Score: 4, Insightful

    All of these apocalyptic arguments about the Internet going down etc. would be moot...

    Then again one has to wonder how Cisco would have created their empire if their code would have been open sourced. A lot of their business is not only selling H/W but ISO features.

    1. Re:If IOS was Open Source... by Yogurt+Earl · · Score: 0

      I believe you mean "it would be moo" You know moo, like a cows opinion, it doesn't matter.

    2. Re:If IOS was Open Source... by drinkypoo · · Score: 1

      Guess what? If this story really is true, IOS is Open Source. It's just not Free or free :D

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:If IOS was Open Source... by Anonymous Coward · · Score: 0

      But it will soon be "free," if you know what I mean. (wink, nudge)

  14. Suspect profile by Anonymous Coward · · Score: 5, Funny
    Here is my suspect profile:

    1. French or German
    2. Linux/open source zealot
    3. Lives in parents basement
    4. Showers monthly

    1. Re:Suspect profile by eclectro · · Score: 0


      You forgot one;

      5. Chicken of the she.

      --
      Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
    2. Re:Suspect profile by skasingularity · · Score: 0
      1. French or German

      Nevermind, that would just be too easy. ;)

      (no offense to my "foreign" freinds!)

    3. Re:Suspect profile by Mateito · · Score: 0, Offtopic

      > 4. Showers monthly

      I can't work out if that's meant to be an insult or a compliment.

    4. Re:Suspect profile by upside · · Score: 1

      I suspect he/she likes to lurk on messageboards and posts "witty" comments anonymously.

      --
      I'm sorry if I haven't offended anyone
    5. Re:Suspect profile by Anonymous Coward · · Score: 0

      > 4. Showers monthly

      I can't work out if that's meant to be an insult or a compliment.


      How is that Offtopic? One of the funniest comments on this thread! Mod him up as such, people!

    6. Re:Suspect profile by HiThere · · Score: 1

      Well, that tells me who you are.

      You didn't mention any evidence that would lead me to believe that your profile is any better than my wild guess (which, because it's a wild guess, I'll keep private).

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  15. Cisco IOS built on BSD by p.rican · · Score: 3, Interesting

    I recently finished CCNA training and asked the instructor what OS CiscoIOS was based on and I was told it's based on BSD OS. He didn't tell me which BSD though....

    --

    /. --"Demented and sad....but social" -Judd Nelson

    1. Re:Cisco IOS built on BSD by LizardKing · · Score: 5, Interesting

      I recently finished CCNA training and asked the instructor what OS CiscoIOS was based on and I was told it's based on BSD OS. He didn't tell me which BSD though....

      It's descended from the Unix related work done at Berkeley in the early 1980's. I can't find a suitable link at the moment, but from what I remember there was some controversy about the commercialisation of the code. Much of the work was while the future Cisco founders were still employed at the university. This meant it should have belonged to the Regents, and released under a BSD license. If so, then it's ironic that the code is in the public domain, albeit under dubious circumstances.

      Chris

    2. Re:Cisco IOS built on BSD by thogard · · Score: 1

      I was using a cisco AGS+ router over a decade ago that ran IOS so I would bet its The BSD... something between 4.2 and 4.4 Tahoe.

    3. Re:Cisco IOS built on BSD by Sleeper · · Score: 2, Informative

      as far as i remember the founders of Cisco are from Stanford not Berkeley.

      --
      - Back off man. I am a scientist
    4. Re:Cisco IOS built on BSD by Old+Uncle+Bill · · Score: 0, Offtopic

      Wow, you mean students actually made some money off of their inventions rather than the school? How novel. One of the schools here consistently hands out class projects with the sole purpose of using the students' designs and code for commercial gain (and professor notoriety). Personally, I think those students pay enough money in tuition every year to keep their inventions. I rate this right up there with the highly ethical tradition of college sports.

      --
      Yes, I am an agent of Satan, but my duties are largely ceremonial.
    5. Re:Cisco IOS built on BSD by Anonymous Coward · · Score: 1, Informative

      No, actually Cisco 'Classic' router IOS in its current state is much more closely related to an old DEC operating system. About 10-12 years ago, Cisco paid an 'unspecified' sum of money to DEC for the rights.

      Also, please remember that IOS is partially a marketing term; the software running on the 800 series is not entirely the same, identical code running on a 7500. The RAM requirements alone make that absurd.

      And the Cisco founders started at Stanford, not Berkeley.

      Anonymous CCIE and former long-time Cisco employee

  16. Rough translation of 'bragged' link... by iapetus · · Score: 5, Informative

    "As SecurityLab discovered, on the 13th of May all the source code of the CISCO IOS operating system, which is used in the majority of CISCO's network installations was stolen. The full extent of the stolen information runs to about 800MB compressed.

    According to our information, the release of fragments of the source code came about due to a break-in to the corporate network of Cisco System. Representatives of Cisco System have meanwhile made no comment on the incident.

    The information came from a certain individual under the nick of franz on darknet@EFNet IRC, where he also presented a small part of the source code (about 2.5MB) as evidence.

    Below are links to the first 100 lines of source code from the files ipv6_tcp.c and ipv6_discovery_test.c."

    Apologies for any errors - my technical Russian's a little rusty. :)

    --
    ++ Say to Elrond "Hello.".
    Elrond says "No.". Elrond gives you some lunch.
    1. Re:Rough translation of 'bragged' link... by HiThere · · Score: 1

      Personally I suspect that the intrusion was via "social engineering". And OS9 won't protect you from that.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  17. Go for it Cisco by Stokey · · Score: 4, Insightful
    Just do it!

    Open source all your code. It's too late now (cat/bag/out of). Set an example to the rest of the business community.

    --
    Natsu gusa-ya, Tsuwamono domo-ga, Yume no ato
    1. Re:Go for it Cisco by mumblestheclown · · Score: 1
      ah, of course there was going to be a troll like this.

      the simple fact is, and as much as it pains me to say this, SECURITY BY OBSCURITY DOES WORK.

      now, before you turn on your flamethrowers, consider this: if cisco opened their source last year, would you have looked at it since then in a meaningful way? cisco employs dozens to hundreds of people who look at their source code all day every day. are you going to have such an interest in doing the same work that those people for real salaries for free?

      there may be an academic researcher or two who may be a minor exception, but the fact of the matter is that i doubt there's even one white hat who would spend their lazy weekends bug checking cisco's (a multi-billion dollar company) code. i mean, really.. why? you have no real motivation at all. on the other hand, if the source was opened up, a black-hat hacker does have motivation (notoriety, crEd, whatever) to burn the midnight oil looking for holes.

      you see boys and girls, it's not just whether the source code is 'open' as in freely obtainable that matters, it's *how many eyeballs will actually look at it*. you could open source the code to all sorts of meaningless and/or for-profit crap today, and i guarantee you that the most you'd do would be to attract more black hats than white hats..

    2. Re:Go for it Cisco by the_mad_poster · · Score: 4, Interesting

      SECURITY BY OBSCURITY DOES WORK

      *sigh* And, of course there's going to be a troll like this.

      No, it doesn't, but thanks for playing. See, someday maybe you'll learn the painful lesson that Cisco is learning now: Security Through Obscurity only works as far as your REAL security measures can protect it. Gee. Looky there. Cisco's cat just left the bag, and why? Becuase the network security wasn't strong enough to protect it. All these years of obscurity are now on the brink of becoming completely worthless because the REAL protection wasn't there just long enough to let it happen. The second that code hits a public FTP server, STO at Cisco became absolutely useless.

      But, hey. If you want to rely on STO for anything more than your last line of defense, be my guest. Just promise me you won't be mad when I laugh at you for getting burned by it.

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    3. Re:Go for it Cisco by plover · · Score: 1
      Sure, the black hats will be all over this like flies on p00p.

      But so will the white hats, and the gray hats.

      For both the white and gray hats, finding a weakness is their ticket to 15 minutes of fame. "Slightly shady" companies like eEye or @stake got their starts as hacker groups that found profit in promoting their l33t ski11z by discovering and announcing vulnerabilities. They found that while hacking for bragging rights is really fun, turning that newfound glory into IPOs was really, really a great way to make some serious cash.

      The thing is, security by obscurity may work; or, it may not. Obscurity obscures both ways. If there's a bad-guy ring who discovered a Cisco weakness two years ago and has been using it to rob on-line banks (or whatever,) who knows? Their exploit might be so slick that it leaves no traces. But now with the code open the race to find these bugs is on. And if the racers discover a flaw that bad guys have been exploiting in the past, well, that hole is plugged because the obscurity is gone.

      A leak of this magnitude is sure to attract eyeballs like crazy. And at least a few of those eyeballs will be coming from underneath white hat brims. Sure, they'll be outnumbered, but they'll be there; and it takes only one good guy to ruin the bad guys fun.

      (Sorry if this was kind of rambling.)

      --
      John
    4. Re:Go for it Cisco by Anonymous Coward · · Score: 0

      Who gives a shit either way.

      Open source software will have holes.

      Closed source software will have holes.

      As long as humans continue to make software, it will have holes. And in the rare circumstances where the software doesn't have holes, a stupid fucking human will allow social engineering to fuck up the security. So any way you look at it, humans will fuck up the secure aspect of any software. Just live with it.

    5. Re:Go for it Cisco by the_mad_poster · · Score: 1

      So, are you a troll, or do you just have a reading comprehension problem? Or, did you reply to my post thinking it was someone else's post? Because, what you said doesn't really have anything to do with what I said.

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    6. Re:Go for it Cisco by HiThere · · Score: 1

      Well, in a sense all security is "security by obscurity". If I have a complete core & disk dump of your computer, I can know anything that you have on it. So the chant "SECURITY BY OBSCURITY DOES WORK" is technically valid.

      OTOH, there are degrees and degrees. Rot-13 is better than no encryption at all...unless it focuses attention onto itself. And public key is so far pretty good as a concept, though some holes in various implementations have been discovered.

      The question is, do you gain more by public exposure than you loose? Cisco gained market share which was independent of security by keeping their code secret. And probably not too many people would have reviewed the code and helped them develop it. So while they can keep their code secret, they have probably benefitted. And the reports thus far have indicated that Cisco code is probably pretty sound (I haven't looked myself, and I lack the needed skill anyway, so I'm relying on secondary sources). One can still be pretty certain that some new holes will apear. How serious they are is another question, and that depends partially on the design (and not just the implementation). Some rumors claim that there are backdoors built in that will allow Cisco engineers to enter the routers without knowing your passwords. If this doesn't depend on knowing, say, your router's serial number (i.e., a number printed on the back of the router) then this would be a serious problem. (Note the security by obscurity feature?) But if it does, then it would be a quite minor problem (unless the serial number is internally readable).

      Security will always depend on a mix of obscurity and design. You will always need both parts. Good design limits your dependance on obscurity (perhaps only your private key needs to be kept hidden), but the requirement will always be there. Since Cisco also wanted other benefits of obscurity (i.e., benefits beyond that of increased security) their trade-off of benefits tilted in favor of keeping more features hidden. And since few people work on developing software for routers, the expected benefits of not keeping things hidden was smaller. Now, however, the bill may come due.

      Do note, however, that Cisco is now a large and successful company. The gains that have have reaped in the past by fostering secrecy will probably overweigh the costs of currently loosing it...unless they made some really unethical or poor design decisions (rather than merely poor implementation decisons).

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  18. Lemme guess by eclectro · · Score: 2, Funny


    The password they used to get access to the crown jewels was ciscokid

    Pretty 133t if you ask me.

    --
    Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
    1. Re:Lemme guess by Anonymous Coward · · Score: 0
      The password they used to get access to the crown jewels was ciscokid
      Are you sure it wasn't mafiaboy?

      --
      Free Naked Pictures
    2. Re:Lemme guess by 3.5+stripes · · Score: 0, Offtopic

      Nah, it was thongthongthongthong

      --


      He tried to kill me with a forklift!
  19. what the fuck? by CAIMLAS · · Score: 4, Insightful

    Two direct links on the front page of slashdot to (literally) stollen IP?

    I wonder if Slashdot will get in trouble with Cisco for this? The moderators could have at least have checked the links, no?

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    1. Re:what the fuck? by Anonymous Coward · · Score: 0
      Two direct links on the front page of slashdot to (literally) stollen IP? ... I wonder if Slashdot will get in trouble with Cisco for this?
      Thanked, more probably. Two words: Free DDOS.
    2. Re:what the fuck? by Anonymous Coward · · Score: 0, Interesting

      "Two direct links on the front page of slashdot to (literally) stollen IP?"

      Not literaly, but metaphoricaly. It would have been "literaly" stolen only if the source code disappeared from Cisco's servers.

    3. Re:what the fuck? by ajs · · Score: 1

      More specifically, links to external articles that include the source. Those external sources could be taken down, but Cisco is going to be more concerned about the OTHER 797.5MB of source, not what Slashdot links to.

    4. Re:what the fuck? by Clovert+Agent · · Score: 1

      Technically, it's not stolen IP. Apart from the fact that it's not _stolen_ anything (since you can only violate copyright, not steal it), semantics aside it's only _allegedly_ copied code.

      Pending confirmation from Cisco, it's at best a pointer to where you can find something which is purported to be part of something which someone says might be covered by somebody else's IP.

      There's enough uncertainty in there to be perfectly safe. Even were it confirmed, I don't think Cisco's in the mood for a DeCSS-go-round over 200 lines of code out of 800mb. They're too busy getting subpoenas for franz's ISP, I imagine.

    5. Re:what the fuck? by Unregistered · · Score: 2, Funny

      "Technically, it's not stolen IP. Apart from the fact that it's not _stolen_ anything (since you can only violate copyright, not steal it), semantics aside it's only _allegedly_ copied code."

      Holy shit! Bill Clinton posts on /.

    6. Re:what the fuck? by Anonymous Coward · · Score: 0

      You could make the argument that parts of the source code are trade secrets. Then it becomes a case of industrial espionnage, no matter the laws on copyright.

    7. Re:what the fuck? by Anonymous Coward · · Score: 0

      well its no longer trade secret anymore

  20. Seminar sessions by T-Kir · · Score: 4, Funny

    In the seminars I can imagine how Cisco would explain they're love of being shafted, hence all the backdoor access (pun intended!)...

    ...Microsoft will just blab about how they CAN be trusted, and show everyone pretty pictures and a Matrix spoof to distract everyone...

    ..while Valve gets the dates for the seminar mixed up and turn up 6 months later.

    --
    Are you local? There's nothing for you here!
    1. Re:Seminar sessions by Anonymous Coward · · Score: 0

      Naw, Valve would delay the conference about six times (each time with Gabe Newell's increasingly annoying voice saying, "I've got my seminar all prepared but I just have to make a few minor tweaks..."). After the sixth delay, Newell blames the delays on the fact that some script kiddy stole his wallet and he couldn't afford cab fare to the airport.

      And then there's the Team Fortress 2 conference, originally scheduled for sometime in 1998...

  21. Not the first time by Anonymous Coward · · Score: 2

    This is not the first time that IOS code is circulating. Previous versions were available at least for the last five years.

  22. Makes you think.. by t_allardyce · · Score: 2, Funny

    Hmmm i wonder when the linux kernal source code will be stolen? oh yeah! never!

    --
    This comment does not represent the views or opinions of the user.
    1. Re:Makes you think.. by sumdumass · · Score: 1

      it's been stolen several times, just ask SCO..

      No seriously. It is somethign when everyone else is afraid of the source code being leaked into public domain/view when linux proudly places it there and begs for people to point out the flaws.

      I don't think there is any serious trade secrets that can't be protected by other means (legaly) that cisco would be huhrt if they opened up thier source and offered a bounty od lets say $50 to anyone (or thew first persons) finding a hole in it. Then maybe thier slef protecting network wousl really preotect itself. lol

    2. Re:Makes you think.. by t_allardyce · · Score: 1

      You'd think with all the patent laws in their favour no-one would actually need to close-source, just patent everything and sue anyone who so much as uses an 'if' statement.

      --
      This comment does not represent the views or opinions of the user.
    3. Re:Makes you think.. by sumdumass · · Score: 1

      damn, The one time I actually did want to spell check and hit the wrong button.

  23. The one thing not mentioned by RedShoeRider · · Score: 5, Interesting
    Thus far, I find it odd no one has inquired as to the exact nature of how the hell someone got so far into the system as to be able to copy source code. That's not something any company leaves sitting in /pub. Whomever pulled this off (assuming it's not bullshit) knew something (social engineering, perhaps), for I'm sure Sisco has been hammered by attacks for years, just like any large company.

    My one thought: it's all bullshit until Cisco comes out and says they were hacked. Anyone can put together a bunch of seemingly well-written code and say that they were l33t and got in to Cisco.

    The proof is in the pudding. And all I see so far is some sugar.

    --

    Chris Knight is my hero.

    1. Re:The one thing not mentioned by LizardKing · · Score: 2, Funny

      Anyone can put together a bunch of seemingly well-written code

      Many "professional" programmers can't, not at my company at least.

      Chris

    2. Re:The one thing not mentioned by groot · · Score: 3, Insightful

      Thus far, I find it odd no one has inquired as to the exact nature of how the hell someone got so far into the system as to be able to copy source code. That's not something any company leaves sitting in /pub.

      It's like some warped Stratego (TM) game, and the hackers have captured the flag.

      Now
      :
      1. The act of stealing it, sort of renders it useless, who would want a firewall that can be broken into an its own sources stolen.

      2. This embarrasement would have been circumvented if they had most of the code in the open source domain, especially the firewall. A good algorithm should be be able to resist the test of scrutiny of its sources.

      3. The routing algorithm would be valuable but I doubt that it is what the hackers were after. So maybe they would want not to open source it.

      Bottom line, those things which are not core to your business should be release to the open source community. Of course some, like MS believe the universe is their core, so some will never change.

      --laz
      --
      "Just remember, it takes a village idiot." -- The Motley Fool.
    3. Re:The one thing not mentioned by Zapman · · Score: 1

      This hit over the weekend, so I imagine that Cisco is still in damage control mode. A stratagy for dealing with this is shutdown ALL lines of communication and get the house in order before you talk to anyone.

      Besides, the story yesterday on /. had a link to an IRC brag. The guy got access to their network, and to their sourcesafe repository, hacked together his own faux sourcesafe client, and sucked the code out that way.

      It now being Monday (and 6:00 AM on Monday in California), it wouldn't supprise me if they have a press conference or press release (late) today or tomorrow.

      --
      Zapman
    4. Re:The one thing not mentioned by upside · · Score: 0

      The proof is not in the pudding.

      The proof of the pudding is in the eating.

      Thank you. /pedant

      --
      I'm sorry if I haven't offended anyone
    5. Re:The one thing not mentioned by atheos · · Score: 1
      it's all bullshit until Cisco comes out and says they were hacked.


      So, using this logic all Cisco has to do is stay quiet, and this
      says they were never hacked?

      ya, That's bullshit alright.
    6. Re:The one thing not mentioned by meadowsp · · Score: 1

      Sisco deserves a hammering for years after that thong song.

    7. Re:The one thing not mentioned by Anonymous Coward · · Score: 0

      Man, you are stupid.

    8. Re:The one thing not mentioned by robin_j · · Score: 1
      Anyone can put together a bunch of seemingly well-written code and say that they were l33t and got in to Cisco.

      Anyone??? Did you ever see my attempts to write C code? :o)

    9. Re:The one thing not mentioned by drinkypoo · · Score: 1
      While I agree that it is fairly pathetic for Cisco's IOS sources to be stolen the fact is that it was only a matter of time. If some cracker didn't get in, a disgruntled release engineer, or backup manager would have ample opportunity to acquire the sources. In fact, there's no one who can say that didn't happen, unless we get an announcement from Cisco saying "this is how it happened" and the people with the source confirm. Otherwise, any statement is suspect. As such we will probably never know.

      All kinds of proprietary sources are floating around the net. For example, some complete versions of SunOS 4.1 are known to be out there, and some AIX 3 sources as well.

      You are correct that their code should probably be open source. If it really has been stolen, once it is distributed there will be little incentive not to open source it, since they will have nothing to lose (I.E., their obscurity.)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  24. might be a good thing ... by xplosiv · · Score: 2, Interesting

    Am I the only one who thinks this 'might' be a good thing? Cisco now has incentives to give their code another look and hunt down any serious bugs they might not know about yet, resulting in a more secure OS. I doubt it would happen, but it's what I would do if my source code was stolen.

  25. That's why corps should stick to dial-up.. by Anonymous Coward · · Score: 5, Funny

    ..they would have noticed then if 800 MB was being downloaded.

    1. Re:That's why corps should stick to dial-up.. by Anonymous Coward · · Score: 0

      Not likely. Remote access logginmg is not a sniffer; there's usually no way to tell precisely what's going on, just what boxes were accessed by whom.

      Most likely valid credentials were used for access anyway, either stolen or easily guessed.

    2. Re:That's why corps should stick to dial-up.. by bruthasj · · Score: 2, Insightful

      It's funny until you actually have to work with corporations with this mentality.

    3. Re:That's why corps should stick to dial-up.. by Anonymous Coward · · Score: 0

      Yep. Whenever I attend a security conference, the standing joke is that the biggest threat to network security are the network administrators.

      We have a network monitoring system that alerts the infosec team whenever the "Domain Admins" group membership changes. You would not believe how many times a day that normal users are made domain admins just to "fix" problems.

      They got all ticked off when we blocked Internet access to any member of the domain admin group. This now acts as an early warning system that someone was left in the DA group but they are mad that they now have to have two accounts.

      The network admins whined to the CIO, who couldn't understand why this was necessary. After we explained that a network-aware virus caught from a domain admin would wipe out every computer and server in the company, he caught on.

      Old American Proverb: May you never be cursed with a "business side" CIO.

  26. Nota Bene to Cisco: time to GPL the code... by Anonymous Coward · · Score: 0

    Well, if Cisco would just GPL the code, we can
    improve it...get the bugs out, more secure, etc.
    Why are some companies SO slow at recognizing this?
    Fine, want to keep your code secret and proprietary?
    You won't be getting any of my business, using
    bug-filled, secret, full of security holes
    software...

  27. Cizzz-coeee by caereth · · Score: 2, Funny

    Perhaps we will now see a Cizzz-coeee IOS source code detector van in the near future.

  28. How is this different from the original reporting? by forged · · Score: 0

    And no one shouting 'DUPE' ??? I don't get it.

  29. Woohoo by Chuck+Chunder · · Score: 1, Funny

    There's at least a couple of days off work there!

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  30. Vulnerability by version by RicoX9 · · Score: 5, Insightful

    I think that susceptibility will depend on what source was stolen. Was it the ENTIRE source? Or was it just pieces? They (the cracking types) may discover a hole in something that exists only in the Enterprise feature set, leaving most of the exposed routers on the Internet un-compromiseable (As most companies aren't going to pony up for the most expensive feature set when all they're doing is shuffling IP packets).

    Also could find a problem in basic TCP/IP code, making every Cisco router on the planet a revolving door. I find this scenario highly unlikely, as thier base code is probably a lot more stable and reviewed than the newer, more advanced features.

    1. Re:Vulnerability by version by swb · · Score: 1

      They (the cracking types) may discover a hole in something that exists only in the Enterprise feature set, leaving most of the exposed routers on the Internet un-compromiseable

      That's a good point. The IP code has likely been subjected to many uses, bugs, fixes, reviews and so on.

      IPX? DECnet? Appletalk? Those bits are less popular and probably have more potential problems, but have a much lower security exposure.

  31. Funny lines in the source code by MavEtJu · · Score: 4, Funny

    /*
    * Juniper engineers are weenies!
    */

    --
    bash$ :(){ :|:&};:
  32. QUICK ! React ! by rainer_d · · Score: 2, Funny
    Buy shares in companies that deal or lease fax-machines !
    When the internet gets shut down for a maintenance-period, their business will go through the roof.
    And don't forget to reserve enough machines for yourself, or your business might go through the toilet :-)

    --
    Windows 2000 - from the guys who brought us edlin
    1. Re:QUICK ! React ! by Eraser_ · · Score: 1

      Have you seen the lag on a windows machine going over a WAN for file services? Let alone having to FAX all those packets to and from our other location. I'll risk total compromise, thanks.

  33. 800Mb when compressed? by Andy_R · · Score: 1

    Am I the only one wondering what on earth they are filling that much space up with?

    Seems bloated to hell to me - what exactly do these routers do that take so much code?

    --
    A pizza of radius z and thickness a has a volume of pi z z a
    1. Re:800Mb when compressed? by aonaran · · Score: 1

      You are forgeting that IOS has to support a fairly wide range of harware and feature sets. Every router, switch, acesspoint etc. that cisco makes or has ever made has to have drivers in IOS

      For comparison, the Linux Kernel (2.6.6) is 34MB Bziped, 47MB unziped. It's likely that they are talking about 800MB of un-compressed code.
      Add on the size of all the userland programs like freeswan, webmin, telnet, openssh, openssl, tftpd, dhcpd, dpcpcd, ntpd, an ftpd, shorewall, etc. that would be needed for linux to have all the functionality of IOS and I think eventually you'll find that 800MB of source isn't as much as you might have thought.

    2. Re:800Mb when compressed? by Anonymous Coward · · Score: 0

      Wait! We already have most of the code to create a router!

    3. Re:800Mb when compressed? by tarballedtux · · Score: 1

      All that code is probably every line ever written from the beginning. Add up code for every device they sell, and most have had a dozen major releases plus many minor releases. Don't forget the releases that just add features. Plus the possibility that that isn't all IOS. Could be code for some other software of theirs. --Tarballedtux

  34. Er.... by brunes69 · · Score: 1, Flamebait

    You think the TV networks would continue to operate if 62% of the worlds routers wen't offline?

    If so I envy you, since you seem to be living in a fantasy land...

    1. Re:Er.... by mwood · · Score: 1

      Nah, the networks they depend on are mostly made of gear from outfits like Siemens, Ericsson, and Alcatel. cisco's biggest box is pretty small stuff compared to what it takes to run the wires that the Internet rides on. And IP is even worse for carrying a decent TV signal than it is for voice.

  35. If it had been a microsoft leak ... by Anonymous Coward · · Score: 5, Interesting

    Well ... is it not kinda strange? A few months back when the Windows code was leaked, most of Slashdot was screaming about 65,000(i dint cook that number!) Windows bugs. Well, nothing happened really. Except an IE 5.x bug, which was patched silently before the source code leak.

    Now lets compare the REAL security issues.
    1. The number of people who were dissecting the Windows Source Code are much more than those trying to find a Cisco hole.
    2. Even without the Windows Source, we can reverse engineer large parts of the Windows Sources and identify problems. With the leak it just became easier. I dont expect too many crackers trying to find holes in Cisco's IOS.

    This simply means that the chances of finding a security hole in Cisco is much higher than in Windows. Because now that the source is out in the open, its easier. Why would they choose to look?

    1. Bringing down those routers could virtually bring down most of the internet.
    2. The entire financial world uses them! If a hole is discovered it might just be the easiest way to get into those systems.
    3. It could be easier than trying to find a Windows hole, since (as from my earlier logic) many many people have already tried without results.
    4. The damage that could be done in those 2 cases are so immense, that a comparison would be irrelevant. ... Slashdotters, cant it be just possible that this leak might be much more disastrous that the Windows leak.

    [Troll: Btw ... its funny reading that Windows article again, and going through posts that talked abt non-existant security in Windows. And how many holes did people find.]

    1. Re:If it had been a microsoft leak ... by Anonymous Coward · · Score: 0

      i guess sasser was a figment of my imagination.

    2. Re:If it had been a microsoft leak ... by Geoff-with-a-G · · Score: 1

      No, this is great, I'm glad you mentioned Sasser, because you already made my point for me.

      Sasser, and many of the recent big-bad-worms came from Microsoft releasing the vulnerability notice along with their fix. Not from someone covertly analyzing the source code. Security through obscurity would have actually helped here. Not that I'm actually suggesting the policy, I'm just saying that these worms were created because Microsoft publically released details, not because they hid them.

  36. Again? by gkelman · · Score: 2, Informative

    The source code to IOS was floating round the net about 5 years ago. Obviously not the same as the latest version...

  37. Keys-in by LemonYellow · · Score: 1

    They just legally drive away... and return it the next day with wider wheels and a new sound system!

    1. Re:Keys-in by KamuSan · · Score: 1

      Come to think of it, the BMW analogy is flawed.

      Better analogy is:
      Leave the keys in your BMW so that everybody can make a duplicate. And then they add your big shiney wheels and sound system, and I can get a free upgrade as well.

  38. What? Nobody's said it yet? by leonbrooks · · Score: 1

    "OMG! What if this happened to Mandrake or SuSE?"

    --
    Got time? Spend some of it coding or testing
  39. This is why staying current is bad by Anonymous Coward · · Score: 0, Troll

    My routers run IOS 9, the desktops run Windows 95 and we use IE 4.

    Nobody has released an exploit for these things in ages, my costs are very low and I can buy 200 MB computers for a song when something breaks.

    Another upside is I don't have to worry about patching things, because none have been produced for years!

  40. Code theft? by Mr+Smidge · · Score: 4, Insightful

    Slashdot labels a story as theft when no portion of the source code was removed from Cisco's computers? Never!

    No, I'm afraid this is not 'theft'.

    Theft must incorporate a desire to deprive the rightful owner of said taken item(s). Surely we know this by now?

    Stealing, yes. Theft, no.

    </PEDANT>

    1. Re:Code theft? by protoshoggoth · · Score: 1

      I thought that the term regularly trundled out by our IP cognoscenti for general-oohing-and-aahing-over was "unauthorized copying".

    2. Re:Code theft? by Mr+Smidge · · Score: 1

      Yes, it is definitely "unauthorised copying", but it is also stealing:

      steal
      v. tr.
      To take (the property of another) without right or permission.


      The verb 'take' does not necessarily imply that what is taken is in fact removed, where as complete removal is in the definition of 'theft'.

    3. Re:Code theft? by cpghost · · Score: 1

      The verb 'take' does not necessarily imply that what is taken is in fact removed

      "Okay guys, let's take some pictures..." Reporters picking up pictures from the office walls. Airplane I.

      --
      cpghost at Cordula's Web.
    4. Re:Code theft? by cpghost · · Score: 1

      Isn't it actually spying? When a spy takes snapshots of secret documents, he's not stealing them. He just changes their nature from "SECRET" to "LETS PRETEND IT NEVER HAPPENED" (aka. "TOP SECRET"). But stealing?

      --
      cpghost at Cordula's Web.
    5. Re:Code theft? by Tom7 · · Score: 1

      You can't "take" the code from their servers, though. It's just impossible. The closest you could do is to make a copy, and then erase the original.

      Copying is different from theft/stealing/larceny both legally and ethically. It's fine to have opinions as to whether it is or should be right/wrong legal/illegal. But lumping it in with stealing is just misleading, and that is not a fair way to present your case.

      Of course, this is worse than copyright infringement, as it is misappropriation of trade secrets, which--presuming it is done for economic benefit--is actually a crime.

    6. Re:Code theft? by AK+Marc · · Score: 1

      Ah, yes. There is no difference in someone that takes great pains to protect their IP, but someone hits them with a targeted attack and coppies it and a company that purposefully releases IP into the public domain and then complains about how it is used while in the public domain.

      Anyone that sees a difference between the two scenarios must be an evil pirate out to steal billions from the **AA.

  41. shame on you! by Anonymous Coward · · Score: 1, Insightful

    Changing the way the public perceives issues involving IP requires consistancy.

    Whether its illegally copied songs or illegally copied code, IT IS NOT THEFT because nothing is stolen. No one that had the code before doesn't have it now due to this.

    OF COURSE this is wrong, and it breaks many laws including copyright laws and computer crime laws (unauthorized access, etc), but please, do not frame this argument using the wrong terms. This just digs us deeper in our hole.

  42. the code that is "shown" as Cisco IOS .... by Anonymous Coward · · Score: 4, Interesting

    I've looked at the sources on display at the russian site [IPv6 sources], that pretend to be from the IOS. Several things took my attention:
    1. Since when programmers, working for a serious company, write copyright notices for themselves in the header... Like if you work for, let's say, SCO (ha-ha), you will put in the header copytight by you, and then - who knows - might sue SCO for stealing code from you :)
    2. printf("\nAdding %P to ND cache", &target);
    The ND cache is really connected to neighbor solicit messages, but would the Cisco IOS be printing a message, saying that it is adding the address to the ND cache without checking debug flags, etc.? And I am sure it is not a matter of system design in this case. You cannot get the impression just from one tiny piece of code.
    3. Some post here were stating... "root" access, which certainly made me smile. The IOS is running cooperative multitasking and the tasks usually run at the same level.
    4. Ole Troan really works for Cisco Systems (in UK) and is the proud author of the IPv6 DHCP RFC specification 3633. So this is an argument that supports a little bit of the theory. Just didnt think that Cisco still has developers in UK. I thought they outsourced everything to India long time ago ;)))
    There are some more, but I'll save you the tiny details, like big endian or other nifty stuff in the code.

  43. Security Through Obscurity? by ThisIsFred · · Score: 3, Insightful

    Does this code contain the infamous "backdoor" account ever present on certain Cisco devices? It should would be worth a criminal's time to get a hold of that. Think of all the other information he could steal once he knew that.

    --
    Fred

    "A fool and his freedom are soon parted"
    -RMS
  44. But... but... by vaxer · · Score: 1

    We have the right to create deep links... and this is some pretty deep stuff!

  45. Re:unlikely? it happened by Anonymous Coward · · Score: 0

    I've attended at a MS seminar in Buenos Aires where i heard one of the top managers talking about security. After a long speech about the "do"s and "dont"s in computer security, he said: "...and that's why we never had a security problem at microsoft".

    This seminar was one of two weeks after the windows 2000/nt source code leak.

  46. Shouldn't we say 'copyright infringement'? by jocknerd · · Score: 1

    If it was the only copy of source code, then yes it was stolen. Otherwise it should be copyright infringement. After all, this is our claim regarding illegally downloaded music. Its not stolen. It's copyright infringement.

  47. A litte story by Anonymous Coward · · Score: 0

    I seem to remember that cisco bought a small compamy called grand junction, which produced switching products. they also had this product called IOS. Which is just the reason why cisco bought them. Cisco has just branded and improved someone elses product. it is that simple, i know a couple of people that work for cisco since way back in the day. And this is a story most of them can confirm.

    So is anyone looking for ppl, i am a CCNP in the southfield, mi area looking for a job. I am great with linux, bsd, and windows. Anyone?
    thedude_001@hotmail.com

  48. What pisses me off... by greendot · · Score: 1, Offtopic

    The thing that annoys me most is how Cisco is going to handle this.

    I bought one of their home/soho routers, the "cheap" $300 one. I wanted more meat to my home broadband than what Linksys had to offer.

    The day after I buy it I find out that the software is out of date and there are upgrades. Am I able to get them? Nope. I have to pay an extra $100/year to just get the software updates.

    Needless to say, this will be the last Cisco product I own.

    Considering the small form factor PCs out there, custom Linux firewall is in the works.

    1. Re:What pisses me off... by Anonymous Coward · · Score: 0

      Well gee, you can always return the items to the store. Enterprise equipment is like that, our phone systems never fail but we paid Avaya $12000 a year for maintenance contract

    2. Re:What pisses me off... by smeenz · · Score: 1
      That's because Cisco doesn't really build equipment for the home market (even though they do name some products as 'SOHO').. their target is really business, and businesses expect to pay ongoing maintenance/support fees for products they own.

      I would also point out that Cisco provide ISO updates to SOHO users free of charge for security fixes.

  49. Cisco is running Red Hat nowadays anyway by Geminus · · Score: 1

    I attended a Cisco Intrusion Detection System class a shortwhile back and laughed my arse off when I saw the Red Hat 7.3 installation screen. I asked the instructor for a copy of the modified source code and he just sat there looking stupid... nice. At least the worlds routers are not running Microsoft right?

    1. Re:Cisco is running Red Hat nowadays anyway by ZorroIII · · Score: 1

      The ids modules, content engines and NAM's all run Linux. But all current routers run IOS.

  50. Re:I download code every day. by Anonymous Coward · · Score: 0
    (ok, now this *could* be the same as leaving your keys in your BMW, because noone is able to steal it! They just legally drive away ;-) )

    No, they can't. But if you put a photocopier and a full set of schematics of both car and copier, it'd be legal for someone to plug the copier in, insert their own toner and paper, and copy the schemaitcs, then build their own BMW. Except for those nasty patents, but you should be in the EU anyway.
  51. The GPL doesn't pay by A.+Pizmo+Clam · · Score: 2, Funny

    Call me crazy or mod me down, but I'm positive that this has something to do with CICSO's previous tussle with the GPL .

    I can only assume one of two things:

    1. CICSO's use of code that's open to just anyone allowed a "hacker" to access vulnerabilities in its systems.
    2. Due to its earlier minor and well-intentioned misstep, some GNUlatic decided to take revenge on CICSO.

    In either case, this sends a loud and clear message to all businesses out there: messing with GPL code will get you burned, and burned badly. DANGER WILL ROBINSON!!!.

    Stay away while you still have your security intact. GNUlatics only want to hurt you.

    --

    Thank you for your support.
    1. Re:The GPL doesn't pay by Quill_28 · · Score: 1

      >In either case, this sends a loud and clear message to all businesses out there: messing with GPL code will get you burned

      Why because then if you do something the GPL'ites don't like we will do something illegal against you?

      I think it would be better to take cisco to court, not play software terrorists.

  52. Direct linking to source code by hkb · · Score: 1

    Way to go Slashidiots! Directly linking to stolen IP is one of your finer decisions. Thanks.

    --
    /* Moderating all non-anonymous trolls up since 2004 */
  53. Equipment by go3 · · Score: 1

    They didn't change the default administrator password on their Linksys BEFW11S4 router.

  54. Poor coding standards by jkabbe · · Score: 3, Funny

    Who would use critical hardware from a company that can't even decide where to put their curly-braces? Are they at the end of the line or on a line by themself? Make up your frickin' mind!!

  55. All they have to do now is pick an O/S license by Anonymous Coward · · Score: 0

    things would just be easier. GPL?, LGPL?, BSD-License?, Open License?

  56. Thanks so much by Anonymous Coward · · Score: 0


    That kind of BS is exactly why we keep losing our jobs to trained monkeys.

    1. Re:Thanks so much by Anonymous Coward · · Score: 0

      He's exactly right. If you can only do a basic config of a cisco router, you are very expendable, because people who can do that are a dime a dozen. If you want to not lose your job to trained monkeys, learn a bit more. Being able to solve problems quickly as they arise is what will keep you your job, not running through cisco config maker 20 times a day setting up a stupid little DSL connection.

  57. Re:I download code every day. by KamuSan · · Score: 1

    I am and since my BMW is not software, the patents are still valid ;-)

    But you're right, my analogy was incorrect. The difference with my analogy and Open Source is that, while you can drive my BMW away and deprive me of the use of my shiney, Topasblue Compact, with Open Source I'd still be able to use my software.

    And like above post says, they would be able to improve my BMW and I would reap the benefits as well.

  58. Is this news?!? I saw it 5 years ago. by Anonymous Coward · · Score: 0

    Everybody knows that CISCO IOS source was stolen about 5 years ago by a Bulgarian hacker called Simeonov at Varna Hacking Group. It was available within hacking communities in Bulgaria but as far as I know was not publicly distributed on IRCs and such. The IOS source code was found to contain large portions of open source code including (gdb and GNU development tools -- you could even fall back to gdb in the IOS if compiled in debug mode.

  59. IOS already obsoleted by Anonymous Coward · · Score: 0
    Cisco's HFR is set for release in 8 days, with a completely re-written OS which obsoletes IOS. This article suggests the existing userbase will need to upgrade anyway.

    Maybe all is not as it seems?

  60. 1 & 4 Redundant by Anonymous Coward · · Score: 0

    I thought showering once a month was the norm in France?

  61. Not actually stolen by aminorex · · Score: 2, Funny

    In fact, the owner was never deprived of the use
    of their putative property. Thus, no code was stolen.

    --
    -I like my women like I like my tea: green-
    1. Re:Not actually stolen by /dev/trash · · Score: 1

      But that code is worthless now.

    2. Re:Not actually stolen by aminorex · · Score: 1

      I don't think the value of the code changed.
      Was anyone offering money for it before?
      Actually, the number of people interested in
      licensing the source may increase, now that they
      can see it -- if it's any good that is.
      Or are you saying that now everyone knows it's
      crap?

      --
      -I like my women like I like my tea: green-
  62. Re:the code that is "shown" as Cisco IOS .... by Anonymous Coward · · Score: 0

    The company I work for prefaces all source files with copyright statements. I never understood the rationale, but I bet it's pretty common practice.

  63. IOS naming by kruczkowski · · Score: 1

    What is more intresting is that the 12.3t was stolen, "t" in the IOS name means "technology", that is where new features are introduced into the code (like the odd kernel numbering), but a lot of companies run the t IOS becouse that is the only place you can get all the features that Cisco advertizes.

    Cisco has a book just on the naming convention of IOS - and the book is pretty thick.

    --
    hmm... for fun I enjoy launching DDoS attacks against 127.87.42.5
    1. Re:IOS naming by Anonymous Coward · · Score: 0

      It is worse than that: with the T series, a new packaging was introduced. Instead of some 50 pre-compiled .config settings, now there are only 8.
      But that still means you have to select from 8 versions, to find one that meets your needs, fits in the available memory, and has good price-requirements ratio.

      A decade ago, the Linux developers had the same problem. Pre-compiled Linux kernels were increasingly difficult to build, because of the ever increasing number of drivers, subsystems and parameters that defined a kernel compile.

      But instead of working around this problem in ever different ways, the "loadable module" concept was introduced. At first there were sceptics, bringing up that this would lead to endless version incompatability problems. But now, it is the widely accepted way of making sure that with one pre-compiled Linux kernel a very wide range of systems and applications can be handled.

      The Cisco people still are sceptics.

  64. Code samples by apankrat · · Score: 1

    Security lab posted first 100 lines of ipv6_discovery_test.c and ipv6_tcp.c. Aside from a somewhat clumsy type names, the code is clean.

    --
    3.243F6A8885A308D313
  65. Size of data may be a clue! by Anonymous Coward · · Score: 1, Insightful

    Just a hunch, but I worked for cisco for five years, and that source code was kept under TIGHT control, on a TIGHT network.

    Does the size relative to the amount of data that can be burned to one CD make anyone else suspect that an insider walked it out on a CD?

    Maybe it was just the most l33t ever...

  66. Stock trading by Anonymous Coward · · Score: 0

    There is at least one business activity that has totally flourished with the internet: stock trading. Even though most equities are still being traded by mutual funds and the like, the amount traded by individuals over the internet is pretty significant. If the internet went down for an extended period of time, don't be surprised to see a direct effect on the stock market and the economy.

  67. Commercialization caused a big stink by nurb432 · · Score: 1

    From what i remember, when the guys formed a company and started selling what was developed in class, it created quite a ruckus.. and they had to pay something back to the school..

    I dont have details handy, but I'm sure its 'out there' somewhere as it wasnt a secret..

    --
    ---- Booth was a patriot ----
  68. News.com are saying Cisco have confirmed it... by Andy+Davies · · Score: 1
  69. Insecure by Donny+Smith · · Score: 1

    I don't know if something like this is possible, but if I had the source code I'd try these
    a) Modify it so that sends private/public keys, passwords and other such info to my site somewhere on the net
    b) Add a backdoor or two

    When timing is right, I'd upload it to a bunch of 2nd hand Cisco switches and resell them at slight loss on eBay.
    Or perhaps work with a disgruntled employee of some networking h/w reseller to get my switch installed at some attractive site such as bank.

  70. Re: Secure? by Xenographic · · Score: 1

    It only affected an old version of IE (IE 5?) and had been patched a very long time ago at the time that exploit was found.

    In any event, it's a pity that this code is pretty much only in the hands of those who do not mean well, rather than in the hands of people who would probably submit patches back to Cisco to help make the Internet more secure...

  71. Know what you are doing? by unity · · Score: 1

    The great thing about open source is that you only work on a project if you know what you are doing

    I think I clearly remember working on many open source projects when I didn't know what I was doing. I was working on open source in order to learn how to do it in fact.

    I would bet there are quite a few people like me out there as well.

    Just a thought; but you do have to enjoy it, that's true.

  72. so what? if anything it'll help by Anonymous Coward · · Score: 0

    saying that leaked IOS source code will hurt anything is silly. do you think cisco has horrible coding standards? do you think anyone actually cares to touch and read and be contaminated by such obviously illegal intellectual property anyways? you who espouse open source as being more scrutinized and secure are complaining about source code being out?

    its an embarrassment for cisco if it happened but nothing at all more serious unless happy-lucky-router-co in china manages to use it to sell their own criscos and kill the asian sales for cisco. fat chance.

  73. Why I Chose Closed Source by Nintendork · · Score: 1
    One common argument is that OS software is inherently more secure because everyone can review it. I'm sorry, but I don't think the number of people reviewing the software, looking for vulnerabilities in an effort to be a good citizen is astronomical. The proof is the fact that new vulnerabilities are announced just as frequently as those for closed source software. Whether it's OS or closed source, the attacker could keep the knowledge for himself and launch a zero day exploit, so the argument about hoarding closed source vulnerabilities applies to OS software as well.

    Obscurity is just one part in a multi-layered defense. Attackers footprint a network and enumerate as much information as possible. The less information they can obtain, the better the defense. What do you think is more likely: Someone finding a security hole with or without the source code? I'll pick the software that's more difficult to analyze and has corporate backing. If someone's trying to target my network, I want to make it as difficult as possible.

    If there were armies trying to capture the data on my network and their success meant my death, I would pick a product designed from the ground up with security as the number one concern. Windows 2003 is a lot closer to that goal than 2000 and XP because it's shipped locked down by default, but it's still built on old code. New vulnerabilities are still being announced regularly. If my life were on the line, I would have to go with SecureBSD. It has a solid record and it's built from the ground up with security as the number one concern. Last I heard, it's only had one vulnerability announced in the last few years. However, if there were a closed source equivalent, I would choose that.

    Luckily, my workplace doesn't require that level of security. I take the most functional, cost effective product (TCO) for our business and harden it manually to a level I feel fits the company. The Windows NT family works great for us.

    -Lucas

    1. Re:Why I Chose Closed Source by Ironica · · Score: 1

      One common argument is that OS software is inherently more secure because everyone can review it. I'm sorry, but I don't think the number of people reviewing the software, looking for vulnerabilities in an effort to be a good citizen is astronomical.

      It doesn't need to be.

      The main point is that, with closed-source software, if the source gets out, the only people who can/will do anything with it are the black hats, because it's not legal to have it. If it's open source, then the good guys can do stuff too.

      If the source stays secret, closed source is more effective. But the problem is that one-way door. If it gets out *just once*, you're completely blown. There's no going back. And *only* the bad guys benefit from it.

      --
      Don't you wish your girlfriend was a geek like me?
    2. Re:Why I Chose Closed Source by MightyYar · · Score: 1
      The proof is the fact that new vulnerabilities are announced just as frequently as those for closed source software.

      You beg the question. It is possible that you are correct and that both closed and open source software have the same number of vulnerabilities. It is also possible that one or the other have far more vulnerabilities, and they are simply finding them at the same rate. In other words, one or the other could be more effective at finding holes. The very fact that you cannot know whether there are more or fewer bugs in closed source software compared to open source software is scary. What is scarier:

      1. Using a base of code that you've had your own guys pour over, yet you also know that everyone in the world can see as well, or
      2. A smiling salesman saying "Trust me!"

      Personally I think the salesman is scarier, but people assess risk in different ways.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  74. Why Couldn't This Happen to DirecTV? by Anonymous Coward · · Score: 0

    I mean, c'mon d00dz! With the source code to their smartcards (complete with comments), just imagine how much more 13373r you could be when you're charging $30/month to program the latest "unhackable" technology :)

  75. Funny new entry on Freshmeat by BeBoxer · · Score: 1

    This just in. routercli-0.1.pre-alpha From the project page:

    "RouterCLI is a cisco-like shell for small or diskless linux distributions. Pre-alpha includes interface configuration, routing manipulation, ping,telnet and trace utilities, I still think about libtecla, access-lists and config."

    I'm sure it's coincidence, but the timing is kinda funny. Actually looks like it might become a useful little tool. And we can tell it's not really based on the leaked Cisco source by the use of fork() :-)

  76. Interoperability is the big thing... by Anonymous Coward · · Score: 0

    Security flaws aside, studying this code would make interoperability with ios much easier for juniper and other router companies.

    As well, looking over the code could give cisco's competitors lots of hints to improve their own products.

  77. it's been confirmed by tero · · Score: 2, Informative

    Not much chance that this will be seen now, but according to CNet Cisco has confirmed that "unspecified amount" of code been leaked. The article is here

  78. Good God!!! by sn0wman3030 · · Score: 1

    Could they choose a smaller font?! /me ctl+scrolls

    --
    Life is offtopic.
  79. This makes it impossible for Cisco to open source by imbezol · · Score: 2, Insightful

    If Cisco were to release the code into open source now it would send a message to the world that anything they're able to steal they can have. They would never open source this code now for that reason.

    Cisco does not want to reward hackers and would be "freedom fighters" for attrosities such as this one.

    I think those of us that support the open source movement need to be very careful about the comments we post after incidents like this. Most of us are hard working respectable geeks that don't go busting into corporate networks to steal proprietary code.

    Let them open source when they want to. Have the conviction and faith that our movement will gain their trust in time. Stealing their code is not going to get us anywhere.

    BigFiber.net

  80. Re:Then it would be Cisco to blame by cbreaker · · Score: 1

    The internet taken down because people found out weaknesses in the sources and exploited them on running routers?

    Isn't this what OSS is so good at preventing? Security through obscurity doesn't work, period. Maybe if they DO find holes and exploit them, it will underscore the need to have more core technologies open sourced.

    --
    - It's not the Macs I hate. It's Digg users. -
  81. Does it matter? by ayf6 · · Score: 1

    So there is the IP issue... but honestly this just gives people and incentive to switch to juniper. GSR's cant even touch a high end Juniper for edge routing...

  82. Don't worry about it ! by skelley · · Score: 1

    from news.com - Cisco apparently thinks this is not a problem at all

  83. Cisco Equipment by tarballedtux · · Score: 1

    I completely agree that once you have some sit time on the console, Cisco equipment isn't that bad. It just gets weird when you start to work on equipment that varies between major IOS versions. Then you have Catalyst OS on High-End equipment that changes everything. Almost as if they program the way Microsoft does. Change everything and change it often. --tarballedtux

  84. Re:the code that is "shown" as Cisco IOS .... by MightyYar · · Score: 1
    We do, too. And our returns get kicked back if we don't update them!

    I always figured that it was just a precaution in case the file got out in the wild.

    --
    W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  85. the next useful internet worm by Dossy · · Score: 1

    Someone please use the IOS source to find an exploit that goes around and updates Cisco routers with proper egress filtering. k, thx! :-)

  86. IOS by Telco-Guy · · Score: 1

    You all act as if Cisco's IOS hasnt been in the open for years.

    -r-------- 1 -- -- 55804111 15 Jan 2002 IOS-11.2-8.tar.gz

    or perhaps

    -rw-r--r-- 1 -- -- 152437 15 Jan 2002 CHANGES.112-7.4-8.1
    drwxr-xr-x 14 -- -- 10240 15 Jan 2002 boot
    drwxr-xr-x 2 -- -- 6144 15 Jan 2002 micro
    drwxr-xr-x 8 -- -- 2048 15 Jan 2002 snmp-em
    drwxr-xr-x 5 -- -- 2048 15 Jan 2002 subsys
    drwxr-xr-x 167 -- -- 26624 15 Jan 2002 sys
    drwxr-xr-x 3 -- -- 2048 15 Jan 2002 wbu

    The src for 11.2 has been around for ever.
    Noted that its some 7 years old but if they lost it once.

    I can find no evidence that any exploits created from back when this came out until now are based on this code so I can only assume that exactly the same events will happen now.
    A few hackers will keep the code as a momento and no one will be bothered looking for bugs. Well no one who has the skills to find them anyhow.

    In 11.2 there are some 258416 lines of code. I expect that in 7 years has become probably 2 million lines. Sure there will be bugs . there has to be. but I still cant see any reason to stress out over it.

  87. Found SCO code in IOS. by rice_burners_suck · · Score: 1
    The code contained the following valuable intellectual property:
    #include <stdio.h>
    Upon learning that SCO's valuable intellectual property above was misappropriated into IOS, Marl DcBride began planning a new lawsuit against Cisco.

    In an interview, the Chief Architecture Officer of the Ministry of Truth, Gill Bates, was quoted as saying, "There are no Americans in Iraq."