Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.
posted by CoolHand on Thursday June 22 2017, @06:37PM   Printer-friendly
from the collaboration-what-collaboration? dept.

The rise and fall of FireWire—IEEE 1394, an interface standard boasting high-speed communications and isochronous real-time data transfer—is one of the most tragic tales in the history of computer technology. The standard was forged in the fires of collaboration. A joint effort from several competitors including Apple, IBM, and Sony, it was a triumph of design for the greater good. FireWire represented a unified standard across the whole industry, one serial bus to rule them all. Realized to the fullest, FireWire could replace SCSI and the unwieldy mess of ports and cables at the back of a desktop computer.

Yet FireWire's principal creator, Apple, nearly killed it before it could appear in a single device. And eventually the Cupertino company effectively did kill FireWire, just as it seemed poised to dominate the industry.

The story of how FireWire came to market and ultimately fell out of favor serves today as a fine reminder that no technology, however promising, well-engineered, or well-liked, is immune to inter- and intra-company politics or to our reluctance to step outside our comfort zone.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Interesting) by Anonymous Coward on Thursday June 22 2017, @08:34PM (5 children)

    by Anonymous Coward on Thursday June 22 2017, @08:34PM (#529655)

    I kind of liked Firewire, but it was a huge security risk that I don't think most people realized. Or at least non-technical people. The first time I used it for networking and had a device plugged into one computer pop up for use on the other, I realized just how dangerous the technology was.

    Which is a shame, because that very aspect of it made it great for debugging frozen computers.

    Starting Score:    0  points
    Moderation   +2  
       Interesting=2, Total=2
    Extra 'Interesting' Modifier   0  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Thursday June 22 2017, @08:47PM (1 child)

    by Anonymous Coward on Thursday June 22 2017, @08:47PM (#529661)

    Well that just seems like a driver update was needed.

    • (Score: 0) by Anonymous Coward on Thursday June 22 2017, @09:25PM

      by Anonymous Coward on Thursday June 22 2017, @09:25PM (#529669)

      You're missing the point, if it needs an updated driver, that's still a security problem. It's just that the incident underlined what a security problem the bus was.

  • (Score: 1) by Ethanol-fueled on Thursday June 22 2017, @11:39PM

    by Ethanol-fueled (2792) on Thursday June 22 2017, @11:39PM (#529704) Homepage

    I assume you're referring to DMA? Live forensic analysts liked it too, but not necessarily for its speed.

  • (Score: 2) by kaszz on Friday June 23 2017, @05:40AM

    by kaszz (4211) on Friday June 23 2017, @05:40AM (#529858) Journal

    There could been some switch implemented for restricted use?
    Ie only allow remote memory access outside of specified memory range if said switch is on.

  • (Score: 2) by TheRaven on Friday June 23 2017, @08:17AM

    by TheRaven (270) on Friday June 23 2017, @08:17AM (#529897) Journal
    FireWire wasn't a security risk, some FireWire drivers were because they allowed device-initiated DMA without setting up an IOMMU (a number of Thunderbolt implementations do the same). Apple had a problematic relationship with this. They initially shipped with no restrictions on DMA. Then they realised that it was a security problem and added some quite right restrictions. Then a bunch of their customers complained because being able to do a crash dump using an iPod plugged into an XServe was a killer feature (and it was great for post-mortem debugging - plug in iPod and get a complete core dump of the server, even if the OS has crashed so hard that it can't write to disk), so they reenabled it. This cycle repeated a few times.
    --
    sudo mod me up