v1.1.53

RELEASES HAVE MOVED

Please visit the change log and downloads page for the information on the latest releases

Change log

• Fixes an issue #109 where a NullReferenceException occurs using the PowerShell module to change the store path

v1.1.x Update Information

v1.1 introduces several new cmdlets for helping to manage your Password Protection store.

• Sync-HashesFromHibp - Allows you to sync hashes from the Have I Been Pwned API directly into your compromised password store. This replaces the previous flat-file import process.
• Get-PasswordFilterConfig - Allows you to get the registration and enabled/disabled status of the password filter, as well as the password store location
• Get-PasswordFilterPolicy - Allows you to see the filter policy settings currently in place
• Set-PasswordFilterConfig - Allows you to set the store location and enabled/disabled status of the filter

Updated documentation is available at docs.lithnet.io

v1.1.51

Change log

• Fixes an issue where some of the PowerShell scripts in the installer were not signed

v1.1.x Update Information

v1.1 introduces several new cmdlets for helping to manage your Password Protection store.

• Sync-HashesFromHibp - Allows you to sync hashes from the Have I Been Pwned API directly into your compromised password store. This replaces the previous flat-file import process.
• Get-PasswordFilterConfig - Allows you to get the registration and enabled/disabled status of the password filter, as well as the password store location
• Get-PasswordFilterPolicy - Allows you to see the filter policy settings currently in place
• Set-PasswordFilterConfig - Allows you to set the store location and enabled/disabled status of the filter

Updated documentation is available at docs.lithnet.io

v1.1.48

This version introduces several new cmdlets for helping to manage your Password Protection store.

• Sync-HashesFromHibp - Allows you to sync hashes from the Have I Been Pwned API directly into your compromised password store. This replaces the previous flat-file import process.
• Get-PasswordFilterConfig - Allows you to get the registration and enabled/disabled status of the password filter, as well as the password store location
• Get-PasswordFilterPolicy - Allows you to see the filter policy settings currently in place
• Set-PasswordFilterConfig - Allows you to set the store location and enabled/disabled status of the filter

Updated documentation is available at docs.lithnet.io

v1.0.7244

What's changed

Fixes an issue where Test-IsADUserPasswordCompromised cmdlet would fail when a server name was not specified, and NTLM was disabled for the calling user

v1.0.7243

What's changed

Fixes an issue from v.0.7242 where the PowerShell module would not load with a dependency not found error

v1.0.7242

What's changed

Fixes an issue where LPP running in LSASS protected mode on Windows Server 2012 or Windows Server 2016 would not load after installing the latest version of LPP, or after installing the latest Microsoft Visual C++ Runtime.

v1.0.7239

What's Changed

• Fixes #75 Test-IsADUserPasswordCompromised: Getting error "The output char buffer is too small to contain the decoded characters" for some user accounts
• Bump Newtonsoft.Json from 12.0.3 to 13.0.1 in /src/PasswordProtectionPS by @dependabot in #79

v1.0.7238

Changes the behavior of regular expression matching from requiring an exact match, to requiring only a partial match, as well as allowing case-insensitive matching.

This means that where a previous regex of password would only match an exact input of password, the same filter will now match this is my password

v1.0.7236

Adds fix for issue where no events are logged if LPP starts before the event log service and tries to log something
Add a backup file-based log to %windir%\logs\lpp.log
An event log entry is created on startup

This version is Microsoft signed and suitable for use in environments where LSA protected mode is enabled

v1.0.7234

Adds an event log entry on initialization of the module

Not this is a pre-release and is not signed by Microsoft and therefore cannot be used when LSA Protected Mode is enabled. Use the latest release version for Protected Mode support.