-
Notifications
You must be signed in to change notification settings - Fork 24
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
Rename project? #283
Comments
One other fun ideal: |
I had a few ideas:
It's hard to find a clever way to use |
I really like |
Unfortunately, malcontent seems to be a package that ships with many Linux distributions already. Maybe 'malintent'? It doesn't have the same ring to it though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When this project first began, it focused on enumerating binaries' capabilities. It's since grown in two ways:
Since we're still pre-v1.0, I think it's a good time to consider whether the project's name is still appropriate. I'd like something that references the usage of the program.
I'm opening the floor to alternative names. The only ones ideas that have come to me so far are
malcapz
andbadcapz
.Alternatively, maybe we just keep the name as it is. We still have rules in place to detect non-malicious behaviors that could be used for defining
seccomp(2)
profiles, but it's not been fully implemented.The text was updated successfully, but these errors were encountered: