Graham Cox wrote:
Sure, I understand that. Actually the SHA-1 hash is derived from the - hash of several objects, not just the date. My take is that the combination of the several objects (typically about 8 different pieces of information) is sufficiently unique to be unspoofable in practice. And in fact the SHA-1 is only used as a signature anyway, not as a unique value in its own right - the existence of identical SHA-1 hashes for different info sets wouldn't matter.
Do you present a hash failure to the user in the same way as expiration of the date? Maybe one of the other hashes is changing, and it isn't necessarily the date.
Nice thought, but not the case. The expiry is firing several months too early, not just a few hours.
It might be worthwhile to temporarily change the primary language on your machine, long enough to cause your app to trigger the problem, so you can see it happen. I don't know Korean or Arabic, but I can switch the language and puzzle it out well enough with menu positions and menu lengths and the like to figure things out.
You might also try changing the date on your machine, then create a series of future expiries with sequential months, different days, and different years, so you can try them all under the foreign language that's known to fail. The idea is to get enough predictable data points so you can observe more than occasional failures. Then a pattern might emerge.
-- GG _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
