This could also be a marketing opportunity for us as well. This was quickly put in place and new purchasers can be assured that their license code will never tell them to F***-THIS-S***. If there’s a match, we generate a new code automatically. We built a list of inappropriate words (a list Paul referred to as “my favorite list ever”) and now check the code portion of each key against the list before sending it out. Once I recognized the problem, the solution was easy. On that day, one out of every 128 licenses generated will start with the F-bomb.
AUDIO HIJACK LICENSE CODE GENERATOR
It turns out that one day in the not-too-distant future, our random number generator gets filthy. And of course there are several bad words we can generate, and these odds apply to each one separately. That’s pretty common, and it’s even worse if you count instances split between two groups with a dash in the middle. It turns out that the chances of a random license containing the word F- is actually one in 65,000. But I ran the numbers anyway just to be sure. After all, the chances of generating some bad word at random must be really low.
Hey, you could even get a whole license code made up of four-letter words. The way some of the letters lined up almost looked like a word, how funny.
AUDIO HIJACK LICENSE CODE LICENSE KEY
The cold-sweat moment came the other day as I was entering a license key into a copy of Fission. We started using the new system a few months ago and it has worked well for us, well enough that nothing user-facing changed. This opened up enough room to squeeze in a short unique number next to the rest of the license data.
By adding in the rest of the alphabet, then eliminating letters and numbers which are easily confused, such as 0 (zero) and O (oh), RASN2 was able to have 27 different digits. RASN used hexadecimal, a 16-digit number system using the digits 0-9 and the letters A-F. However we didn’t want to make our codes any longer, so I had to cram more information into the same space. This had the potential to cause problems when two (or more) people with the same name purchased our software, as they would each receive the same license key.įor the new system (RASN2), we decided to add a unique number to each code to make it different from others generated for the same name. The old system (RASN) generated a single unique license key based on the name of the purchaser. It’s worse when you realize that the bug has already been there for months.Ī few months ago I set out to redo our license key system. One of the professional hazards of being a programmer is the cold sweat which comes when you suddenly realize that some code you’ve written has a terrible bug.
0 kommentar(er)
