http://iPhoneIncubator.com/blog/debugging/do-not-trust-the-system-clock Tips and Tricks for iPhone, iPod, iPad and iOS Developers Tue, 17 Apr 2012 16:54:31 -0600 http://wordpress.org/?v=2.8.6 hourly 1 http://iPhoneIncubator.com/blog/debugging/do-not-trust-the-system-clock/comment-page-1#comment-4772 Dave Sun, 12 Sep 2010 16:26:06 +0000 http://iPhoneIncubator.com/blog/?p=395#comment-4772 Given the requirement that the timestamp be provided by the client, the mistake that you made was in assuming that the resulting value would have a length of 10 characters. It would have been much better to accept the value that the client provided, then attempt to validate it as an actual date. Given the requirement that the timestamp be provided by the client, the mistake that you made was in assuming that the resulting value would have a length of 10 characters. It would have been much better to accept the value that the client provided, then attempt to validate it as an actual date.

]]> http://iPhoneIncubator.com/blog/debugging/do-not-trust-the-system-clock/comment-page-1#comment-1738 Nick Wed, 30 Dec 2009 15:55:30 +0000 http://iPhoneIncubator.com/blog/?p=395#comment-1738 @Adrian: I completely agree with you that having a single system of reference for time is in most cases the best design. However in this rather unusual example the timestamp had to be generated on the client to meet the requirements. I can't go into too much detail; suffice to say that it was security related. @Adrian: I completely agree with you that having a single system of reference for time is in most cases the best design. However in this rather unusual example the timestamp had to be generated on the client to meet the requirements. I can’t go into too much detail; suffice to say that it was security related.

]]> http://iPhoneIncubator.com/blog/debugging/do-not-trust-the-system-clock/comment-page-1#comment-1737 Johan Wed, 30 Dec 2009 14:25:56 +0000 http://iPhoneIncubator.com/blog/?p=395#comment-1737 Thanks for the insight. I always marvel at the bugs you find when your system's clock is out of sync. Try using certificates when your clock is set to Jan 1st 2001 and see what strange errors you receive :) Thanks for the insight. I always marvel at the bugs you find when your system’s clock is out of sync. Try using certificates when your clock is set to Jan 1st 2001 and see what strange errors you receive

]]> http://iPhoneIncubator.com/blog/debugging/do-not-trust-the-system-clock/comment-page-1#comment-1734 Adrian Wed, 30 Dec 2009 08:55:46 +0000 http://iPhoneIncubator.com/blog/?p=395#comment-1734 Wouldn't it had been better to make the server create the timestamps at each connection? This way you centralize time information with the same clock (the server's). I agree that you should not trust user data, but you might as well have skipped the timestamp feature altogether. I don't know, maybe you couldn't, so excuse my ignorance :) Wouldn’t it had been better to make the server create the timestamps at each connection? This way you centralize time information with the same clock (the server’s). I agree that you should not trust user data, but you might as well have skipped the timestamp feature altogether. I don’t know, maybe you couldn’t, so excuse my ignorance

]]>