Paul Haddad
Grabbed a new Mac App Store receipt. They are back to using SHA1 and it now has an expiration date in 2023.pic.twitter.com/HgenGzPLaB
-
@mjtsai You check the creation date (when the cert was used) against the certificate’s validity period, vs checking the current time.
Matt Stevens
Michael Tsai
@mjtsai So if the certificate is trusted and was valid at the time it was used you don’t care if it is expired.
-
-
@mattstevens Right. My question is, does Apple's sample code implicitly use the current date? (Guess: No. So this wouldn't be a problem.) -
@mjtsai Looks like no and you’re right, it’s not an issue if you don’t check the validity period at all. -
@mjtsai I was wrong, after testing that code will verify the chain against the current time unless otherwise configured. - View other replies
-
@mattstevens@mjtsai at any rate, that doesn't explain the "damaged" dialog since there the app hasn't run at all. It would affect exit(163) -
@mattstevens@mjtsai oops, exit(173), of course. -
@rbrockerhoff@mjtsai Definitely multiple factors and that one is all Apple. I did see 173 logs in console for “damaged” apps though. -
@rbrockerhoff@mjtsai But finding the path that actually triggers “damaged” requires more framework spelunking than I really care to do. -
@mattstevens@mjtsai in my experience, 'damaged' is triggered by a MAS app without a receipt, or corruption in the receipt or app signature. - Show more
-
Rainer Brockerhoff
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.