зеркало из https://github.com/github/codeql.git
Add change notes
This commit is contained in:
Родитель
dcdb5299f0
Коммит
8e325ead91
|
@ -26,10 +26,10 @@ The following changes in version 1.24 affect C/C++ analysis in all applications.
|
||||||
|
|
||||||
## Changes to libraries
|
## Changes to libraries
|
||||||
|
|
||||||
* The data-flow library has been improved when flow through functions needs to be
|
* The data-flow library has been improved, which affects and improves some security queries. The improvements are:
|
||||||
combined with both taint tracking and flow through fields allowing more flow
|
- Track flow through functions that combine taint tracking with flow through fields.
|
||||||
to be tracked. This affects and improves some security queries, which may
|
- Track flow through clone-like functions, that is, functions that read contents of a field from a
|
||||||
report additional results.
|
parameter and stores the value in the field of a returned object.
|
||||||
* Created the `semmle.code.cpp.models.interfaces.Allocation` library to model allocation such as `new` expressions and calls to `malloc`. This in intended to replace the functionality in `semmle.code.cpp.commons.Alloc` with a more consistent and useful interface.
|
* Created the `semmle.code.cpp.models.interfaces.Allocation` library to model allocation such as `new` expressions and calls to `malloc`. This in intended to replace the functionality in `semmle.code.cpp.commons.Alloc` with a more consistent and useful interface.
|
||||||
* Created the `semmle.code.cpp.models.interfaces.Deallocation` library to model deallocation such as `delete` expressions and calls to `free`. This in intended to replace the functionality in `semmle.code.cpp.commons.Alloc` with a more consistent and useful interface.
|
* Created the `semmle.code.cpp.models.interfaces.Deallocation` library to model deallocation such as `delete` expressions and calls to `free`. This in intended to replace the functionality in `semmle.code.cpp.commons.Alloc` with a more consistent and useful interface.
|
||||||
* The new class `StackVariable` should be used in place of `LocalScopeVariable`
|
* The new class `StackVariable` should be used in place of `LocalScopeVariable`
|
||||||
|
|
|
@ -29,10 +29,10 @@ The following changes in version 1.24 affect C# analysis in all applications.
|
||||||
|
|
||||||
## Changes to libraries
|
## Changes to libraries
|
||||||
|
|
||||||
* The data-flow library has been improved when flow through methods needs to be
|
* The data-flow library has been improved, which affects and improves most security queries. The improvements are:
|
||||||
combined with both taint tracking and flow through fields allowing more flow
|
- Track flow through methods that combine taint tracking with flow through fields.
|
||||||
to be tracked. This affects and improves most security queries, which may
|
- Track flow through clone-like methods, that is, methods that read contents of a field from a
|
||||||
report additional results.
|
parameter and stores the value in the field of a returned object.
|
||||||
* The taint tracking library now tracks flow through (implicit or explicit) conversion operator calls.
|
* The taint tracking library now tracks flow through (implicit or explicit) conversion operator calls.
|
||||||
* [Code contracts](https://docs.microsoft.com/en-us/dotnet/framework/debug-trace-profile/code-contracts) are now recognized, and are treated like any other assertion methods.
|
* [Code contracts](https://docs.microsoft.com/en-us/dotnet/framework/debug-trace-profile/code-contracts) are now recognized, and are treated like any other assertion methods.
|
||||||
* Expression nullability flow state is given by the predicates `Expr.hasNotNullFlowState()` and `Expr.hasMaybeNullFlowState()`.
|
* Expression nullability flow state is given by the predicates `Expr.hasNotNullFlowState()` and `Expr.hasMaybeNullFlowState()`.
|
||||||
|
|
|
@ -25,10 +25,10 @@ The following changes in version 1.24 affect Java analysis in all applications.
|
||||||
|
|
||||||
## Changes to libraries
|
## Changes to libraries
|
||||||
|
|
||||||
* The data-flow library has been improved when flow through methods needs to be
|
* The data-flow library has been improved, which affects and improves most security queries. The improvements are:
|
||||||
combined with both taint tracking and flow through fields allowing more flow
|
- Track flow through methods that combine taint tracking with flow through fields.
|
||||||
to be tracked. This affects and improves most security queries, which may
|
- Track flow through clone-like methods, that is, methods that read contents of a field from a
|
||||||
report additional results.
|
parameter and stores the value in the field of a returned object.
|
||||||
* Identification of test classes has been improved. Previously, one of the
|
* Identification of test classes has been improved. Previously, one of the
|
||||||
match conditions would classify any class with a name containing the string
|
match conditions would classify any class with a name containing the string
|
||||||
"Test" as a test class, but now this matching has been replaced with one that
|
"Test" as a test class, but now this matching has been replaced with one that
|
||||||
|
|
Загрузка…
Ссылка в новой задаче