Skip to content

Fallback to AppLocker after WldpCanExecuteFile #24912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Mar 24, 2025

Conversation

SeeminglyScience
Copy link
Collaborator

PR Summary

After #17247, AppLocker was no longer being checked if the Windows API WldpCanExecuteFile was present. With the changes in this PR, fallback to AppLocker will once again occur if WldpCanExecuteFile did not return Blocked or AllowedConstrained.

PR Context

PR Checklist

@SeeminglyScience
Copy link
Collaborator Author

/azp run

Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@TravisEz13 TravisEz13 closed this Jan 31, 2025
@TravisEz13 TravisEz13 reopened this Jan 31, 2025
@TravisEz13
Copy link
Member

/azp run

Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@TravisEz13
Copy link
Member

/azp run powershell-ci-macos

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@TravisEz13
Copy link
Member

/azp run PowerShell-Windows-Packaging-CI

Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Review - Needed The PR is being reviewed label Feb 11, 2025

return modernMode switch
{
SystemScriptFileEnforcement.Block => SystemEnforcementMode.Enforce,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't/shouldn't this not be the case as per the above and it would be better to throw the exception in the default branch?

@TravisEz13 TravisEz13 added the CL-Engine Indicates that a PR should be marked as an engine change in the Change Log label Mar 11, 2025
@SeeminglyScience
Copy link
Collaborator Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@daxian-dbw daxian-dbw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@TravisEz13 TravisEz13 merged commit dc0f399 into PowerShell:master Mar 24, 2025
40 of 42 checks passed
@SeeminglyScience SeeminglyScience deleted the fix-applocker-fallback branch March 24, 2025 21:13
Copy link
Contributor

microsoft-github-policy-service bot commented Mar 24, 2025

📣 Hey @SeeminglyScience, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Review - Needed The PR is being reviewed label Mar 24, 2025
TravisEz13 added a commit to TravisEz13/PowerShell that referenced this pull request Mar 24, 2025
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
pwshBot pushed a commit to pwshBot/PowerShell that referenced this pull request Apr 10, 2025
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
Sysoiev-Yurii pushed a commit to Sysoiev-Yurii/PowerShell that referenced this pull request May 12, 2025
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BackPort-7.4.x-Done Backport-7.5.x-Migrated CL-Engine Indicates that a PR should be marked as an engine change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants