History of user-visible changes. Last update: 2024-11-03
Do you have a bad habit of typing -AsPlainText -Force like I do? ConvertTo-SecureString may have given you some muscle memory that's hard to ignore. Fortunately, this version includes a secret -Force parameter that does nothing except allow you to type it.
- This version is more secure, as the generated password is now built in memory as a
[SecureString], and only converted from one when this cmdlet is run with-AsPlainText. - Added a new
-ExcludeCharactersparameter which does as it says; generated passwords will not include those characters. Thanks to GitHub user @wwc-trevor for the great idea and for testing my work.
This version builds the password in-memory as a [SecureString], which means it is never stored insecurely.
In addition, I've added a new `-ExcludeCharacters`` parameter which does as it says; generated passwords will not include those characters. Thanks to GitHub user @wwc-trevor for the great idea and for testing my work.
Not dead yet! In this version, the cmdlet's verb has been changed. It is now called Get-RandomPassword (but New-RandomPassword still works.)
Also, what makes it worth a major change? We can now generate passwords that are made of random words. Use the -Words and -WordList parameters and generate more readable passwords, like:
hemolytic<sheeptick=PlannedPachydermatouspowder³Estblackberries<kitakyushu#imcompressibility%roadway
This is a bug-fix release with no visible changes.
This is the first public release, so everything is new to the world. If you happen to have an earlier version, you'll notice that passwords are now returned as SecureString objects. To restore the earlier behavior, add the -AsPlainText parameter.
To learn more about this module, run these commands:
Get-Help New-RandomPasswordGet-Help about_PSPasswordGenerator