Slashdot Mirror


US Military Uses 8-Inch Floppy Disks To Coordinate Nuclear Force Operations (cnbc.com)

An anonymous reader writes from a report via CNBC: A new report reveals the U.S. Defense Department is still using 8-inch floppy disks in a computer system that coordinates the operational functions of the nation's nuclear forces. The Defense Department's 1970s-era IBM Series/1 Computer and long-outdated floppy disks handle functions related to intercontinental ballistic missiles, nuclear bombers and tanker support aircraft, according to the new Governmental Accountability Office report. The report shows how outdated IT systems are being used to handle important functions related to the nation's taxpayers, federal prisoners and military veterans, as well as to the America's nuclear umbrella. "Federal legacy IT systems are becoming increasingly obsolete: Many use outdated software languages and hardware parts that are unsupported," the report found. "Agencies reported using several systems that have components that are, in some cases, at least 50 years old." From the report: "GAO pointed out that aging systems include the Treasury Department's 'individual master file,' which is the authoritative data source for individual taxpayers. It's used to assess taxes and generates refunds. That file 'is written in assembly language code -- a low-level computer code that is difficult to write and maintain -- and operates on an IBM mainframe,' the report said." The report also mentioned that several other departments, such as the departments of Treasury, Commerce, Health and Human Services and the Veterans' Administration, "reported using 1980s and 1990s Microsoft operating systems that stopped being supported by the vendor more than a decade ago."

