Applocker blocking certain 1pw exe files
Dear all, anyone here using Windows Applocker and having problems with (only certain) exe files?
Executable files signed by Agilebits are allowed as per Publisher Rule but for some reason some exe files related to 1pw (Installer exe and Update exe for example) are being prevented from execution:
I´ve seen a similar post in this community in regards to Applocker blocking 1pw files because of a problem with the file signature (revoked certificate). That doesn´t seem to be the case for my problem though, as PowerShells Get-Authenticodesignature command returns "valid" as certificate status.
Any ideas? I´m happy to provide more context / details if necessary.
Many thanks!
Hi all and thanks everyone for contributing ideas and suggestions. To sum it up:
- 1password is in the process of changing the way files are being signed and while this is ongoing, exe files will have two certificates ("dual signed")
- Applocker will block those dual signed files (at least the 1password files, I havent tested this on other files) when allowd by a "Publisher Rule"
- As a workaround it is possible to allow the files via "File Hash Rules" (meaning: every single file = one rule per file)
- After 1password is done transitioning the signing process, the dual signing will stop and therefore Applocker Publisher Rules are likely to function again as they should
This is what the Support wrote:
With regards to publisher certificates, the team are transitioning to using Microsoft's Trusted Signing, because of that, the installer is currently signed with two certificates, with the MS Trusted Signing one being the second certificate. The first certificate is nearing expiration and will be removed from the installer in the near future (according to the Development team this will be end of this month or early next month).
It's possible that AppLocker currently may not support dual certificates (they have supported it in the past), it may be rejecting the first certificate due to it nearing expiration, or simply fails to recognize publisher rules when dual-signed binaries are involved. In the interim you'll likely need to use hash rules for the 1Password app in order to allow it with AppLocker. Although I don't have a specific timeline to share or can't make any promises as the landscape may change, given regular update cadence I expect no more than the next two updates will contain dual certificates.
