Only Apple does this, so it behooves us to comprehend Apple's policy:
*Apple About Software Updates*
<https://support.apple.com/guide/deployment/about-software-updates-depc4c80847a>
"Not all known security issues are addressed in previous versions."
For example,
1. The iPhone X first shipped for retail sale on November 3, 2017.
2. The last pre-iOS-17 release was iOS 16.6.1 on September 7, 2023.
3. 2,134 days / 365 days in a year = 5.85 years
Note this critical sentence which shows why subsequent iOS 16.x releases
do NOT contain a fully-patched OS (as documented by Apple's own words):
"Not all known security issues are addressed in previous versions."
Since Apple appears to have written their policy under duress from security researchers, let's let others more transparently explain Apple's policy:
*Apple Admits It Only Fully Patches Security Flaws In Its Latest OS Releases*
<https://hothardware.com/news/apple-admits-only-fully-patches-security-flaws-in-latest-os-releases>
"Old versions of operating systems of Apple devices
do not get complete security patches."
*Here's How Long Apple Provides Full Security Updates For Products*
<https://screenrant.com/apple-product-security-update-lifespan/>
"The support document notes that only the latest releases provide
full protection from security vulnerabilities."
*Apple clarifies security update policy: Only the latest OSes are fully patched*'
<https://arstechnica.com/gadgets/2022/10/apple-clarifies-security-update-policy-only-the-latest-oses-are-fully-patched/>
"Despite providing security updates for multiple versions of
macOS and iOS at any given time, Apple says that only devices
running the most recent major operating system versions
should expect to be fully protected."
The difference between Apple's "full update" & "Security Patch" has to take into account Apple's definition of a Full Update (Major or Minor Release).
A full update is any update that:
a. Advances the OS version in a meaningful way (i.e., not an RSR)
b. Adds features, frameworks, or API changes
c. Is part of the active development cycle of that OS
And, most critically:
d. Is released *before* the next major OS version launches
Example: iOS 16.0 -> 16.1 -> 16.2 -> ... -> 16.6.1
These are updates Apple actively develops on a current platform.
a. iOS 16.6.1 (September 7, 2023) is the last of these.
b. That's why it's so important when understanding Apple's release policy
What released after that are security patches (Legacy Support Update).
After iOS 17 launched, Apple occasionally released:
a. iOS 16.7
b. iOS 16.7.1
c. iOS 16.7.2
etc.
These are not full updates as they:
a. Add no new features
b. Make no architectural changes
c. Only patch security vulnerabilities
d. Are issued only to keep older devices safe enough to use
e. Are not part of the active development cycle
They're essentially random "life support" updates.
When we say:
"The last fully-supported iOS release was iOS 16.6.1"
a. We're identifying the final full update
b. Which is the last time the OS received real development attention
c. before Apple moved on to the next major release cycle
That last release prior to the next release is the date that defines:
"Not all known security issues are addressed in previous versions."
The instant the next major release ships, that defines:
a. The end of the iPhone X's full software support
b. The end of feature development
c. The end of API evolution
d. The cutoff for app developers targeting new features
It's the moment the device becomes "legacy" in Apple's ecosystem
Subsequent security patches don't change any of that.
a. iOS 16.6.1 is the last full update.
b. Everything after it is maintenance only.
Only Apple does full-support this way so it behooves us to understand it.
Only Apple does full-support this way so it behooves us to understand it.
That is the way I understand it. So what? Apple just patched Dark Sword
all the way back to iPhone 6.
Look at all the Android phones out there not getting any updates after
just a few years. Many would be vulnerable to this recent one:
https://www.forbes.com/sites/daveywinder/2026/03/16/critical-flaw-875-million-android-phones-at-risk-of-60-second-hack/
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,105 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492321:01:03 |
| Calls: | 14,155 |
| Calls today: | 2 |
| Files: | 186,283 |
| D/L today: |
152 files (31,708K bytes) |
| Messages: | 2,501,982 |