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

Issue #115: provideIntegrity missing on Actor and Asset class #116

Merged
merged 2 commits into from
Sep 29, 2020
Merged

Conversation

izar
Copy link
Collaborator

@izar izar commented Sep 29, 2020

No description provided.

@@ -1144,6 +1145,8 @@ class Actor(Element):
checksDestinationRevocation = varBool(False, doc="""Correctly checks the revocation status
of credentials used to authenticate the destination""")
isAdmin = varBool(False)
# should not be settable, but accessible
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why it should not be settable? An actor can sign requests

Copy link
Collaborator

Choose a reason for hiding this comment

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

How about moving providesIntegrity to the base class?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

an actor signs a request via a process on their behalf, which should be looked at as a Process. I want to keep the Actor semantically separated (right now it is not) from the process it uses in order to allow us to use it for privacy threats later on.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Using a plain bool doesn't solve this anyway. I think we should add not target.source.oneOf(Actor) or not target.source.providesIntegrity (and same for sink) in the thread condition.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

we probably need to implement a "unless_target()" filter or something for these cases.
you mean the plain bool doesn't solve the existing-but-not-settable part, or is there something beyond that I am not seeing here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

TODO: revisit Element/Asset and how the attributes are inherited, clean up inheritance and come up with a cleaner, better method to treat these going forward.

@izar izar merged commit 97fadcb into master Sep 29, 2020
@izar izar deleted the 115 branch March 18, 2021 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Crash on checking threat attributes that are not in current object while generating report
2 participants