163 of 267 comments (clear)

  1. Well... by Arkh89 · · Score: 5, Funny

    I hope they don't click the red cross... or we are all fucked...

    1. Re:Well... by um...+Lucas · · Score: 3, Informative

      Click? Red? Surely you jest, I don't think IBM machines from that era had either Mice, GUI's or color displays with which to display red...

    2. Re:Well... by fuzzyfuzzyfungus · · Score: 4, Interesting

      It was all pretty monochrome; but some surprisingly early GUIs existed. SAGE had them(with lightguns rather than mice, since it predated those by a fair bit); among various other flavors of 'it's actually pretty impressive what you can do with vacuum tubes if you have a lot of smart people and nigh-unlimited money' style tech.

    3. Re:Well... by Koen+Lefever · · Score: 2

      Don't forget Digital Research's GEM, Berkeley Softworks' GEOS and VisiCorp's Visi On.

      --
      /. refugees on Usenet: news:comp.misc
    4. Re: Well... by johnsnails · · Score: 1

      They should take advantage of the free upgrade before it expires.

    5. Re:Well... by Megol · · Score: 1

      Those are commonly called TUI (Text User Interface) in comparison of GUI systems. But the difference between them needn't be huge, there are GUIs that look like TUIs and vice versa.

    6. Re:Well... by Anonymous Coward · · Score: 1

      Commonly is not the word you're looking for. I believe never would be more appropriate.

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

      First, it's absurd to believe the article has much detailed information of the true system or it's capabilities. This is highly placed TS deployment and the IBM system being ID'ed is most probably not what you think it is.
      This system was developed when IBM had a dedicated IBM Federal Systems group that was full 810 military compliant. There was no such option as COTS in those days and the components are very likely built to Mil-Std-810 specifications for surviving nuclear radiation/EM, -55 to 150C operation and extreme shock and vibration. You won't be replacing this with an ARM processor, Java and Android. In fact, there was no "Internet" or Ethernet either, only DarpaNet using dedicated and secure connection which it probably still connects with to this day.
      This system is a world away from Cell phone, COTS server or other low MTBF modern tech. many here are familiar with.
      Safe to say that the designers did not design it to play DOOM or even Pac-man. Instead, like the B-52, it was designed to work, never break and provide the highest security.

    8. Re:Well... by xupere · · Score: 1

      I remember my dad having black and white CRT monitors that he'd put tinted plastic transparencies over to make them black-and-green, black-and-orange, etc.

      I'm sure the same principal could be applied to get red ;)

    9. Re:Well... by INT_QRK · · Score: 1

      I used GEOS on my old 8088. Ran on 640KB and a 300MB Hard Drive. Really very nice GUI.

  2. Security through obscurity, that might work... by crypTeX · · Score: 4, Interesting

    We really should applaud them. Imagine how hard it will be to figure out how to write code to hack this.

    1. Re:Security through obscurity, that might work... by Geoffrey.landis · · Score: 4, Funny

      The bad news is that it's not a very secure operating system. The good news is that the hackers are having trouble figuring out how to get the 2600 baud acoustic modems to ARPAnet to download the malware...

      --
      http://www.geoffreylandis.com
    2. Re:Security through obscurity, that might work... by Anonymous Coward · · Score: 1

      You mean 2400 baud modem. "2600" is either the original Atari console, or the hacker magazine.

    3. Re:Security through obscurity, that might work... by U2xhc2hkb3QgU3Vja3M · · Score: 2

      300 baud? Surely you mean 110.

    4. Re:Security through obscurity, that might work... by Anonymous Coward · · Score: 1

      No, 300 baud was in use in the 70s. tty was 110. The main advance in the early 80s from the 70s was the hayes command set (at)

      https://en.wikipedia.org/wiki/Modem#History

    5. Re:Security through obscurity, that might work... by MrKaos · · Score: 2

      With 8 inch floppy disks and a 70s computer, it would have been 300 baud at best. So slow you can hear the characters.

      Only a 300 baud modem is baud and bps exchangeable.

      It probably has an acoustic coupler as well ;) and when they pick up the phone the modem tone says 'Do you want to play a game?'

      --
      My ism, it's full of beliefs.
    6. Re:Security through obscurity, that might work... by SeaFox · · Score: 1

      The good news is that the hackers are having trouble figuring out how to get the 2600 baud acoustic modems to ARPAnet to download the malware...

      You mean 2400 baud modem. "2600" is either the original Atari console, or the hacker magazine.

      Maybe the malware infection will be done acoustically as the parent post said, so to cover their tracks they need to make a lot of pay phone calls to ARPAnet.

    7. Re:Security through obscurity, that might work... by Big+Hairy+Ian · · Score: 1

      Not sure. Would the 237KB storage of an old 8" floppy be too small to accommodate StuxNet?

      --

      Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

    8. Re:Security through obscurity, that might work... by VAXcat · · Score: 1

      2600 referred to the 2600 Hz tone used to take control of a long distance trunk line, used by phone "phreaks" back in the day. The magazine was named after the tone.

      --
      There is no God, and Dirac is his prophet.
    9. Re:Security through obscurity, that might work... by MercTech · · Score: 1

      The acoustic modems maxed out at 300 baud. The ones that had encryption capability came in their own separate 18lb briefcase. 110 baud was the spec for the original telex and teletype terminals. It was considered a wonder in 1974 that you could type on a terminal and it would come out on hundreds of terminals around the world. (Original AP and Reuters method of wire service news dissemination)

      In the 70s; mobile communications was carting a dumb terminal (VT-100s were common) with an acoustic modem. You then dialed in to a mainframe to type things in. Think of having your monitor (an old CRT monitor) and your keyboard connected to your computer over phone lines at 110 baud.

      By the late 70s small computers became actually functional things a business could afford. 8 inch floppies became common. Trust me, training people on Datapoint computers was a pain. And, support was expected to be done by coming to the office not by a phone center. After four instances in one week of people putting their main operating system master disk (A special 8 inch floppy you only used to make a copy of for installing user software to) in a "safe place" by putting it behind the filing cabinet with a refrigerator magnet; I joined the military to get away from customer support.

      By the early 80s, 8 inch floppies (1.2 meg) were the standard for small business computers and 5-1/4 floppies (180K SSDD) were standard for home computers. I actually think that IBM partnered with Microsoft entering the desktop computing market in 1984 set back desktop computing a decade at least. There were much better systems out there before big corporate leverage changed all to IBM-PC standard running a re-branded QDOS. (The original Microsoft Disk Operating System was obtained not by coding but purchasing QDOS "Quick and Dirty Operating System" and re-branding it.)

          Anyway, the PGP running mini mainframes with 8 inch floppies are children of the 1980s. That was when ARPANET was under development and the systems for certain classified things were first being computerized. Upgrading, literally, takes an act of Congress. .. Computer literate old fart here.

      --
      NRRPT/RCT
  3. It's hopeless by realmolo · · Score: 4, Insightful

    This kind of "back-end" software is EXACTLY the kind of thing that contractors DREAM of. Nobody knows how it works, and the general public never has to see it, so they can't complain about it being a piece-of-shit that they paid for.

    It's just like the air traffic control system "upgrade" they've been working on for nearly 30 years. The contractors have ZERO incentive to ever provide a working product. Much better to keep in in development forever.

    I'm not one of those "government can't do anything right" people, but this is one of those things that is just a tailor-made pork-barrel disaster. I see why they don't want to even bother trying.

    1. Re:It's hopeless by holophrastic · · Score: 4, Insightful

      Seems like a good investment to me. Operational for fifty years, and never been hacked. Seems like your government did everything right -- oh how I wish that had continued to be true.

    2. Re:It's hopeless by Anonymous Coward · · Score: 1

      This kind of "back-end" software is EXACTLY the kind of thing that contractors DREAM of.

      But this is the nuclear arsenal, not healthcare.gov. I don't want Accenture going in and replacing it with some Pega piece of crap.

    3. Re:It's hopeless by ShanghaiBill · · Score: 5, Interesting

      The contractors have ZERO incentive to ever provide a working product.

      I have worked on tech projects both as a government employee and as a contractor. Most projects were disasters for the reasons you list, but I have seen a few successes. Here is a quick checklist:

      1. Do NOT use a contractor. They have a vested interest in bloat and delay.
      2. Use your own subordinates so they have skin in the game, and their future raises and promotions depend on the success of the project.
      3. Make sure they are a small team that has worked together successfully in the past on similar projects.
      4. Starve them of resources, so they have no choice but to implement a clean and simple design, with only basic functionality.
      5. Avoid hyping or even announcing the project until you have something working. If you hype it early, you will get demands for every feature, including the kitchen sink, thrown at you, and you will get politically connected contractors forced on you.

    4. Re:It's hopeless by thinkwaitfast · · Score: 1

      They have a vested interest in bloat and delay.

      I haven't seen any of it, at least at the individual level. Where I do see it is management level (cost plus). This is a problem by both buyer (lack of oversight) and the supplier. But what's the alternative, NASA hiring another 20,000 people only to fire them when the latest rocket program gets cancelled? Then try and staff up when it gets refunded?

    5. Re:It's hopeless by Darinbob · · Score: 1

      But it's the way it is because there's no budget to fix it. In corporations they upgrade PCs every one or two year, polish up the foosball tables, then tell the investors that they need more funding. In the government they often are stuck with aging outdated equipment, buildings, etc. Of course, given the price tag charged by contractors treating the government as an ATM it's no wonder they can't upgrade.

    6. Re:It's hopeless by PPH · · Score: 1

      In corporations they upgrade PCs every one or two year,

      Not where I've worked. Things get stuck as-is until management can be convinced that there is a crisis. A few hundred million in funding is secured, consultants are brought in. Nobody can find the old source code, so millions of dollars more are expended trying to reverse engineer the legacy system. Projects go seriously over budget and schedule. But we had a saying: Heads roll uphill.

      --
      Have gnu, will travel.
    7. Re:It's hopeless by Kjella · · Score: 3, Insightful

      1. Do NOT use a contractor. They have a vested interest in bloat and delay.
      2. Use your own subordinates so they have skin in the game, and their future raises and promotions depend on the success of the project.

      1. Depends. Small contractors have often been the ones pushing to cut through the fluff and get real specs and deliverables on the table because they know the budget is fixed, not delivering makes them look bad and if they don't it'll just fizzle like so many projects we have that are ongoing but never really materialize. "Too big to fail" projects that'll be funded next year too unless hell freezes over are different, but then you're often screwed because you really don't have the skills or resources in-house. In fact big projects almost always fail because of the next one.
      2. For the most part, that simply can't happen. There's no authority to make incentive or performance-based pay, I have my pay grade and overtime pay. As for raises, if I were to get any significantly more pay than anyone with less education, experience and tenure it'd raise hell with unions and whatnot. And it's often the same with promotions, you'll get promoted when it's your turn because if they pass up a candidate that's better on paper there's actually a formal complaint process. Same with public procurement processes, nobody's free to do what they feel is best for the bottom line.

      As for 3-5. they're generally good ideas. If you give people too much time and money to try solving every problem forever, they'll sit around making grand plans and often dismissing the reasons why the current system has become such a mess as bad design, when in reality it's a messy world out there and kludges are our way to cope.

      5. Avoid (...) even announcing the project until you have something working.

      Sadly I've found this is the easiest way to get something done, particularly if it's the type of solution that's not great but less terrible than the one we have. They say learn to walk before you run, but nobody here seems to have heard it. Every time there's a project to get on our feet, somebody must come in and crush it because it's not good enough. Which usually means we're crawling around for a few more years while they argue about their master plan to simultaneously win the 100m dash and the marathon at the Olympics.

      I'm so tired of pie-in-the-sky plans that end up a mad dash to deliver the barest minimum because somebody finally put the foot down, basically throwing away 90% of the work because there was no time to even try implementing anything remotely like it. There should be like a shot clock, if you've spent 30% of your budget start implementing and figure out where the rubber meets the road. Anything else leads to meaningless exercises like trying to estimate a solution where we haven't even decided on the principle for the solution, much less made an actual design and broken it down into work that needs doing and could reasonably be estimated.

      --
      Live today, because you never know what tomorrow brings
    8. Re: It's hopeless by Salgak1 · · Score: 1

      And of course, the crony set-asides, excuse me, "Disadvantaged/Woman Owned/Minority Owned" businesses.

      Which always seem to be owned by the wife of a VP, or the new "owner" WAS a VP of a big contractor, but suddenly, **magical ownership** and now there are parts of contacts specifically set aside for them . . .

      I've worked both sides of the Feds, and I've seen this dodge WAAAAAAAAY too often. . .

    9. Re:It's hopeless by canistel · · Score: 1

      4. Starve them of resources, so they have no choice but to implement a clean and simple design, with only basic functionality.

      Yeah. I'd love to work for you, where do I sign up?

    10. Re:It's hopeless by gtall · · Score: 1

      Sounds more like private industry cannot do anything right. Admittedly, the U.S. Gov. isn't holding the gun to their head properly. Given all the rules and regulations, it is more the case of they have to hold the gun properly and in a non-threatening manner with the bullets kept by a different agency than that holding the gun.

    11. Re:It's hopeless by luis_a_espinal · · Score: 1

      The contractors have ZERO incentive to ever provide a working product.

      I have worked on tech projects both as a government employee and as a contractor. Most projects were disasters for the reasons you list, but I have seen a few successes. Here is a quick checklist:

      1. Do NOT use a contractor. They have a vested interest in bloat and delay. 2. Use your own subordinates so they have skin in the game, and their future raises and promotions depend on the success of the project. 3. Make sure they are a small team that has worked together successfully in the past on similar projects. 4. Starve them of resources, so they have no choice but to implement a clean and simple design, with only basic functionality. 5. Avoid hyping or even announcing the project until you have something working. If you hype it early, you will get demands for every feature, including the kitchen sink, thrown at you, and you will get politically connected contractors forced on you.

      #4 is idiotic, and #1 is plain generalization bullshit. I worked with government contracts also, and employees are not above bloat, delays and vested interests. Most of the bloating and delays occur because of management bloat and red tape that inevitably arises when dealing with the government (yes, acquisition processes used by the government promotes bloat.)

      It is rank-n-file employees and contractors that have to deal with that shit. Certainly there are some who use that to their advantage ($$$), but the majority are trying to do a good job, or at least keep their heads up and not cut their wrists when dealing with a tidal wave of shit that comes inevitably with government contracts.

      There is plenty of moral hazard blame to throw around. Don't be disingenuous trying to peg it all on contractors.

    12. Re:It's hopeless by F.Ultra · · Score: 2

      Yes, imagine the horror when they "upgrade" to new and shiny. At least it will web scale or something.

  4. So What? by plopez · · Score: 5, Insightful

    They've been stable for decades. I'll take master files on floppy disks and programs written by people who cared over "eventually consistent" databases developed by "just good enough" monkeys any day.

    --
    putting the 'B' in LGBTQ+
    1. Re:So What? by nuckfuts · · Score: 4, Insightful

      Yes and no. I would not advocate changing operating systems simply because they "stopped being supported by the vendor more than a decade ago". After all, if your needs have been met for decades by something like MS-DOS 6.1 or Windows 3.11, what "support" would you looking for from Microsoft today?

      Physical devices are a completely different issue, however. Floppy drives and floppy disks WILL wear out and fail. Maybe these agencies have a stockpile of spares, or maybe someone is still manufacturing 8" floppies to sell to the government for an arm and a leg, but barring that, good luck sourcing replacements for your antique computer hardware when it fails.

    2. Re:So What? by kylemonger · · Score: 1

      Well, there's the possibility of sudden catastrophic failure of the hardware, for which there may be no spare parts anymore. I hope someone is exploring the virtualization angle; any fifty year-old piece of hardware could be emulated in software running on $200 phone today. So migrating off the creaky hardware need not involve disinterring all that assembly language and exposing it to "agile" development.

    3. Re:So What? by Anonymous Coward · · Score: 3, Informative

      I work on similar systems, and while we don't have stuff quite that old, the US Military absolutely knows about the obsolescence, yes those floppy drive and floppy disks do wear out. However they knew that when they built the system, when they bought the drives back then they went out and bought a 50 year supply of drives and floppies. And today the still repair the systems, and the logistics guys know roughly when they will run out of parts, and they will replace those bits when they need to. With those old systems it's very much a plan of fix and replace only what needs to be fixed and replaced, they know the failure rates and the specs don't change.

    4. Re:So What? by Dadoo · · Score: 1

      Physical devices are a completely different issue, however. Floppy drives and floppy disks WILL wear out and fail.

      If you have enough money, you can pay someone to build you an 8" floppy drive, from scratch.

      --
      Sit, Ubuntu, sit. Good dog.
    5. Re:So What? by Nethead · · Score: 1

      I actually have about 100 old 8" floppies and two drives sitting out in the shed. Now that I've typed that on the Internet, the government knows where to find them. I'll just reset the combo lock to 8008 for them.

      --
      -- I have a private email server in my basement.
    6. Re:So What? by nmb3000 · · Score: 1

      If you have enough money, you can pay someone to build you an 8" floppy drive, from scratch.

      Must you first invent the universe?

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
    7. Re:So What? by angel'o'sphere · · Score: 1

      If you knew what an "eventual consistant" database is, you would not rant like that.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    8. Re:So What? by plopez · · Score: 1

      It means corrupted inconsistent "good enough" data. I've had plenty of that over the years.

      --
      putting the 'B' in LGBTQ+
    9. Re:So What? by R3d+M3rcury · · Score: 1

      They also seem to be on the ball, and are probably looking at replacing the mechanical floppy drives with a micro controller and an SD card.

      For some reason, this makes me think of that scene in Captain America: The Winter Soldier where Black Widow plugs in a USB drive into the giant mainframe computer...

      Oddly, I can't find a clip of it on-line.

    10. Re:So What? by Lehk228 · · Score: 1

      their techs have been repairing those drives for 50 years, odds are most of them could build one from a rack of components.

      --
      Snowden and Manning are heroes.
    11. Re:So What? by Imrik · · Score: 1

      Honestly, in the event of an all out nuclear war I'm kind of ok with them not working.

      I have two main criteria for a nuclear missile system:
      1. must be convincing enough for foreign governments to believe it will work, which would generally mean the people using it have to believe it will work
      2. must not launch without proper authorization

      Actually launching with proper authorization is optional.

    12. Re:So What? by Imrik · · Score: 1

      You switch out the bad drive or take parts from a drive that failed in a different way.

    13. Re:So What? by MrKaos · · Score: 1

      I'll just reset the combo lock to 8008 for them.

      bu dum *tish* - nice one!

      --
      My ism, it's full of beliefs.
    14. Re:So What? by serviscope_minor · · Score: 1

      their techs have been repairing those drives for 50 years, odds are most of them could build one from a rack of components.

      Indeed. Send those techs to the pub with a couple of decent engineers for a few evenings, and you'd have a brand new design that could easily be built today with modern components.

      --
      SJW n. One who posts facts.
    15. Re:So What? by Big+Hairy+Ian · · Score: 1

      Bearing in mind they are using 8" floppy's surely the computers they are interfacing to are probably based on Mag Tapes.

      --

      Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

    16. Re:So What? by ACE209 · · Score: 1

      That's only needed for apple pie, I think.

      --
      "we are all atheists about most of the gods that societies have ever believed in. Some of us just go one god further."
    17. Re:So What? by iggymanz · · Score: 1

      there are devices that take the mainframe coax-carried protocols and convert to parallel and usb printing ports. Of course, plugging in anything but a printer won't get one much.

    18. Re:So What? by angel'o'sphere · · Score: 1

      No it does not.
      Try again.

      Even in an "eventually consistent" database all requests deliver an in it self consistent result. Corruption is impossible.

      If you noticed corruption you likely have problems on another level.

      I'm still pretty sure you don't know what the term means ...

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  5. WOPR? by TigerPlish · · Score: 1

    I know it was fictional, but I just can't get WOPR out of my mind when reading this.

    --
    The "Civilized World" jumped the shark ca. 1973.
    1. Re:WOPR? by bobbied · · Score: 2

      WOPR or really the idea behind it is EXACTLY why we use 1950's technology still in our nuclear silos.

      Think about it. If you own an operational nuclear tipped missile, your primary concern is that it is only going to detonate when and where YOU want it too. Also figure that you realize that this thing is going to be sitting for decades, hopefully with a minimum of mess and fuss over things like maintenance and refurbishment. It may sit there for multiple decades, but it HAS to work when you push the button under adverse operating conditions. This means you need a really robust system that's easy to take care of.

      ALL of these requirements mean you will choose the most simple design that fulfills your needs. The one with the least parts, especially those parts that move, and once you have a proven design, you are going to be loathed to change it just because it's out dated. Once it works and proven there will be NO changes without some seriously good reasons. Newer is not always better. You don't mess with a design that works, just because it's old.

      Couple this with the fact that the government is where the obsolete is always in style and it's never simple (nor cheap) to change anything and you can see why stuff like this takes on a life of its own. Why change it? It works and we don't need anything else that's better.

      One more thing that comes to mind.. Nuclear weapon development is subject to international treaty oblations. I don't pretend to know all the details, but I'm fairly sure that we cannot just go out and replace our current crop of nuclear missiles w/o having issues with some treaties.... Not that Putin could do much about it if we unilaterally decided to do something, but he'd sure be crying foul and loudly if we did.. Not to mention the political fall out from that...

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    2. Re:WOPR? by Imrik · · Score: 1

      Rather than only detonating when and where I want it to, my primary concern is that it not detonate any other time and place, detonating at the correct time and place is just a bonus.

    3. Re:WOPR? by DarkOx · · Score: 1

      I mostly agree with you but the simplest design is NOT always the most robust. For example nobody would argue that points and a distributor are not simpler than todays electronic ignition systems on cars. Similarly nobody would argue that electronic ignition control isn't more robust and far simpler to maintain.

      Sometimes new technology and with it increased complexity does result in a more robust system.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    4. Re:WOPR? by bobbied · · Score: 1

      Generally the reduction of moving parts is a good thing and the distributor points/condenser ignition system has a number of moving parts. So in cases where you are removing mechanical assemblies and putting in parts that don't move, it's a good thing. For instance, our fleet of Nuclear missiles have had their original mechanical gyros replaced with laser ring versions, which are more reliable because they don't have moving parts.

      However, electronic ignition systems are necessary for reasons other than being robust. They are required to meet emissions standards and where developed for that purpose, not because they where more reliable. Actually, they initially where not all that reliable as memory serves. They became so because the CAFE standards started to push minimum warranty periods on emission controls, making it cost effective for manufacturers to design robust systems because the government mandated that such systems had to work for a minimum number of miles and years.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
  6. Perhaps Slashdot uses similar technology.. by forty-2 · · Score: 1

    ..Which is why they didn't notice the dupe from a month ago.
    https://tech.slashdot.org/stor...

    --
    never drink kool-aid from a big vat
    1. Re:Perhaps Slashdot uses similar technology.. by BeerCat · · Score: 1

      ..Which is why they didn't notice the dupe from a month ago.
      https://tech.slashdot.org/stor...

      Or 2 years ago, even.

      FTFURL: ...slashdot.org/story/14/04/29... means it was 29 April 2014

      --
      "She's furniture with a pulse"
    2. Re:Perhaps Slashdot uses similar technology.. by qubezz · · Score: 1

      And they also can't help but repost the obvious clickbait headline that is not news and really has nothing to do with what is being reported on, which is the general account office released the report that details IT spending in the government, and their view of a lack of oversight of expenses, which has transitioned into support costs instead of paying for new systems:

      In the report being released today, GAO is making multiple recommendations, one of which is for OMB to finalize draft guidance to identify and prioritize legacy IT needing to be modernized or replaced. In the report, GAO is also recommending that selected agencies address obsolete legacy IT O&M investments. Nine agencies agreed with GAOâ(TM)s recommendations, two partially agreed, and two stated they had no comment. The two agencies that partially agreed, the Departments of Defense and Energy, outlined plans that were consistent with the intent of GAOâ(TM)s recommendations.

  7. So if... by dfsmith · · Score: 5, Funny

    If I notice a quantity of 8" floppies dropped around a parking lot next to an inconspicuous government building, can I assume that some sort of Stuxnet cyber attack is under way?

  8. New Procurement by Geste · · Score: 1

    Obviously, they urgently need to start a new procurement cycle. Then things can get royally screwed up

    1. Re:New Procurement by bluefoxlucid · · Score: 1

      Yeah, we should rewrite everything!

      I actually wouldn't mind being PM on a modernization job like that. It's the sort of high-complexity, high-risk program that got me into project management in the first place: so many things can go wrong, from bad requirements gathering to bad delivery, and predicting and controlling all those risks is an amazing challenge.

    2. Re:New Procurement by fuzzyfuzzyfungus · · Score: 1

      The tricky bit is whether anyone bidding for such a job would want the project managed as competently as possible, or whether it's one of those situations where having a risibly old(but functional enough that disasters aren't drawing attention to the slipping deadlines of the replacement) legacy system makes meandering in the vague direction of a solution for as long as you can as good or better than actually delivering.

      If something like the 'CityTime' payroll system upgrade project can go as excitingly wrong as it did; I'd hate to see what a project of this magnitude would do.

    3. Re:New Procurement by bluefoxlucid · · Score: 1

      Of course they'd want it managed as competently as possible. They have to bid low against competition, and every unpredicted and uncontrolled risk cuts into their profits on that. Failure to deliver on-budget bans you from government contracts with the agency for several years. Besides that, the agency awards a fixed-fee-plus-awards or time-plus-awards contract for this sort of work, meaning finishing at higher quality and less time generates a higher per-hour billable than stretching the work, and thus you can move on to the next project at higher per-hour billables if you can keep being awesome.

  9. More like by fred911 · · Score: 4, Interesting

    Security through obsolescence.

    --
    09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    1. Re:More like by bancho · · Score: 3, Funny

      More like: Security through Antiquity :)

    2. Re:More like by NatasRevol · · Score: 1

      So we need an electronic rosetta stone?

      --
      There are two types of people in the world: Those who crave closure
    3. Re:More like by Fishchip · · Score: 1

      Terminology is everything.

    4. Re:More like by angel'o'sphere · · Score: 1

      I doubt anyone gets your mangled quote.
      Kudos!

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    5. Re:More like by pslytely+psycho · · Score: 2

      The Rosetta Stone in this case is likely a 10" thick set of punch-cards....

      --
      Donald Trump, on a crusade to make Nixon look respectable
    6. Re:More like by Rob+Y. · · Score: 1

      Okay, this is gonna sound crazy, but the system I worked on originated on the IBM Series/1 - and was written in assembler. In order to outlive the Series/1, we wrote an interpreter for S/1 machine code, and built a unix system that supported running new native unix apps as well as legacy Series/1 code seamlessly from the same front-end. Unbelievably, although most of the code nowadays is several generations down the native unix branch, there is still some legacy S/1 assembler code used on a daily basis. Sometimes it's just downright hard to kill this stuff...

      --
      Posted from my Android phone. Oh, I can change this? There, that's better...
  10. To what extent is this actually bad? by fuzzyfuzzyfungus · · Score: 3

    I'd be curious to know how many of these seriously outdated systems are egregious piles of failure; and how many are utterly contrary to any fad of the week from the last three decades; but where done right the first time and actually compare pretty favorably to the results of (the so often horribly doomed) 'upgrade' efforts.

    Some flavors of outdated are fairly clearly bad; if you can't get replacement hardware without raiding a museum or reverse engineering and cloning/emulating quirky 80s gear all by yourself, keeping your systems running is going to be unpleasant and expensive. If you have a system whose security depends on an OS or other 3rd party components that have exciting known vulnerabilities and haven't had vendor support even under a thrillingly expensive special extended contract with the vendor in a decade, you have a problem.

    If you have a legacy system that is merely retro; but well built and supported by hardware you can still get without much trouble, you will certainly get your share of snide comments about its dreadfully antique design; but you are taking a real risk in trying to modernize it. Those sorts of 'upgrades' don't always fail; but agonizing, wildly expensive, upgrade attempts that languish in development so long that the upgrade is obsolete before you've finished deploying it are hardly uncommon.

    Sure, in an ideal world, we'd all get to implement from scratch with all the benefits of hindsight and absolutely no accrued technical debt; but we don't live in an ideal world. How many of these systems are old as in broken; and how many are old as in classic?

    1. Re:To what extent is this actually bad? by dadelbunts · · Score: 1

      I would argue its even better if it works properly. What are the chances an attacker would know to target, or would even have the ability to target such an old system.

    2. Re:To what extent is this actually bad? by fuzzyfuzzyfungus · · Score: 2

      I wouldn't necessarily take refuge in obscurity if running something important; a core IRS system or nuclear-related control systems would be the sort of targets where you'll get some fairly motivated attackers rather than just kiddies looking for soft targets. That said, it's not necessarily the case that old=insecure in a situation where you aren't dealing with software thrown together as fast as possible to secure a first mover advantage or win a feature race with competitors.

      There have been a lot of advances over the years in the average state of low cost hardware and software, and in attempting to mitigate the results of running a hodgepodge of untrusted and mostly crap software exposed to a constant stream of hostile input from the internet; but that newer-is-mostly-less-awful trend is really most notable in the cheap seats, not in comparatively simple(if only because the hardware wasn't available for anything bigger) and very expensive systems built for justifiably paranoid customers.

      I suspect that some of the now outdated 'COTS' based systems are truly horrifying: new and common enough that plenty of known vulnerabilities exist, old and dysfunctional enough that they probably aren't getting fixed; but the more unusual evolutionary dead ends, while not cheap to support, have at least a chance of being extremely good at what they do.

    3. Re:To what extent is this actually bad? by tnk1 · · Score: 1

      They were probably *all* piles of failure at one point. The nice thing about having 40-50 years to work on something is that eventually you don't just fix a few bugs, you've probably re-written the whole thing about three times over with all that patches that went into it. And that's just the first twenty years *before* it was shoved into "evergreen" neglect mode for the following twenty years.

    4. Re:To what extent is this actually bad? by SvnLyrBrto · · Score: 2

      Retro becomes a problem because it becomes excessively expensive, or even impossible, to maintain.

      Consider just those 8" floppy disks. For starters, they're not exactly durable. And barring clumsiness, the oxide coating used for data storage continues to oxidize over time since they're not airtight. So every one of them is slowly going bad and needs to be periodically replaced. Vintage disks in a warehouse would also be exposed to oxygen and slowly going bad. So somewhere there's a production line running, still turning out 8" floppy drives. There's a certain minimum cost to keep any production line running. And how many customers besides the DoD do you suppose that vendor has? So those are some epically expensive 8" floppy disks.

      The production line to make those 8" floppies needs maintenance and, critically, spare parts when something breaks. These are unlikely to be industry-standard machine parts... how many 8" floppy fabs still exist? So any replacement parts to the production line would need to be a custom job from a machine shop, at obscene pricing. (Skilled machinists are becoming more and more rare in the US and custom work demands a large premium.) And since the Air Force probably doesn't a steady supply of these floppies, and there are unlikely to be many, if any, other buyers, the production line probably starts and stops every so often to produce batches around replacement time. Starting or stopping a production line is a large expensive process itself; sometimes more expensive even than leaving it running at low volume for extended times. And what happens if, at the next contract renewal, the vendor decides it just doesn't want to be in the 8" floppy business anymore? What happens if the vendor goes out of business

      And that's just one component of the "retro but still functional" design. Pretty much any and every replacement part is likely to be a custom job at this point. And, for obvious reasons, that production isn't something you can just job out to China.

      --
      Imagine all the people...
    5. Re:To what extent is this actually bad? by newcastlejon · · Score: 1

      Sounds vaguely like Clavain from Redemption Ark.

      --
      If God forks the Universe every time you roll a die, he'd better have a damned good memory.
    6. Re:To what extent is this actually bad? by sd4f · · Score: 1

      You wouldn't really need to maintain the entire production line. In this case, I would presume that the demand for the disks would be low, so you'd look at different production techniques which are going to be more labour intensive, but much more cost effective for low production volumes. After all, in a floppy disk, there's very few parts, most of which are incredibly simple to manufacture, and can be done in more ways than one. For instance, you wouldn't need the same machine that made jackets all those years ago, as that could easily be done on a small 2D CNC machine.

    7. Re:To what extent is this actually bad? by serviscope_minor · · Score: 1

      For instance, you wouldn't need the same machine that made jackets all those years ago, as that could easily be done on a small 2D CNC machine.

      The world runs on small plastic bits o' crap. There's manufacturing facilities from all levels of scale from near one off injection moulds to manufacture by the billion in a wide variety of ways. My guess would be for the jackets, you can find some low volume manufacturer, they'll CNC the moulds and can then run off batches of 1000 every few years or so as you need them.

      --
      SJW n. One who posts facts.
    8. Re:To what extent is this actually bad? by serviscope_minor · · Score: 1

      So those are some epically expensive 8" floppy disks.

      Yes, but probably still cheaper than the alternative. One of the usual suspects (big contractors) is easily capable of burning through 10 billion building a "replacement" which is eventually scrapped because it doesn't work. You can buy a lot of epically expensive floppy disks for that price. Heck, you could buy and staff the factory 1000 times over probably for that price.

      --
      SJW n. One who posts facts.
    9. Re:To what extent is this actually bad? by evilviper · · Score: 1

      Retro may be a bit more costly, but you're ignoring the astronomical cost of upgrading big systems like these. We're not talking about someone's desktop PC being overdue for an upgrade.

      Estimates are that "it would cost $352 billion over the next decade to modernize the facilities." Obviously you can keep 8" floppies in production for FAR, FAR less than that! What's more, even if you spent the hundreds of billions of dollars to upgrade the systems, you're ONLY moving the baseline forward a bit, not PERMANENTLY solving the problem.

        In other words, whatever media they upgrade to (e.g. CD-R, SD card, etc.), is likely to be obsolete and unavailable in a decade or so, as well. Whatever systems they certify for use, will be hard to find in just a few years. This is a problem, in general, for any life-critical system that needs to be end-to-end certified... You can't just swap in a newer system that should be compatible, you have to exhaustively test every edge case works EXACTLY like the old one did.

      The only problem is one of perception... If the system was built of custom circuit boards, with lots of transistors and Z80 or 6509s, nobody would bat an eyelash that it was expensive to maintain, custom replacement parts needed to be ordered, and nobody would expect drop-in upgrades. But since it involves non-embedded computers, and accessories familiar to home PC users, there's a knee-jerk negative perception around all of the above, even if it's much cheaper and more reliable than the alternatives, because people can't perceive just how different the industrial needs are than their home usage pattern.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    10. Re:To what extent is this actually bad? by fuzzyfuzzyfungus · · Score: 1

      I'd imagine that the big variable on 8-in floppy cost is whether or not any modern use requires a magnetic medium of coercivity close enough to be compatible: the actually-floppy floppies are pretty simple on the inside, just a casing made of die-cut plastic sheet, some anti-dust pads on the inside, and the 'donut' of magnetic medium. If you have to commission bespoke magnetic medium because all the modern stuff is too high coercivity to suit high density magnetic recording, that could get unpleasant. If there is some user of magnetic film of appropriate coercivity, getting appropriately shaped pieces of it punched out of sheetstock shouldn't be too difficult.

      Even if (and it wouldn't be too surprising) the floppies or their drives are ultimately impractical to keep running, it still might be easier and less risky to build a floppy drive emulator that speaks the appropriate protocol but uses some more modern storage mechanism. That's an entire cottage industry in hobby retrocomputing, allowing you to replace scarce oddball HDDs and weirdo floppies with CF or SD cards; and given the relative simplicity of historical floppy drive interfaces I would strongly suspect that you could get an all-American engineering team to cook up a drop-in replacement without too much trouble.

      That said, hardware is certainly the area where obsolescence is likely to become a real logistical problem first; so any attempts at modernization(incremental or wholesale forklift-replacement) should be aimed at trying to decouple the system from specific hardware as much as possible(the 'baseline' hardware profiles used by virtualization systems to accommodate guest OSes that aren't virtualization aware and capable of playing nice with virtualized devices, say, are already obsolete hardware; but will probably be just as available decades from now as they are today); but even where hardware is involved, the difficulty of replacing the system as a whole makes trying to incrementally replace the hardware(with well defined compartmentalization at various interfaces to make the future replacement of your replacements easier) a viable consideration.

    11. Re:To what extent is this actually bad? by dadelbunts · · Score: 1

      Depends on the system. Id much rather take an older system with no USB ports, no way to even get on the internet even if it had the proper ports, and some antiquated OS. While it may not stop an attacker, it will certainly make life harder for them.

    12. Re:To what extent is this actually bad? by F.Ultra · · Score: 1

      However the storage density of these old disks are probably so low that they can still work with a lot of rust :)

  11. Security by Obscurity by The+New+Guy+2.0 · · Score: 2

    The government doesn't want anything in general release in these situations. A large old floppy isn't readable or writable by the average Windows computer. This creates "security by obscurity" that makes it harder for a non-authorized command to be run. We don't want some kid playing Thermo-Nuclear War.

  12. Only if you are narrow minded by s.petry · · Score: 2

    The military using special technology is a good thing from a security perspective. It is not supposed to run on Commodity hardware and software, because if anyone can work on it everyone potentially has access.

    Stop playing the narrow minded "cheap is good" game and consider other reasoning. Longevity is a good thing, not a bad thing. Specialized knowledge in security is a good thing, not a bad thing. It's only government waste because you are only considering a very minor aspect.

    By the way, if they were using "new tech" it would not last for half a damn century. It would have been stuffed in the trash every couple years, like we do with the majority of our servers today who have an average lifespan of less than a year before the first malfunction causing a hard stop.

    --

    -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    1. Re:Only if you are narrow minded by tnk1 · · Score: 1

      Yes, that's great until you start running out of living humans with the ability to actually operate that stuff. I'm not saying I dislike quality or custom gear for the military, but support and logistics is a real thing.

      And unlike the wishful thinking about aliens and black ops the real reason we have $20,000 toilet seats is because the government can't just use something that everyone else does. And half the time, the reason isn't even something as intelligent as security or reliability, it's because someone wrote some dumb-ass regulation that everyone has forgotten why it existed in the first place but its chiseled right there in that stone tablet that everyone has to abide by or they get thrown in jail.

      The fact that it just happens to be more secure was more of an accident than anything else. That's a shaky premise for good security. If you could find someone with enough motivation to learn how, it would be trivial to break this stuff.

    2. Re:Only if you are narrow minded by s.petry · · Score: 1

      Ask Iran how well that "we should be using commodity" rule you want to impose worked for them. Oh, wow! Never thought about that did you? Yeah buddy, we want to be just like them right? (That was sarcasm).

      And then you go out to fantasy island for your next point. How about the reason commodity items are overpriced is due to corruption? When we catch it we fix it? Hmm, what a novel thing to consider.. (more sarcasm, but well deserved) Then we consider that some things are better served as commodities, like desks and toilet seats while others are better off as independent systems. Like Military stuff we don't want to share.

      If the Government uses 1970s tech they can train new people to support it. Just like they have done for nearly 50 years. It's not like when Joe retires he takes all of his worldly knowledge with him. Good grief, it that were true then long ago someone died and that explains why nobody can ever balance a checkbook again!

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    3. Re:Only if you are narrow minded by tnk1 · · Score: 2

      Your sarcasm is misplaced and missing the point. Nowhere did I suggest that a commodity rule was required for this. There is a middle ground.

      As for independent systems, you know that the military uses things like Windows, right? On warships. And for passing classified messages. It's not Windows 10, but it's not like we have to handcraft our operating systems.

      You think that the code written in assembler stored on 8-inch floppies makes something secure? You'll be lucky if there is any security features on it at all. The reason it is secure isn't that it is secured by obscurity, it's because it is secured behind (mostly physical) measures that work to protect the entire US nuclear weapons control system. If Iran guarded their air-gapped Windows based control systems for their centrifuges as well as we guard our nuclear weapons, we wouldn't have been able to get a USB drive or 3.5 inch floppy into their machines either.

      If the Government uses 1970s tech they can train new people to support it. Just like they have done for nearly 50 years. It's not like when Joe retires he takes all of his worldly knowledge with him. Good grief, it that were true then long ago someone died and that explains why nobody can ever balance a checkbook again!

      Actually... balancing a checkbook may be on its way out in a generation or two. Who actually uses one any more? But aside from that, I should point out that the difference between nuclear weapons control systems and balancing checkbooks is that the skill set behind checkbooks is simple math and it used to have universal adoption, the other not so much. And humans certainly can lose skills through the passage of time and neglect if it isn't something with a ready source of reinforcement.

      More to the point, I'm less concerned about those operating these systems, as they were built to be run by 18 year olds. I'm more concerned with what happens when they break, or we actually need a new *feature*.

      You assume we can train someone because we seem to have before, but that's a huge assumption. Where are the schools that are teaching this? Sure, the Air Force can teach operators, but this is written in Assembler. Here's what the report actually said:

      " For example, one agency (SSA) reported re-hiring retired employees to maintain its COBOL systems."

      COBOL was a widely used language at one point. No one is learning it now. One guy I know who has used it went to a job fair and no one at it who knew COBOL was under 50 years old. Do you think that someone who knows how to code for the specialized hardware for the nuclear control systems is going to be even that easy to find?

      They're not re-training... they're using the already trained people until they die. There are no replacements.

      The answer is actually going to be that when it does break or a new feature needs to be had, they won't find these people to train. They will spend time and effort of building it from scratch all over again. In a new language. With parts that have actually been in a full production run in the last decade. And they fail, fail, fail until they get it right again, and the government promptly neglects it for another 40 years. And the failure only builds up every year that they hold out.

      So, sure, don't install the latest version of Windows or buy your components off Amazon, but there has to be a better way than what they're doing.

    4. Re:Only if you are narrow minded by LWATCDR · · Score: 1

      "Yes, that's great until you start running out of living humans with the ability to actually operate that stuff."
      Actually the US government is pretty good at keeping old tech alive.
      The B-52 for example. The last model is the H and it was last built in 1962 and is still in use. Sure some of the avionics have been updated but the tf-30 engines are the same.
      KC-135 tanker is still in service and is just as old or older.
      The USS-Enterprise that just retired a few years ago was finished in 1962.
      The military used to be great about documenting everything. You can get a complete set of blueprints for the P-51 Mustang if you want.
      Also computers where different back then as well. The where completely documented and computers where made out of parts. Even if they used ICs the ICs where usually parts that you assembled into a computer unlike today where the ICs are the computer.
      If you read the article it is the typical let's scare people. For example they are complaining that the backend systems for the VA and SSA are both written in COBOL... Yes so? Code doesn't stop working.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    5. Re:Only if you are narrow minded by luis_a_espinal · · Score: 1

      Yes, that's great until you start running out of living humans with the ability to actually operate that stuff. I'm not saying I dislike quality or custom gear for the military, but support and logistics is a real thing.

      And unlike the wishful thinking about aliens and black ops the real reason we have $20,000 toilet seats is because the government can't just use something that everyone else does. And half the time, the reason isn't even something as intelligent as security or reliability, it's because someone wrote some dumb-ass regulation that everyone has forgotten why it existed in the first place but its chiseled right there in that stone tablet that everyone has to abide by or they get thrown in jail.

      The fact that it just happens to be more secure was more of an accident than anything else. That's a shaky premise for good security. If you could find someone with enough motivation to learn how, it would be trivial to break this stuff.

      There is something called training.

    6. Re:Only if you are narrow minded by Pentium100 · · Score: 1

      If Iran guarded their air-gapped Windows based control systems for their centrifuges as well as we guard our nuclear weapons, we wouldn't have been able to get a USB drive or 3.5 inch floppy into their machines either.

      I think that there is one difference though. USB drives are easier to hide and common, so the operators may decide to plug their own drive (or one they found on the ground in the parking lot) in their work computer.

      While somebody could do the same with an 8" floppy, it is less likely for two reasons. One, a floppy disk in the parking lot is much more suspicious than a USB drive (since people usually do not carry floppies for personal use anymore). Two, the operators are less likely to have 8" floppy drives at home, so they cannot unknowingly bring an infected disk with them (with music or some Word document they wanted to edit on their work PC).

  13. But can it play tic-tac-toe? by DidgetMaster · · Score: 1

    Obligatory War Games reference.

  14. It's all about the money by fredgiblet · · Score: 1

    The systems were designed in the 70s and have had minimal upgrades since then. Honestly I'm not even convinced we could actually prosecute a complete nuclear war at this point. The other problem is that designing a new system would cost tens of billions of dollars due to the inevitable cost overruns and waste from the Military-Industrial Complex.

    We should produce upgraded command and control systems, but we should also have fixed price contracts to keep things in line.

  15. 8 inche floppies worked pretty well by tomhath · · Score: 1

    My daughter found a very dusty 8 inch floppy that must've been at least twelve years old. It had a game on it that I'd bought as shareware in the early days of the Internet. She found an old floppy drive in my spare parts bucket and hooked it up - the game actually worked and was a pretty good RPG for it's day (it was called Lumpies of Lotus), so she wrote a review of the game in an online forum and received an nice "Thank You" from the author.

    So there's a chance that the guys watching over the US nuclear arsenal are sitting there playing Lumpies while they wait for the pre-emptive strike.

    1. Re:8 inche floppies worked pretty well by tarpitcod · · Score: 1

      Was it really an 8 inch floppy on an Atari 8 bit? That sounds like you must have had a sweet ATR 8000 attached...

    2. Re:8 inche floppies worked pretty well by tomhath · · Score: 1

      Nah. It was a Basic program running on DOS

    3. Re:8 inche floppies worked pretty well by serviscope_minor · · Score: 1

      Nah. It was a Basic program running on DOS

      On an 8"? That's awfully obscure. Sure it wasn't 5.25"? If not, you have a really obscure piece of kit there!

      --
      SJW n. One who posts facts.
    4. Re:8 inche floppies worked pretty well by Binestar · · Score: 1

      This is what happens when people try measuring their floppies with their stiffies.

      --
      Do you Gentoo!?
    5. Re:8 inche floppies worked pretty well by tarpitcod · · Score: 1

      Super obscure. You'd want a different / patched DOS too to handle the different sector sizes and number of sectors too. Not impossible, but definitely not a stock or common alternative SIO attached drive.

  16. Re:Maintenance contract? by TechyImmigrant · · Score: 1

    Can you still get a maintenance contract on a Series 1 computer? How expensive would that be???

    It's called hiring all the people in the world who know how it works and giving them a safe job until retirement, followed by nice contract jobs every few weeks once you're into retirement.

    --
    I should use this sig to advertise my book ISBN-13 : 978-1501515132.
  17. Good luck.... by johnsmithperson123 · · Score: 1

    Finding parts on eBay for that.

    1. Re:Good luck.... by scsirob · · Score: 1

      I guess you haven't looked. Plenty of 8" drives and floppy's on offer there.

      --
      To Terminate, or not to Terminate, that's the question - SCSIROB
  18. It would be good if this system didn't work. by Dzimas · · Score: 1

    The best possible outcome for humanity would be that the launch systems for nuclear arsenals don't actually work. The United States currently has a strategic nuclear stockpile of approximately 547 Mt. Detonating those warheads in our atmosphere would simply end civilization, with no winners and no future. Well, unless you're an ambitious young cockroach with your eyes set on world domination.

    Nuclear stockpiles are as sensible as boarding a jetliner with an M2 flamethrower, just in case there happens to be a terrorist on board who needs to be subdued.

  19. Re:So it's air gapped. That's good, right? by thinkwaitfast · · Score: 5, Insightful

    There's probably more rationale here than many realize.

    I'd doubt it. More like,

    If it ain't broke, don't fix it.

  20. Wasn't this on 60 Minutes? by mattack2 · · Score: 1

    Wasn't this stuff covered on a 60 Minutes report in the past year or so?

    Another example being some sort of special tool (a wrench?) being FedEx-ed between sites because some broke and they didn't have extras?

    1. Re:Wasn't this on 60 Minutes? by PPH · · Score: 3, Funny

      Yes. But the story was forwarded to Slashdot via UUCP/dialup with a 12 hop bang path. So we only just got it.

      --
      Have gnu, will travel.
    2. Re:Wasn't this on 60 Minutes? by evilviper · · Score: 1

      Yes, aired April 27, 2014.

      And discussed on Pipedot months ago:

      http://pipedot.org/story/2015-...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  21. No Chinese gov hackers in those systems - too old by millertym · · Score: 1

    There is something to be said about using ancient tech when it works well. Extremely few people out there able to exploit it. As long as it does the job it needs to do reliably, why go ape $*&^ and start trying to spend time and money running it all on new, vulnerability riddles OS's and networked programs. I think any of us in the IT world have seen the latest and greatest ruin a good, smooth process permanently.

    The huge consideration here being that the old tech is indeed reliable, efficient, and functional.

  22. The Russians must be laughing... by bogaboga · · Score: 2

    It amazes me that our so called analysts then laugh at Russia for what they sometimes called its "rustbucket military hardware."

    That was until [in Syria], it delivered a shock to us us in the west, with its successive wins on the battlefield, despite having less hardware compared to the west's.

  23. 8" floppy disks are reliable as fuck! by blind+biker · · Score: 2

    I worked at a bank that had several mainframes IPL-ing from 8" floppies - I left the bank at the end of the 90's - at that point, the system has been operational for more than a decade. As far as I know, not a single floppy has ever failed during the years I've been there, or before my tenure.

    --
    "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    1. Re:8" floppy disks are reliable as fuck! by serviscope_minor · · Score: 2

      Not surprising that the quality went down. I do remember when I was starting off, floppies were reliable. I don't think I actually remember one failing on me, but they were pretty pricey. By the end, they'd been caught in an aggressive price war and so of course the quality was in the pan. It got to the stage where you couldn't even necessarily transfer a file once off on one without it crapping out.

      It's not a "things were better then", it's that a race to the bottom price wise produces junk. Of course if I'd kept on buying expensive 3M ones, I'd probably not be saying this...

      --
      SJW n. One who posts facts.
    2. Re:8" floppy disks are reliable as fuck! by blind+biker · · Score: 1

      3M floppies got worse, too. I know, as I bought those almost exclusively.

      But 8" floppies never did get into that race to the bottom you mention.

      --
      "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
  24. Underfunded military by Dunbal · · Score: 1

    This is what happens when your country has a negligible military budget. Oh wait. So where IS the money going if none of it is going to upgrading existing hardware?

    --
    Seven puppies were harmed during the making of this post.
  25. Re:My watch has more computing power by citylivin · · Score: 2

    but can it end civilization?

    --
    As a potential lottery winner, I totally support tax cuts for the wealthy
  26. It ain't broke, is it? by WheezyJoe · · Score: 5, Interesting

    Sounds to me like tax-payer dollars well-spent on equipment that keeps on giving.

    Maybe your typical gamer has to upgrade every coupla years because the latest Doom doesn't run well on a 4-year old GeForce. Maybe Macy's needs to upgrade their mainframes because they have way more inventory to deal with and want to offer more sales online. And maybe we all need to upgrade off Windows XP (looking at you, banks, with your hackable ATM's) because it was a lousy, full-of-security-holes platform in the first place.

    But as Microsoft tries to force me off my perfectly workable Windows 7 for no damn reason, I wonder why a machine bought by a government department, that does the job and does it really well, needs to be upgraded or swapped out for something new that may or may not work because of something non-related to whether the damned thing does the job and does it really well. Replacing such a system is not easy, particularly when there are consultants circling overhead, hungry for a fat government contract so they can build a complete clusterfuck out of overpriced commodity hardware that does nothing approaching what the old system did. And needs to be upgraded all over again in 2-3 years.

    Yes, on the one hand, holy shit! those are old floppy drives. On the other hand, holy shit! they still work and do the job after all these years. Why have we grown so accustomed to throwing shit out every coupla years? Seems to me, government (state and federal) is one of those areas where shit oughta stay the same for a while so people can focus on getting the job done, rather than re-learning and re-tooling every few years just because some software vendor wants to sell another release of something.

    --
    Take it easy, Charlie, I've got an Angle...
  27. And here's the full GAO report by Guy+Harris · · Score: 4, Informative

    Here's the actual Government Accounting Office report, if you want to read it instead of a Slashdot story about a news story about the report.

    1. Re:And here's the full GAO report by MrKaos · · Score: 1

      Great info - thank you.

      --
      My ism, it's full of beliefs.
  28. Yes, an also accurate headline would be by Anonymous Coward · · Score: 1

    "US Military Uses Unhackable, Proven Technology to Coordinate Nuclear Forces"

    The other examples given are more worrisome, though. Ancient versions of Windows are ridiculously hackable and proven to be unreliable.

  29. Re:So it's air gapped. That's good, right? by tnk1 · · Score: 3, Interesting

    That's the major problem though. It's not that it is a bad thing, precisely, to have a system that works for 50 years. The problem is that logistics and support is horrendously complicated.

    Probably the only way that this is still even partially maintainable is because the government is single-handedly propping up production of 8-inch floppies, which probably now cost something like $20,000 a piece. Not only because they are low production runs, but because on top that, they probably have to be built to a particular government standard that no one has updated since 1970 to make them able to be trusted for controlling nuclear weapons while also being handled by barely trained 18 year olds.

  30. The Brooklyn Bridge is 150 years old. by Brannon · · Score: 2

    nt

  31. Re:So it's air gapped. That's good, right? by MightyMartian · · Score: 1

    Still, apart from having to source 8" floppies, it must occupy time realigning drives. I'm assuming there's a lot of 8" drives sitting in closets to be cannibalized.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  32. Upgrade by Anonymous Coward · · Score: 1

    At least they were smart enough to disable automatic upgrade to Windows 10.

  33. Re:Battlestar Gallactica by Tough+Love · · Score: 1

    Somebody doesn't know their culture.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  34. Bad example by dlenmn · · Score: 1

    It's just like the air traffic control system "upgrade" they've been working on for nearly 30 years. The contractors have ZERO incentive to ever provide a working product. Much better to keep in in development forever.

    Next Generation Air Transportation System started initial planning in 2003 (nowhere close to 30 years ago), and the actual implimentation started some time later. It was always planned to be a slow rollout, in part because aircraft would have to be fitted with new equipment, and airlines did want to rush to do that.

    Moreover, many parts of the system are already working. For example, see the section in the linked article on noise pollution. The system is efficient in that it can pack more planes in a given amount of airspace and can better make the planes follow the same route. If you live under the flightpath that kind of sucks, since the system being efficient means more noise above your head. The increase in noise pollution complains is a signal that the system is working!

    There are many examples of the problem you mentioned, but this isn't really one of them. This is the system working basically as intended: slow but steady progress to update multiple intertwined, critical systems that can't reasonably be replaced all at once.

  35. assembly? by The+Grim+Reefer · · Score: 1

    That file 'is written in assembly language code -- a low-level computer code that is difficult to write and maintain

    Maybe I'm getting old, but did assembly really need to be explained?

  36. Re: So it's air gapped. That's good, right? by Anonymous Coward · · Score: 2, Insightful

    And what exactly is wrong with that?

    New shiny stuff is much scarier...

  37. Supplies for the Governemnt by jacobsm · · Score: 1

    I have a box of 2500 unpunched, punch cards that I can donate to the government if they run short.

  38. Which part is worse? by ngc5194 · · Score: 1

    I'm a little concerned that the system still uses 8" floppies. I'm much more concerned it uses 90's era (or even contemporary) Microsoft products.

  39. Re: So it's air gapped. That's good, right? by Anonymous Coward · · Score: 1

    They probably don't even need to replace them. 5.25" floppy disks for an Atari 800 still work after 30 years.

  40. Re: So it's air gapped. That's good, right? by tnk1 · · Score: 2

    They can last awhile, but if they haven't been recently producing them, these have probably been stockpiled for 20-40 odd years. The disk media may well last that long, but the mechanical drives have a way of becoming misaligned and destroying the media over time. It's unlikely that in 40 years this has not happened at least a few times. It's one thing to pop a disk in that you've only intermittently used into a drive after 30 years, another entirely to have it either being in that drive all the time, or being inserted and removed repeatedly. You're going to have failures and they're going to need to be replaced every so often. Perhaps they have a large enough stockpile of them, but it would make me pretty nervous to have to rely on them lasting.

    But, let's face it, its the government itself who did the study and wants to replace them. They have done the work to determine why they can't be using these forever. I don't even really need to speculate.

  41. Re: So it's air gapped. That's good, right? by Lehk228 · · Score: 1

    in the end it will be much cheaper to put together a little arduino device with some custom hardware that connects as if it were one of those drives and reads and writes "DISK00.IMG" on the inserted (micro)SD card.

    --
    Snowden and Manning are heroes.
  42. Trused code and OS by RY · · Score: 2

    The programs written for the weapons are the only item run on the computers for a reason. The code is trusted and audited which is way more important than new and flashy. Changing or updating the underlying OS or code requires a new audit and verification.

    The calculations can be done longhand for verification.

    Read the rainbow series for more info if they are still in existence.

  43. And people wonder why I laugh... by Xyrus · · Score: 1

    ...when they tell about their weird and bizarre conspiracy theories. The brains have been infected by Hollywood.

    As this article points out, there's still a good chunk of tech that hasn't been changed for decades even in critical systems. There's no super 'leet next age UI. There's a monochrome monitor with a prompt that says "feed-the-badger>" with a tape drive and an 8" floppy.

    If ain't broke and has 1200 pages of mimeographed documentation then it's still good.

    --
    ~X~
  44. Re:if it ain't broke by 4wdloop · · Score: 1
    --
    4wdloop
  45. Re:There's a perfectly good reason for this by MrKaos · · Score: 1

    It makes more sense to just maintain the existing dinosaur equipment until we can throw it away completely.

    ++insightful

    --
    My ism, it's full of beliefs.
  46. I still have some of those by tigersha · · Score: 1

    I still have a few 8 inch disks lying around, some with data on that I programmed in 1980/81 or so. Maybe the DOD is in the market?

    --
    The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
  47. Re:So it's air gapped. That's good, right? by jandersen · · Score: 1

    This is much more common than one would think - I have worked in two major institutions where they used very early computers. One was the GIER - a Danish built, 2nd generation computer with no OS. We would in essence boot with the program we wanted to run from a paper tape - like the Algol compiler, which would compile a program that we'd then boot up afterwards. The main problem was that the capacitors tended to dry out every 5 - 10 years. Things have changed since then :-)

  48. Re: So it's air gapped. That's good, right? by serviscope_minor · · Score: 1

    Stuff of that era, size and expense was designed to be serviced. I'll bet the drives do fail, but I also bet they have tech who can service them. The throwaway culture, especially for mainframe kit wasn't such a big thing then.

    --
    SJW n. One who posts facts.
  49. Old News by Catmeat · · Score: 1

    Eight-inch floppies were pictured in use about two years ago... skip to 2m 50s

    https://www.youtube.com/watch?...

  50. Re: So it's air gapped. That's good, right? by TheRealHocusLocus · · Score: 1

    the mechanical drives have a way of becoming misaligned and destroying the media over time.

    With proper care that is a very long time. When I worked at the phone company ~'88 they were using 8" floppies for batch data entry and some of these had been in use for 10 years! In fact I was the one who forcibly retired these disks and put in place a regimen of regular head cleaning, and it was a hard sell because the operator didn't like to change things that "worked". I had to show her a scored disk (which still worked) beside a new one to convince her. Think of an 8" floppy as a mag-strip a hundred feet long, and the large floppy medium as the densest compaction of media up to that time. Compared to the tiny signal one achieves from magnetic tape the magnetic data was literally SCREAMED onto these disks. The signal was high current, the pulses properly shaped and there was PLENTY of s/n ratio. With proper spares 8" floppy is STILL viable as a storage medium for small amounts of data. Far superior to any mag-strip solution. And there is no sudden catastrophic failure mode as there is with a flash device, if you sensibly encode multiple copies on disc with checksums it is robust,

    Signed, PC tech who used to realign floppy drives with a 'scope and cats-eye pattern disk.

    --
    <blink>down the rabbit hole</blink>
  51. at least they won't get easily hacked by drGreg · · Score: 1

    And these systems must be pretty reliable, they don't make them like they used to.

  52. Re:So it's air gapped. That's good, right? by gtall · · Score: 1

    Nope, you can get them on ebay for under $10, and you can get a 8" floppy controller for under $50.

  53. It's safe from hackers by kurt555gs · · Score: 1

    Like a millennial driving a stick shift car.

    --
    * Carthago Delenda Est *
  54. "Out of date" is not a criteria to look at by mysidia · · Score: 1

    The report shows how outdated IT systems are being used to handle important functions related to the nation's taxpayers, federal prisoners and military veterans, as well as to the America's nuclear umbrella.

    Sorry, "Outdated" is an improper way of describing implementations of custom systems using technology.

    The terminology used is biased in favor of upgrades which might not be necessary and might not be significantly beneficial.

    "They're still running DOS 5.0 or Xenix with COBOL-Based software," Is not in itself a good reason to replace proven working long-standing systems with shiny boxes running a brand new C# application coded by the lowest bidder that runs on Windows 10.

    Unless there is a fundamental change to the working environment that makes an upgrade necessary or beneficial, Or if underlying code is no longer available to audit and update to resolve bugs or security issues, then it's not worth the risk to make a change.

  55. That article rings (analog) true by Kevin+by+the+Beach · · Score: 1

    As a former Air Force 49172 (that would be what was once called Informations Systems Programmer) I learned programming on a Honeywell 6060S at Keisler AFB, MS. Magnetic Core & Punch Cards. w00t! Watch out for the Octal Monster (you had to live that)

    There is nothing wrong with assembler, it just takes discipline and a good understanding of dump analysis. When I was doing it on a daily basis it didn't feel any different reading a dump in hex vs. looking at the source code. IBM 370 assembler is very straight forward when it comes to instruction length and their references. I had a pocket tri-fold chart of the instructions and their representations, that chart along with a pencil and couple highlighters could easily make sense of the most obscure code.

    Sunny, Bright, and Nostalgic here by the Beach

  56. Secure against Cylons by chiefcrash · · Score: 1

    You'll see things here that look odd, even antiquated to modern eyes, like phones with cords, awkward manual valves, computers that, well, barely deserve the name. It was all designed to operate against an enemy who could infiltrate and disrupt even the most basic computer systems. Galactica is a reminder of a time when we were so frightened by our enemies that we literally looked backward for protection...

    --
    Show me on the 1st Amendment bobblehead where the moderator touched you...
  57. Deja Vu by chiefcrash · · Score: 1
    --
    Show me on the 1st Amendment bobblehead where the moderator touched you...
  58. Obsolescence? by luis_a_espinal · · Score: 1

    Security through obsolescence.

    It is not obsolete if it works and can still be maintained. I don't quite see what the problem is. Unless we are facing a serious shortage of 8" floppies, or we are seeing r/w failures so often that they compromise the systems' functions, then nothing is broken and nothing needs fixing.

    Changing this setup will most likely involve rewriting critical software. We can barely try to rewrite a website without triggering a bug zombie apocalypse, I seriously would not want a critical system to be rewritten, upgraded or modified unless absolutely necessary.

  59. Re:So it's air gapped. That's good, right? by luis_a_espinal · · Score: 1

    There's probably more rationale here than many realize.

    I'd doubt it. More like,

    If it ain't broke, don't fix it.

    That's all the rationale (and wisdom) you need in most cases.

  60. As seen on Last Week Tonight by Fudoka · · Score: 1

    I don't want to worry you but take a look at Last Week Tonight with John Oliver: Nuclear Weapons (HBO) on https://www.youtube.com/watch?...

  61. Great idea. by ewhenn · · Score: 1

    Let's connect our nuclear arsenal to the Internet, what could possibly go wrong?!

  62. Real Men at the Treasury at least by BranMan · · Score: 1

    Nice to see we have some Real Men at the Treasury - none of these mamby-pamby programming languages for them. No - Real Men write in machine code (falling back to assembler for more object oriented stuff)!

  63. Re:So it's air gapped. That's good, right? by Lawrence_Bird · · Score: 1

    Its not just air gapping. Air gapping is a fail when an infected usb dongle or other device that can contain hacked firmware is attached to a "secure" system.

    My understanding is that there is still a US based manufacturer of 8" (and other sizes) of floppies. And doubt there would be any issue in having a DoD approved contract to periodically manufacture a bunch of new drives.

  64. YIKES!!! by martinfb · · Score: 1

    What happens when that sole support person goes away? I am sure that person is pretty old by now!

    --


    Self-importance and self-indulgence is the root of ALL evil.
  65. Re:Maintenance contract? by F.Ultra · · Score: 1

    They probably have complete schematics for the whole system so they can perform maintenance themselves.

  66. At least a decent drive by Space+Grrrl · · Score: 1

    I hope at least they are using a Persci voice coil drive and not an old stepper motor drive! When your launching nuclear weapons access time could matter!! :-)

  67. Re:So it's air gapped. That's good, right? by thinkwaitfast · · Score: 1

    Ten years ago, I was wandering around the building where I worked and came across an Eclipse still in use. I'd read about this computer when I was a little kid and it's always held a important place in my life. They're occasionally sold on ebay, maybe someday I'll by one.

  68. Re:Potetntial Hack by laing · · Score: 1
    I love the fact that the last four digits of the above (3741) post happen to match an IBM system from 1974 that used the same diskettes described in TFA. The floppy was formatted to the standard described in the 3740 format. This format was later used on the first CP/M computer systems. My first real computer (a Ferguson Big Board II) used Shugart 850 8" floppy drives that used this same disk format. My second computer (an IMSAI 8080) used 851 drives that supported double sided floppy diskettes.

    The standard 3740 diskette held 241kiB of data and was very slow. We've come a long way since then.

  69. Sounds good to me by RockDoctor · · Score: 1

    IF (a big "IF") the systems were robustly designed in the first case (see previous mention of "big IF") , then an ICBM, relying on gravity (not proved to change, on decadal time-scales) and magnetic field (for orientation), Then BigFuckingDeal if they install updates via a "Stone Slab Reader" Unless there is a change in destruction-radius of the warheads, so what? If I have a "fucks everything up" warhead with an effective footprint 30km in radius, sub-millimetre landing is not relevant. These are weapons of Mass Destruction. Precision is not necessary, and may be counterproductive.

    --
    Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
  70. Nuclear "surety" by pingbak · · Score: 1

    The main impediment to the strategic force upgrade is a process called "nuclear surety". It's what you think it is: a very comprehensive testing process to ensure that the system can't be accidentally triggered (missiles launched.) Surety is as comprehensive as it can be conceived, which means that no process is ever perfect, but this one has a lot of history behind it such that the probability of an accidental or forced launch is very, very low.

    Surety costs significant money, about 65-80% of the cost of upgrading the system. Add to that the general cautiousness of changing the system in any way, and you get the "Holy Cow! You're still using 1960's technology?"