-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Create a dataflow instance specifically for the Serializability library #6216
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
Create a dataflow instance specifically for the Serializability library #6216
Conversation
|
Is number 5 used for anything else at the moment? Otherwise we could consider just renaming it (and possibly renaming number 6 as that is also for a reserved use case IIRC). We have plenty of copies already, so might as well try to keep the number down. |
|
They do all have other users, though few in number. |
|
LGTM, but needs resync. |
java/ql/src/semmle/code/java/frameworks/google/GoogleHttpClientApi.qll
Outdated
Show resolved
Hide resolved
java/ql/src/semmle/code/java/frameworks/jackson/JacksonSerializability.qll
Outdated
Show resolved
Hide resolved
Otherwise because this dataflow instance populates AdditionalTaintStep there is an ever-present danger that a user will stumble into creating a recursive configuration, or at least that by using DataFlow5::Configuration for any other purpose they will needlessly recalculate the Serializability dataflow results.
Co-authored-by: Anders Schack-Mulligen <aschackmull@users.noreply.github.com>
e6d9c33 to
afa8278
Compare
|
Accepted suggestions and rebased |
|
CI still looks very red for some reason. |
|
Looks like there were concurrent changes to |
Otherwise because this dataflow instance populates AdditionalTaintStep there is an ever-present danger that a user will stumble into creating a recursive configuration, or at least that by using DataFlow5::Configuration for any other purpose they will needlessly recalculate the Serializability dataflow results.