In many organizations' security procedures, the recommended practice for password management is as follows:
This advice about using complex passwords can be enforced by add-ins to the login process. Management may be reluctant or unable to implement these because:
In these cases it may be preferred to rely on a centralised random password generator under the control of the network administrator.
It must be said that the use of a generator in this way is not the author's recommended best practice. However because there is a demand for such a tool, the author has made one available.
It is not intended that this program should be used in high security, e.g. military, environments. However, only the most skilled of potential intruders would be able to deduce the generator algorithm from a small sample of username/password combinations.
The most likely way for security to be compromised
is if the executable program is apprehended. Having done this, the perpetrator could disassemble the code to learn the algorithm, although with the program in his possession this would not be necessary.The commercial version of the software's defence against this is that the system administrator chooses a seed for the random number generator, and therefore although the would-be cracker knows the algorithm, he does not know the random seed, and therefore he has only narrowed the number of possible choices to the maximum value of a 32-bit number.
Further security implications, and options for high security applications, are set out in the Password Generator Security Discussion Paper.