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

Blacklisting/whitelisting directory #23

Closed
jdziat opened this issue Sep 12, 2015 · 4 comments
Closed

Blacklisting/whitelisting directory #23

jdziat opened this issue Sep 12, 2015 · 4 comments
Assignees

Comments

@jdziat
Copy link

jdziat commented Sep 12, 2015

is it possible to block or grant execution based off of where an executable is stored?

@russellhancox
Copy link
Collaborator

It can allow based on a path using a regex. The config key WhitelistRegex controls this (which can only be set when santad is not running).

I could add an equivalent for blacklisting by path if it would be useful for you.

@jdziat
Copy link
Author

jdziat commented Sep 12, 2015

That would be great

On Sat, Sep 12, 2015 at 12:46 PM, google/santa
reply@reply.github.com
wrote:
It can allow based on a path using a regex. The config key WhitelistRegex
controls this (which can only be set when santad is not running).

I could add an equivalent for blacklisting by path if it would be useful for
you.


Reply to this email directly or view it on GitHub
[https://github.com//issues/23#issuecomment-139796211] .[https://github.com/notifications/beacon/ABITygTOGRyJqovqYPp_hDkW6Ott7gN5ks5oxE5RgaJpZM4F8RYU.gif]

@sincerelyjoshin
Copy link

+1, but would love to see blacklisting available for all executables stored in specific directory. functionality similar to mcxalr.

@russellhancox
Copy link
Collaborator

Fixed with 5b0e550, which will be included in the 0.9.1 release (which I'm cutting now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants