What's new in Lockdown 1.1.3
Jun 23, 2021
- just received report of a Lockdown user not being able to download files in Chrome or Edge (Chromium) with no blocking reported in the event logs. Thanks to Luke for the report and solution, v1.1.2 has been uploaded to include a new default path in the whitelist rules for “%programdata%MicrosoftWindows Defender” because executables in there were being used to scan file downloads, rather than their counterparts in %programfiles%, I guess.
New in Lockdown 1.1.2 (Jun 23, 2021)
- v1.1.2 has been uploaded to include a new default path in the whitelist rules for “%programdata%MicrosoftWindows Defender” because executables in there were being used to scan file downloads, rather than their counterparts in %programfiles%, I guess.
New in Lockdown 1.1.1 (Jun 9, 2021)
- This update fixes a bug causing Lockdown to not write additions to the Windows default list of executable file types, and as a result previous versions of Lockdown did not block a few scripting languages namely Powershell and Python. The list below shows what Windows considers an executable file type that is blocked by default (and by all versions of Lockdown):
- WSC
- URL
- SHS
- SCR
- REG
- PIF
- PCD
- OCX
- MST
- MSP
- MSI
- MSC
- MDE
- MDB
- LNK
- ISP
- INS
- INF
- HTA
- HLP
- EXE
- CRT
- CPL
- COM
- CMD
- CHM
- BAT
- BAS
- ADP
- ADE
- Lockdown v1.1.1 also adds these file types:
- JSE
- PS1
- VBS
New in Lockdown 1.1 (Jun 8, 2021)
- Lockdown now remembers your customized whitelist/blacklist settings when enabling/disabling Lockdown through the user interface (does not apply to command line arguments.)
- Added import/export feature for whitelist/blacklists both in the UI and through command line arguments.
- Lockdown now detects when it is enabled/disabled, and enables/disables the appropriate buttons in the user interface, so no more confusion as to whether Lockdown is enabled.