Slashdot Mirror


iOS 7 Update Silently Removes Encryption For Email Attachments

An anonymous reader writes "Apple has removed encrypted email attachments from iOS 7. Apple said back in June 2010 in regards to iOS 4.0: 'Data protection is available for devices that offer hardware encryption, including iPhone 3GS and later, all iPad models, and iPod touch (3rd generation and later). Data protection enhances the built-in hardware encryption by protecting the hardware encryption keys with your passcode. This provides an additional layer of protection for your email messages attachments, and third-party applications.' Not anymore."

39 of 68 comments (clear)

  1. Old. Needs an update. by Anonymous Coward · · Score: 3, Informative

    This 'news' is about a week or two old. Apple already issued a statement acknowledging the situation and is looking into it.
    Will probably fixed with an update.

    1. Re:Old. Needs an update. by Rosyna · · Score: 1

      What does the author of TFA want? Double-encryption of message attachments? The storage of the iPhone is always encrypted. In order to access any files, you must supply the encryption key. He supplied the key and could read the files.

      Unless he wants attachments double encrypted or encrypted on iCloud itself?

    2. Re:Old. Needs an update. by Anubis+IV · · Score: 3, Informative

      The storage of the iPhone is always encrypted. In order to access any files, you must supply the encryption key. He supplied the key and could read the files.

      From what I understand, that's actually not what's happening here, and that's the problem. He was able to simply mount the disk and gain access to the files, without having to supply an encryption key. In contrast, the messages themselves were encrypted, just as you'd expect. More or less, it turns out that not everything that's stored on the iPhone is actually being encrypted.

    3. Re:Old. Needs an update. by Rosyna · · Score: 1

      You cannot mount the disk without the encryption key.

    4. Re:Old. Needs an update. by Munchr · · Score: 1

      But even that is doing it wrong. Your fingerprint is NOT a password, it's a login ID. It should only ever be used to identify an account name, rather than be used to protect said account. Using a fingerprint as a password is why it is so trivial to bypass, and gain access to these improperly secured devices.

    5. Re:Old. Needs an update. by michelcolman · · Score: 1

      OK, so if I understood correctly, the entire "disk" (SSD) is encrypted with a key that can be unscrambled with the passphrase (just 4 digits for most people), and Apple used to also encrypt e-mail attachments one extra time on top of the full disk encryption, but now no longer does.

      Can anyone explain what the added value was of the extra encryption they used to add and that is apparently so sorely missed now?

      After all, what were they using to encrypt those attachments? Errr... the same passphrase, right? After all, I can boot up my iPhone, enter my passphrase, and read all my mail. No other extra strong authentication needed to get to e-mail attachments. If someone can get the password by brute-forcing the full disk encryption, they can then use that password to simply log in and open Mail.

      Ergo, the extra encryption was totally useless and just a waste of battery power. Or am I missing something here?

    6. Re: Old. Needs an update. by ikejam · · Score: 1

      For one, a it enables a fairly simple and quick Remote wipe: delete the encryption key and remote wipe is done in a second.

    7. Re: Old. Needs an update. by michelcolman · · Score: 1

      Yes, but I was talking about the EXTRA encryption they used to apply to e-mail attachments. The full disk encryption is still present, that hasn't changed. I was just wondering why they bothered to apply an extra encryption step to e-mail attachments if by breaking full disk encryption you could get the passcode and break all the other encryption too without extra effort.

  2. Title is Misleading by Anonymous Coward · · Score: 5, Informative

    The encryption for email attachment was not removed, it was never present.

    It's not nefarious, it's incompetent.

    Read the original (shorter!) post (http://www.andreas-kurtz.de/2014/04/what-apple-missed-to-fix-in-ios-711.html) instead of the rehashed ad-selling copy.

  3. I need more info by sgt+scrub · · Score: 2, Insightful

    At first glance it looked like there might have been a significant enough performance hit using hardware encryption the took it out. It didn't seem like a big deal. TFA makes it sound like encrypted email I pull from my email server is stored decrypted. That would be a big deal.

    --
    Having to work for a living is the root of all evil.
    1. Re:I need more info by Anonymous Coward · · Score: 1

      The idea behind hardware encryption is that there is no performance hit. Software encryption though is a performance hit.

    2. Re:I need more info by sgt+scrub · · Score: 1

      Not in CPU cycles but power. Granted, I should have pointed that out. This is /. after all.

      --
      Having to work for a living is the root of all evil.
    3. Re:I need more info by blackest_k · · Score: 1

      As a parallel case encrypted satellite signals were routinely decrypted with software cams for years without problems other than key updates. Nagra 3 still appears to be secure after around 4 or 5 years since its introduction. In comparison to these satellite boxes an iphone is a super computer. OTR used with pidgin encrypts and decrypts as you type.

      Just because it is hard to decrypt an encoded block by brute force does not mean it is hard to encrypt and decrypt with a given key set.

  4. No problem by mysidia · · Score: 1

    Encrypt your attachment with PGP before sending.

    Or use a word .DOC managed by Active Directory Rights Management Services, or else: encrypted with the 'require a password to open this document' option

    1. Re:No problem by CaptainJeff · · Score: 1

      Yep...no problem doing these things ON AN IOS DEVICE...

    2. Re:No problem by jonyen · · Score: 3, Interesting

      There's an app for that: http://ipgmail.com/

    3. Re:No problem by Dr.+Evil · · Score: 2

      None of that helps when you receive an attachment on your device.

    4. Re:No problem by tepples · · Score: 1

      Doesn't one of the paid alternative mail user agents support PGP encryption and decryption?

  5. Again a clueless article... by gnasher719 · · Score: 4, Informative

    Fact is, you can't read the data on a locked iPhone. You _can_ read the data if you, as the owner, unlock the iPhone, for example for backing it up. But if the NSA gets your locked phone into their hands, there's nothing that they can do. All the data is _always_ read and written using hardware decryption.

    In addition, apps can use further encryption on a per-file basis. Mail does that for most files, but apparently not for attachments. Additional encryption means for example that entering the key code is needed again for that kind of file. But files without that additional encryption still can't be read.

    What the guy is complaining about is like sending unencrypted data over https, or putting unprotected documents into an unbreakable safe.

    1. Re:Again a clueless article... by antdude · · Score: 1

      Doesn't Apple have access to these locked phones for law enforcement to request with warrants?

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    2. Re:Again a clueless article... by DigiShaman · · Score: 2

      Doesn't the master code get stored on Apple's iCloud network for iOS devices? I know it's optional to have it backed up there when using FileVault for OSX. Anyways, all the NSA has to do is subpoena the information from Apple and they're in like Flynn!

      --
      Life is not for the lazy.
    3. Re:Again a clueless article... by Anonymous Coward · · Score: 3, Informative

      Do a little googling... It seems Apple bypasses the OS to read the encrypted data directly, then does a brute-force attack on the passcode. Most people use a 4 digit numerical passcode, and very very few use more than 8 alphanumeric digits so brute forcing is usually a matter of minutes. There are third-party forensics tools that can do the same, but most police departments aren't up to speed and have an easier time just shipping the device+warrant to Apple and waiting a few weeks. Your data is only as safe as the password you lock it with...

    4. Re:Again a clueless article... by SuperKendall · · Score: 1

      No, we can trust the MANY hackers who have checked and found the master key is not transmitted.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    5. Re:Again a clueless article... by AmiMoJo · · Score: 1

      Do you trust Apple's hardware encryption implementation? If I wanted a secure phone I'd want one where the encryption system was open source so I could verify it myself. After Goto Fail and Heartbleed people are looking at this stuff a lot more closely, when possible.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    6. Re:Again a clueless article... by Bert64 · · Score: 1

      You can configure android to use a 4 digit pin (or nothing at all), and you can also configure ios to use a long passphrase (which for most people is just a complete nuisance to enter on a touchscreen device).

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    7. Re:Again a clueless article... by gnasher719 · · Score: 1

      Do a little googling... It seems Apple bypasses the OS to read the encrypted data directly, then does a brute-force attack on the passcode. Most people use a 4 digit numerical passcode, and very very few use more than 8 alphanumeric digits so brute forcing is usually a matter of minutes. There are third-party forensics tools that can do the same,

      The trick is that only software signed by Apple is able to try out passcodes. When you enter a passcode say 1234, that passcode gets sent to Apple-signed software which then tries it out. Apple can obviously create Apple-signed software that tries any number of keys.

      There are two obstacles for this: One, Apple needs a legal search warrant and the actual device. Two, passcode checking is designed to take about 1/10th of a second per key. So 4 digits can be cracked in 15 minutes. 8 digits would take months. 8 digits and letters are uncrackable.
      br Third-party forensic tools can't do that unless they can jailbreak your phone, so update the OS to a version that cannot be jailbroken. Third-party tools tend to attack backups, but you can tell iTunes to make encrypted backups. (That also has the advantage that iTunes will backup passwords stored on the phone; it doesn't back them up to an unencrypted backup).

    8. Re:Again a clueless article... by gnasher719 · · Score: 1

      Doesn't the master code get stored on Apple's iCloud network for iOS devices? I know it's optional to have it backed up there when using FileVault for OSX. Anyways, all the NSA has to do is subpoena the information from Apple and they're in like Flynn!

      Doesn't get stored anywhere. FileVault for MacOS X works slightly different because it has no individual key built into the CPU. When you backup that key with Apple, you have to supply three security questions + answers and it looks like the answers are not stored but just used to encrypt / decrypt the key. Apple states that without the security answers, they are not capable of supplying the code.

    9. Re:Again a clueless article... by Geeky · · Score: 1

      Exactly, it's a nuisance. On my phone even a 4 digit pin is a pain - I just want to swipe and start using it. I do put up with a pin to prevent casual nosiness if I leave it on my desk, but otherwise I wouldn't bother.

      I care about security, but I also care about the balance between that and convenience. It's risk management - the likelihood of losing my phone is low, the stuff on there isn't that sensitive, so I opt mostly for convenience.

      --
      Sigs are so 1990s. No way would I be seen dead with one.
  6. Re:Or... by epyT-R · · Score: 4, Insightful

    When it comes to encryption, a paranoid default assumption rules the day.

  7. Silently. SILENTLY! by konohitowa · · Score: 4, Funny

    They forgot to use the phrases "much maligned" and "beleaguered". But "silently" is always a great fallback.

  8. BlackBerry FTW by acoustix · · Score: 1

    Suck it, iOS fanbois.

    --
    "A plan fiendishly clever in its intricacies"- Homer Simpson
    1. Re:BlackBerry FTW by Wovel · · Score: 1

      Ah blackberry where they don't need your device because they just hand over the keys to the completely unnecessary server companies were forced to stick in the middle of the email chain.

    2. Re:BlackBerry FTW by narcc · · Score: 1

      Ah, you're confused, I see. They can't "hand over the keys" because they don't have them. As always, BES users are safe.

      Or are you that guy who keeps repeating this despite being told, multiple times, that it's nonsense?

  9. Meh by excelsior_gr · · Score: 1

    What kind of idiot has sensitive data on their iStuff (or Android, for that matter), anyway? Companies go with Blackberry for this exact reason.

    1. Re:Meh by dinfinity · · Score: 1

      Almost everybody.

      Sensitive corporate data is not the same as sensitive data in general.

  10. Big deal? by countach · · Score: 1

    I have to say I don't see the big deal. If you're going to encrypt email attachments, what about the emails? What about all your other data? That's what disk encryption is for surely. This was just a band aid for one scenario among hundreds.

  11. Re:Or... by hebertrich · · Score: 2

    Yup, less trouble for the NSA .. Apple has collected it's 30 silver pieces .

  12. Re: Double? by allan572 · · Score: 1

    This is simply confusion. Everything on the device is encrypted. Attachment that I sent via email may not be being sent encrypted. That's where the confusion lies.

  13. I used the Google: ios pgp mail client by tepples · · Score: 1

    Apparently so. Google Search queries ios mail clients and ios pgp mail client gave relevant results when I tried them today, one of them being "iPGMail" ($1.99) on the App Store. My only explanation for this is that Apple has loosened up on the whole "duplicating included apps" bit since it first introduced the App Store.