Skip to content
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

Error pops up when discovering rules in the C:\Windows\System32 dir #3

Open
CalebAlbers opened this issue Jan 14, 2021 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@CalebAlbers
Copy link
Contributor

PowerShell prompts that are launched as Administrator default to C:\Windows\System32 as the working directory. When OCCAM attempts to discovery .Rule.ps1 files, it does so recursively, which can return errors when attempting to search parts of System32 that the PowerShell process does not have access to.

We can either:

  1. Warn users when running in C:\Windows\System32 that they need to run OCCAM somewhere else
  2. Add a special case that does a non-recursive search in C:\Windows\System32
  3. Catch and silence the errors when in C:\Windows\System32
@CalebAlbers CalebAlbers added the enhancement New feature or request label Jan 14, 2021
@CalebAlbers CalebAlbers self-assigned this Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant