The problem is general, and it's software, though the quality of hardware matters.
Imagine a tube or pipe with large spheres at each end. That represents every place and/or node and/or path, in, and along, which data is received / sent / streamed --- between any two processes / nodes / spheres.
All of it, now, has to be protected (in contrast to the old days), and by more difficult protection schemes.
Inside each sphere, there are these processes:
- stream data-compression / stream data-decompression
- stream data-encoding / stream data-decoding
- stream data-encryption / stream data-decryption
- AND:
- signing of any of those six possible actions
The "signing" in particular, is being required more and more, of late (by Apple), putting authoritative stamps on actions and/or results of actions.
So, there is more work (and time consumed) in a sphere.
There is also a resulting force upon, expectation of, other processes / other spheres, where the technology used in one sphere, or one process, may not be well-interpreted by said other sphere or by said other process.
In a nutshell, all the above, is what is happening with the Mac OS and the Apple iOS, trying to do the right thing, but largely satisfying the A (Apple) of relationships like:
- process A communicating with process B
- process A communicating with sphere C
- sphere C communicating with sphere D
- process B communicating with sphere C
- sphere D communicating with process A
That kind of thing, where Apple's latest security policy is in action, but the others are not quite up-to-date.
It's causing multiple failures to completely communicate data. And those failures (may) show up as a variety of symptoms.
As best as I can figure to date.
-