home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.sys.mac.advocacy      Steve Jobs fetishistic worship forum      120,746 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 119,911 of 120,746   
   Maria Sophia to Chris   
   Re: Why does iOS ask for your passwd eve   
   10 Jan 26 22:23:30   
   
   XPost: misc.phone.mobile.iphone   
   From: mariasophia@comprehension.com   
      
   Chris wrote:   
   > Maria Sophia  wrote:   
   >> Hi Chris,   
   >>   
   >> Thanks for the reply as the topic here is how iOS really works, when, we   
   >> all are now aware that no other common consumer OS works this way at all.   
   >>   
   >> To flesh out how iOS really works, I will respond to your points factually   
   >> and precisely.   
   >>   
   >> Note this is the beginning of the activation-lock cascade only Apple does:   
   >>  Jan 7/8 2026    
   >>   
   >> And note, only Apple 'bricks' the device (over time) if you refuse to   
   >> re-enter passwords for accounts that you never logged out of.   
   >>      
   >>   
   >> Note: Apple will unlock the 'bricked' device   
   >   
   > It's not bricked then, is it? It's simply locked.   
   >> but I had to manually visit   
   >> the Apple Store and present government ID to prove to Apple who I am.   
   >   
   > Kinda defeats your attempts at not giving Apple your details. Doesn't it?   
   >   
   >>> This is 100% a you problem. You choose to do that and thus get the   
   >>> repercussions. You claim you're logged in, but if you don't authenticate,   
   >>> you're not.   
   >>   
   >> This is mixing two different concepts.   
   >   
   > Not at all. This is still 100% down to your behaviour.   
      
      
   Hi Chris,   
      
   I agree with you that most people never test how iOS works so they never   
   learn the interesting details that I learned that I have imparted to you.   
      
   Most people simply play games with iOS.   
   I test how it works.   
      
   This thread is about how it works.   
   Once we all understand how it works, we can BEGIN to delve into the WHY.   
      
   But we can't even get to the intelligent part of this question if you   
   refute Apple's own documented behavior without providing any cites at all.   
      
   Since the topic here is the technical behavior of iOS when Apple ID   
   authentication is not refreshed, the tests were to see how iOS handles it.   
      
   My actions were clearly part of testing how the system behaves when it   
   requests reauthentication even though the user is already signed in.   
      
   You should probably commend me for teaching you how iOS really works.   
   The goal was to observe the mechanism, not to avoid signing in.   
      
   1. Regarding the term bricked, whether one calls the state locked or   
   disabled is a wording issue. Every time I said "bricked", I put it in   
   quotes and put the words "Activation Lock" after that, so if you missed   
   that, I apologize for not making it clearer to you what Apple does.   
      
   Remember, no other operating system vendor 'bricks' your device (Activation   
   Lock) but Apple. Only Apple. Nobody else. The main question here is why?   
      
   If you can find a nicer way to say you're locked out of your own device by   
   Apple, then give us those words defending Apple's actions, Chris.   
      
   Because technical point is iOS restricts device functionality when required   
   authentication tokens expire even when the user has not signed out.   
      
   2. The in person identity check is not the subject here. The relevant   
   fact is that iOS requires identity verification when Apple ID   
   authentication cannot be refreshed. That is how the system is designed.   
      
   3. User behavior and system design are separate concepts. The question   
   being examined is how iOS handles expired or unrefreshed authentication   
   tokens. Being signed in and having valid tokens are different states. iOS   
   maintains multiple tokens with independent expiry and when one expires   
   iOS demands reauthentication.   
      
   4. Apple documents the existence of these tokens in its developer   
   documentation.   
      
      a. StoreKit transaction tokens   
            
      
      b. App Store Server API signed transaction tokens   
            
      
      c. Renewal info tokens   
            
      
      d. Apple ID authentication tokens   
            
      
      e. Apple documents that App Store sign in is separate from iCloud   
            
      
   These links show that iOS uses multiple authentication tokens with   
   independent expiry and that App Store authentication is separate from   
   iCloud authentication.   
      
   The behavior observed during testing matches Apple's documentation.   
      
   If you have Apple documentation that shows the described behavior is   
   wrong please include the link so it can be reviewed. Otherwise I will   
   rely on the documentation already cited showing how iOS actually works.   
   --   
   Apple iOS works differently than all other common consumer OS platforms.   
   If you claim to know iOS, and you don't know that... you don't know iOS.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca