Comments on: Case Study: Unique Serial https://blog.jstassen.com/2013/02/case-study-unique-serial/ A place for collecting my miscellaneous thoughts. Mon, 05 Jun 2023 06:26:58 +0000 hourly 1 https://wordpress.org/?v=7.0.7 By: TheBox193 https://blog.jstassen.com/2013/02/case-study-unique-serial/#comment-34 Sun, 15 Dec 2013 21:31:00 +0000 http://blog.jstassen.com/?p=107#comment-34 In reply to Jacob Zimmerman.

You are somewhat correct about the guessable bit. For this project a human validates the serial against the database when the certificate is redeemed. Needless to say, the odds of a human client guessing a valid as well as unused serial string is highly unlikely. If they were lucky they may get three guesses before being rejected outright.

Appending a hash of the customer’s name certainly add a level of ambiguity/security, but probably is unneeded for this business use-case.

]]> By: Jacob Zimmerman https://blog.jstassen.com/2013/02/case-study-unique-serial/#comment-33 Wed, 16 Oct 2013 19:36:00 +0000 http://blog.jstassen.com/?p=107#comment-33 All but the last four digits are guessable… But that requires that the person trying to guess knows the exact second that the serial was generated. Instead of doing random numbers, you could hash some piece of information, such as the customer’s name and cut it down to 4 digits by doing a modulo of 10000.

]]> By: Michael Wogelius https://blog.jstassen.com/2013/02/case-study-unique-serial/#comment-2 Mon, 18 Feb 2013 01:38:03 +0000 http://blog.jstassen.com/?p=107#comment-2 This was OK.

]]>