17 ms·
About the security content of iOS 16.2 and iPadOS 16.2
- takoid 4y agoAnyone else having issues creating a recovery key for their device? I have tried several times to do so since updating to 16.2 but I can’t get the code to verify.
- byproxy 4y agoLikewise, on an iPhone XS.. if that matters.
- takoid 4y agoAre you also having issues? I’m troubleshooting the issue with Apple Support right now but not having any luck. They said they are going to open a ticket with the engineering team.
- coder543 4y agoI created a recovery key no problem. I'm confused about the Security Key for 2FA situation, since I can't find that anywhere on iOS. On the AppleID website, it mentions it, but the "learn more" link 404s[0], and the "continue on device" button errors out. I guess they're working on rolling this feature out on the backend still. [0]: https://support.apple.com/en-us/HT213154 https://support.apple.com/en-us/HT213154
- photoGrant 4y agoSecurity Key features are beginning 2023
- bombcar 4y agoI made one seemingly fine on a iPhone X - but I updated via a cable to my Mac instead of doing it on device.
- radicaldreamer 4y agoTheir servers are getting hammered, I think some of these features will be unreliable to enable temporarily.
- SamuelAdams 4y agoYou would think generating and verifying a recovery key wouldn’t need server access, but I’m getting the same thing as OP on an iPhone 13 mini. I wonder if one of my PiHole lists are blocking it?
- encryptluks2 4y agoI believe they also keep a copy of your recovery key. Apple touts privacy and security but most people I know that use Apple just repeat whatever they claim in their press releases, and have no clue if their device is actually secure.
- smoldesu 4y agoThey claim that's not the case, at least with this new configuration. I'm not sure if I believe them, but this shouldn't be an issue. In theory.
- riolu 4y agoFor someone with luks2 in the username you sure have a lack of understanding about encryption. Why would it be so hard to believe that your recovery key is hashed and salted like every other password? You can't view your key after creation, you have to regenerate it. Do I really need to pull out Wireshark to verify this for you? Advanced data protection is explicitly removing Apple as a holder of your keys, it's not re encrypting anything, it's not new encryption. The entire process is just deleting the key that was already stored on their servers anyway. How would it be in Apple's interest to keep your recovery key after press releases and multiple warnings saying you're on your own for recovery.
- encryptluks2 4y ago
- thefurdrake 4y agoI attempted to create a recovery code on my ipad. I tried bout 5 different codes, and I could never get them to verify. I had to enable/verify the recovery code on my macbook, after which it worked first attempt. Something's up with the ipadOS/iOS versions.
- GavCo 4y agoIncludes an ‘actively exploited’ zero-day affecting most iPhones: https://news.ycombinator.com/item?id=33974923 https://news.ycombinator.com/item?id=33974923
- arijun 4y agoFrom your article, looks like that was fixed in 16.1.2, not 16.2
- deleted 4y ago[deleted]
- uvesten 4y agoOuch! That felt like a longer-than usual list of bugs, especially the memory mgmt bugs leading to arbitrary code execution. And a sizeable number of remotes (if you include webkit in that category.) I honestly don’t know what to feel; ”great that they fixed so many!” or ”yikes, there are probably millions more like this :(”
- pjmlp 4y agoThat is great, because it is what is causing the business support for safer languages. The amount of hours * salary rate per hour, burned with those security fixes.
- twawaaay 4y agoFor some types of apps, sure. But if you look at the list, the ones that sting the most are kernel or video parsing errors or similar. I am just not seeing these being implemented with anything else than an efficient, low level programming language. At least not for the foreseeable future. But what it may do, hopefully, is getting rid of all that audio/video/photo stuff from the kernel. One has to ask why a video encoder can leak kernel memory in the first place. (This was rhetoric question, we all know why. It is just not sustainable to put more and more stuff into monolithic kernel as you add more silicon to solve some CPU/GPU intensive problems because it is just easy.)
- pjmlp 4y agoAO2 Blue Bottle had video player implemented in Active Oberon, naturally with snippets of Assembly on the hot path. https://gitlab.inf.ethz.ch/felixf/oberon/-/tree/main/source https://gitlab.inf.ethz.ch/felixf/oberon/-/tree/main/source
- Tepix 4y agoWhat difference does it make if there are 3 or 5 remote code execution bugs that were fixed? To me the list seemed pretty ordinary.
- Gigachad 4y agoWhat is Apple doing about these non stop memory safety bugs? Google has put out a post about how they now write the majority of Android code in memory safe languages including 1.3 million lines of production Rust. While Apple hasn't said anything as far as I'm aware. https://security.googleblog.com/2022/12/memory-safe-languages-in-android-13.html https://security.googleblog.com/2022/12/memory-safe-language...
- saagarjha 4y agoMajority of new Android code. Apple also has been writing parts of their operating system in a memory safe language, Swift.
- deleted 4y ago[deleted]
- randyrand 4y agoMost new code at Apple is not written in Swift, just a small portion.
- saagarjha 4y agoI actually think a lot of their new projects are written almost exclusively in Swift. There’s a lot of existing code that would need work to embed Swift into, though. (They’re working on it: https://www.swift.org/blog/future-of-foundation/ https://www.swift.org/blog/future-of-foundation/)
- deleted 4y ago[deleted]
- pjmlp 4y agoWell, given their WWDC 2022 announcement regarding Objective-C, and that Swift has surpassed C++ on iOS 16, things are starting to change.
- 4y ago
- hgo 4y agoAs another poster said: ouch. Out of caution, may some of these vulnerabilities be at all relevant to macOS?
- saagarjha 4y agohttps://support.apple.com/en-us/HT213532 https://support.apple.com/en-us/HT213532
- nequo 4y agoInteresting how all of these "security content" documents frame the bug fixes as "improvements." For example, in this one: This issue was addressed with improved data protection. An out-of-bounds write issue was addressed with improved input validation. A logic issue was addressed with improved checks. The issue was addressed with improved memory handling. Makes it sound like data protection, input validation, checks, and memory handling were fine. But now they are better. Whereas the truth is that they were bad and led to data leaks and remote code execution. As it goes with improvements, they keep coming. Wouldn't it be better for Apple to own up to the fact that these defects are indeed defects, and be transparent about what measures they are implementing that prevent such defects from being added to the code base or from being exploited? Google wrote about the former a couple weeks ago[1] and Apple itself is not doing badly in the latter department.[2] [1] https://security.googleblog.com/2022/12/memory-safe-languages-in-android-13.html https://security.googleblog.com/2022/12/memory-safe-language... [2] See Luca Todesco's talk from October: https://www.youtube.com/watch?v=8mQAYeozl5I https://www.youtube.com/watch?v=8mQAYeozl5I
- kube-system 4y agoIt's a matter of perspective. When you run a business, all of your public communication is marketing communication. That's why they're phrased in the positive, and they're not necessarily highlighting the shortcomings they're aware of.
- NoPicklez 4y agoExactly, to the majority of the population, this looks to them like Apple are constantly improving, as opposed to fixing what were defects/gaps. And that's exactly what Apple want, which is how you run a business.
- saagarjha 4y ago> this looks to them like Apple are constantly improving, as opposed to fixing what were defects/gaps Going to negative to less negative is still a positive change.
- pifm_guy 4y agoThere are a lot of security fixes here. It seems reasonable to assume that next month there will be a similar set. Many of the vulnerabilities are remote exploitable, sometimes even on a locked device. Only one such exploit is needed for someone to be able to steal your data from a locked lost phone - either by knowing an exploit before Apple does, or by keeping your phone in a metal box for a month before exploiting it.
- lynx23 4y agohttps://applevis.com/blog/apple-releases-ios-162-ipados-162-bringing-bug-fixes-voiceover-braille-users https://applevis.com/blog/apple-releases-ios-162-ipados-162-... > At the time of writing, we are aware of the following new bugs ... I wonder if I will ever be able to install a .0 iOS release without breaking my world.
- AdamN 4y agoNo. But why would you expect that? .0 is for the general population but if you're a power user with a mix of libraries and applications and configurations plugged together over the prior decade to make your 'World', you need .1 or .2.
- lynx23 4y agoYour post seems to imply that people with disabilities are not part of the "general population". Also, they are considered power users and if something they need doesn't work, they are on their own? Pretty harsh, but its a free world. Everyone is entitled to their opinion.
- AdamN 4y agoApologies, didn't notice the link there. Agreed that the 3 'moderate' bugs when it comes to accessibility probably should have been a launch blocker for the .0 release (presuming they were reported before the release). I don't consider an OS being accessible a Power User thing - it's just a core requirement since those with disabilities are part of the "general population" and their standard usecases should be satisfied before the GM.
- pabs3 4y agoHmm, I wonder if those WebKit/ppp bugs also apply to Linux and other platforms.