Apple Apologizes About FaceTime Bug, Software Update With Fix Delayed Until Next Week

Discussion in 'MacRumors.com News Discussion' started by MacRumors, Feb 1, 2019.

  1. MacRumors macrumors bot

    MacRumors

    Joined:
    Apr 12, 2001
    #1
    [​IMG]


    [​IMG]

    Apple issued the following statement to MacRumors today in which it apologized for a major FaceTime eavesdropping bug:
    Widely publicized on Monday, the FaceTime bug allowed one person to call another person via FaceTime, slide up on the interface and enter their own phone number, and automatically gain access to audio from the other person's device without that person accepting the call. In some cases, even video was accessible.

    We demonstrated the bug in a video earlier this week:


    Apple disabled Group FaceTime as a temporary server-side solution, preventing the bug from working any longer. Apple is also working on a software update with a permanent fix that it originally said would be available this week, but it has been delayed until next week, according to Apple's statement.

    Apple thanked the Thompson family for reporting the bug--supposedly over a week before it made headlines--and said it is committed to improving the process by which it receives and escalate these reports in order to quash bugs faster.

    Apple already faces a lawsuit in Texas and a proposed class action lawsuit in Canada over the bug. Given the serious privacy implications involved, it is certainly possible there will be more class action lawsuits to come.

    Article Link: Apple Apologizes About FaceTime Bug, Software Update With Fix Delayed Until Next Week
     
  2. otternonsense, Feb 1, 2019
    Last edited: Feb 1, 2019

    otternonsense macrumors 65816

    otternonsense

    Joined:
    Jul 25, 2016
    Location:
    Berlin
    #3
    Stop apologising and do some basic freaking testing and QA before rolling out (delayed) promised features. Every week there's a different bug, "gate" or whatnot.
     
  3. pat500000 macrumors G3

    pat500000

    Joined:
    Jun 3, 2015
    #4
    Oh...NOW you apologize...at this time. You were force to apologize to save face. Thanks to your bug feature, I overheard you saying that you were planning to do some hanky panky stuff.

    Tim, you need to stop shouting “i’m all about security abd privacy.”
     
  4. weup togo macrumors 6502

    Joined:
    May 6, 2016
    #5
    This woman did *everything* right. She got blown off by the security team! Apple's cancerous hiring growth has lead to a mountain of people with no clue about Apple's actual culture or standards. We see the results in the headlines here daily for the last few years.
     
  5. MacFather macrumors 6502a

    MacFather

    Joined:
    Mar 16, 2012
    #6
    I'm surprised they didn't blame Scott Forstall again.
     
  6. Marzel macrumors regular

    Joined:
    Sep 12, 2018
    #7
    And that's probably because new features are becoming more and more complex to develop.
     
  7. snowboarder macrumors 6502

    Joined:
    Jun 9, 2007
    #8
    or China
     
  8. vcboard macrumors member

    Joined:
    Oct 15, 2016
    #9
    I'd imagine that everybody in Apple are breathing down the neck of that lone single poor engineer trying to resolve the bug.
     
  9. goonie4life9 macrumors regular

    Joined:
    Jun 16, 2010
    #10
    To be fair, this is a process-level failure. I never contact Apple until I've tried all the troubleshooting steps I, as an end-user, can. At that point, all that can happen is for the issue to be, "escalated to engineering." Typically, "engineering" asks me to repeat the same troubleshooting and often, they ask nonsensical questions because the agent didn't adequately describe the issue. All of this could be solved by having some from "engineering" communicate directly with customers, but for whatever reason, Apple refuses to allow that. All in all, it typically ends up being a multi-week process, which is exactly what happened here.

     
  10. ImAnAgent Suspended

    ImAnAgent

    Joined:
    Oct 11, 2018
    Location:
    My mind
    #11
    It's impossible to uncover all bugs in any software release no matter what company is involved. That's why releases continue to happen any why beta releases take place. If the bugs aren't found during the betas, you can't blame these companies for releasing a version they feel is ready.
     
  11. givemeanapple macrumors Demi-God

    givemeanapple

    Joined:
    Oct 2, 2016
    Location:
    Earth
  12. Marekul macrumors regular

    Joined:
    Jan 2, 2018
    #13
    Nah only if you have a ****** codebase
     
  13. mattburley7 macrumors 68040

    Joined:
    Oct 13, 2011
  14. az431 macrumors 6502a

    az431

    Joined:
    Sep 13, 2008
    Location:
    Portland, OR
    #15
    Your assumption is that because a bug manifests itself, that Apple doesn't do "basic freaking testing," which is both illogical and incorrect. That's basically like saying if people were careful there would never be a car accident. Duh.

    Regardless of how much testing is done, bugs will pop up, especially in something as complex as an operating system, and especially when you have 1.4 billion devices running that operating system.

    The problem here is Apple's system for handling bug reports is horrible. I've reported bugs that were indeed bugs, and Apple either responded with some canned nonsense about it being intended or didn't respond at all. Then 2-3 years later the bug was fixed. Anytime you have to deal with Apple outside the context of the Apple Store it's a mess.
     
  15. C DM macrumors Sandy Bridge

    Joined:
    Oct 17, 2011
    #16
    Until it's released.
     
  16. otternonsense macrumors 65816

    otternonsense

    Joined:
    Jul 25, 2016
    Location:
    Berlin
    #17
    Yes, like adding poop emoji heads and crappy overlays on 32 people. Priorities.
     
  17. eicca macrumors 6502

    eicca

    Joined:
    Oct 23, 2014
    #18
    Meanwhile, Google, Facebook, Amazon, etc are boldly and obviously stealing EVERYTHING from you and nobody bats an eye.
     
  18. mjharwaz macrumors member

    mjharwaz

    Joined:
    Jul 12, 2017
    Location:
    Tucson, AZ
    #19
    Am I the only person in the world who thinks the process to even get to this bug is asinine and outside of the normal use case of the average person? In what scenario does one find themselves thinking "oh, the other party isn't answering, maybe I should just FaceTime myself?"

    Yes, it's a problem that something like this could be exploited to spy on someone, but without the publicity how many people would have ever tried this in their lifetime, let alone the week it was a problem?
     
  19. jardinager macrumors regular

    jardinager

    Joined:
    Apr 24, 2015
    Location:
    NC
    #20
    Sure. Now that you are forced to acknowledge and correct your mistake, you're sorry.

    Why don't you listen to your customers and developers when they warn you deep in the beta cycle about bugs and problems?

    Why does it take public humiliation and ridicule to get you to fix your sh*t, Apple?
     
  20. usarioclave macrumors 65816

    Joined:
    Sep 26, 2003
    #21
    The real problem with FaceTime is that the connection state can be controlled remotely. If the FT connection state was exclusively driven from the client then this bug couldn't have happened.

    IMO this is the major problem with FaceTime that the bug exposed. The bug implies that Apple can listen in on your phone's audio and video at any time. FT has been around for so long that the functionality is probably part of the design; that's not something that would be "new in Group FaceTime."
     
  21. Marekul macrumors regular

    Joined:
    Jan 2, 2018
    #22
    Only that guy quit two months ago so they had to delay bug fix for a week....
     
  22. cmaier macrumors G5

    Joined:
    Jul 25, 2007
    Location:
    California
    #23
    There are numerous professionals around the world whose only job is to find such vulnerabilities. They work for bad actors of all sorts - oppressive nation states, criminal organizations, etc. THis isn’t about what the average user would figure out.

    And if this lady and her kid figured it out, you can bet that some bad guys knew about it already, and were using it.
     
  23. ipponrg macrumors 65816

    Joined:
    Oct 15, 2008
    #24
    many bugs are divulged privately before they are publicly exposed to the mass. It could happen that this bug has been out longer than a week, it’s just that no one publicly exposed it

    The number 1 rule for finding exploits is to do things that most people don’t do. It’s why QA teams spend a lot of time testing the unhappy paths
     
  24. iName macrumors newbie

    Joined:
    Jul 12, 2008
    #25
    Google and Facebook invade your privacy every day in more insidious ways than you can imagine but THIS is what gets people up in arms? Give me a break.
     

Share This Page