#Secure password creator generator
#Secure password creator code
#Secure password creator password

Not all of those characters have to correspond to a key on a computer keyboard: Unicode has many thousands of different characters, most of which cannot be directly typed.

#Secure password creator password

So weвЂ™re going to create a collection to store the runes that are available to be used in our password: there are various kinds of data structure that we could use, but it seems simplest - and perhaps best - to use a slice for this purpose.ДЄ secure password should use as many different characters as possible, to make sure that itвЂ™s harder for an adversary to guess. Instead of needlessly creating three separate categories of rune, it would be better if we treated them all equally, making sure that thereвЂ™s the same chance of any single rune in our set appearing as another. This ensures that our returned rune will be between min and max. In the case of either upper- or lower-case letters, delta + 1 will equal 26 in the case of digits, it will be 10. This variable is then used as the input to the pseudo-random-number generator.

If you look at the randomRune function, you can also see above how we calculate delta, which is the difference between the rune with the locally biggest integer value and the one with the locally smallest value. (The example under the next heading will solve this problem.) package main ItвЂ™s important to note that this approach gives greater weight to digits, because there are only 10 of them while there are 26 characters in both the upper- and lower-case letters, yet we give each category an equal chance of being chosen. A random floating-point value is generated and its value determines which category we shall pick our rune from.

#Secure password creator code

In the code below, we have an equal chance of choosing between the three main categories of characters. Why use just upper-case letters when we can use lower-case ones and digits too? The goal is to make the final word as hard to guess (or attack by brute force) as possible, so itвЂ™s never a bad thing to have a wide and diverse range of characters used. However, just using one type of character is probably a bad idea, if we want to avoid insecure passwords.

#Secure password creator generator

You can also see how we use an init function, which always runs before the main function, in order to seed the pseudo-random-number generator with the current time in nanoseconds: this ensures that we wonвЂ™t get the exact same runes generated every time the program runs.

The basic rune arithmetic in the randomRune function is similar to what we did when we worked with runes to create a Caesar cipher. The example below takes this approach, adding randomly selected letters to a slice of runes, then concatenating them together as a string: package main So itвЂ™s hard to imagine someone guessing that kind of secure password by pure chance. The simplest sort of relatively secure password is just made up of random letters - you have a one in twenty-six chance of picking any individual letter, which means that if you generate a password with a length of just ten letters, there are 141,167,095,653,376 different possibilities to choose from (26 to the power of 10). Use My Package on Github to Generate Secure Passwords.Structuring Our Code: Object-Oriented Programming.