8000 Releases · Guardsquare/proguard-core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Releases: Guardsquare/proguard-core

9.1.10

24 Mar 11:06
Compare
Choose a tag to compare

Java support

  • Update maximum supported Java class version to 68.65535 (Java 24).

Bugfixes

  • Prevent StackOverflowError in ConstantPoolShrinker when visiting a pattern matching switch in java >= 21.

9.1.9

07 Mar 15:29
Compare
Choose a tag to compare

Improved

  • Improve performance of MethodLinker in situations with large number of linked methods in a chain.

9.1.8

17 Feb 08:39
Compare
Choose a tag to compare

Improved

  • Improve runtime of BamTransferRelation.
  • Add a method signature and descriptor parser in the new package proguard.classfile.attribute.signature.

Kotlin support

  • Add support for processing Kotlin 2.1 metadata.

API changes for the dataflow analysis code

This is a continuation of the API changes started in release 9.1.7.

  • Remove JvmValueBamCpaRun in order to simplify the utility code to run the analysis. ValueAnalyzer is the direct replacement, this class has the same behavior as JvmValueBamCpaRun, as long as analyze is called only once.
  • Remove JvmTaintMemoryLocationBamCpaRun in order to simplify the utility code to run the analysis. TaintAnalyzer is the direct replacement, this class has the same behavior as JvmTaintMemoryLocationBamCpaRun, as long as analyze is called only once.
  • Remove the CpaRun infrastructure.
  • Remove MapAbstractStateFactory, WrapperTransferRelation, and other classes that were only used with the tree heap model.
  • Remove StateNames and getStateByName.
  • Refactor several classes taking generic parameters for CfaEdge, CfaNode, and Signature, to not use the generic parameters anymore. They now default to JvmCfaEdge, JvmCfaNode, and MethodSignature.
  • Refactor CPA reached set, waitlist, operators, and all their dependant classes to be parametrized by the type of abstract states of the dataflow analysis. This allows to make the code safe at compile time and avoid unnecessary casts.
  • Move AbortOperator from being a parameter of CpaAlgorithm#run to the ConfigurableProgramAnalysis interface.
  • Move functionalities of LatticeAbstractState to AbstractState. Remove AbstractDomain since the abstract states can now perform directly the isLessOrEqual and join operations without the need of delegation.

Bugfixes

  • Fix semi-lattice properties of MultiTypedReferenceValue's generalize() method
  • Fix integers potentially being used as reference identifier during interprocedural value analysis. This could result in the analysis not reaching a fixed point.
  • Fix JvmTaintTransferRelation#propagateExtraTaints propagating taint incorrectly if the stack contains more than one element.

9.1.7

12 Dec 10:20
Compare
Choose a tag to compare

Bugfixes

  • Make sure injected initialization methods in interfaces have the correct access flags.

Improved

  • InstructionSequenceMatcher now supports matching of primitive array constants.
  • Support propagation of extra specified taints in JvmTaintTransferRelation.
  • Introduce ReflectiveModel and ReflectiveModelExecutor to simplify the creation and analysis of Models.

API improvements

  • Rename CallVisitor to CallHandler and add extra parameters to handle calls accounting for more data.
  • Add ClassUtil.isClassInitializer(String) and ClassUtil.isInstanceInitializer(String).
  • Extend MemberCollectionFilter to accept a Set of any subtype of Member.

API changes

  • Move classes related to Model to the proguard.evaluation.value.object.model package.
  • StringSharer now uses a string pool to share strings, instead of traversing references.

API changes for the dataflow analysis code

There are several changes to the dataflow analysis code with the objective of eliminating unnecessary abstraction and
make its usage easier. This includes:

  • Remove MemoryLocation, use JvmMemoryLocation instead.
  • Make JvmMemoryLocation independent of the type of value contained in the analysis' state. The type of the value now needs only to be provided when calling extractValueOrDefault.
  • Remove all code related to the tree heap model for taint analysis.

9.1.6

22 Aug 15:23
Compare
Choose a tag to compare

Java support

  • Update maximum supported Java class version to 67.65535 (Java 23).

API changes

  • Make CallGraph reconstruction/traversal methods generic in that they now take a Set<MethodSignature> to determine when to stop exploration
  • Delete EntryPoint class

Bugfixes

  • Fix incorrect traversal direction in predecessorsContain.

9.1.5

17 Jul 14:34
Compare
Choose a tag to compare

Bugfixes

  • Prevent unknown enum value for KmVersionRequirementVersionKind exception when processing code compiled with an outdated Kotlin version.
  • Fix UnknownReferenceValue return wrong string format in getType.
  • Fix ReflectionExecutor not updating instance of StringBuilders in fallback result.

API changes

  • Executors do not support MethodSignature wildcards anymore. The assumption from ExecutorLookup is now that all the signatures supported by the executor are declared explicitly in getSupportedMethodSignatures.
  • StringExecutor, ExecutingInvocationUnit, and JvmValueBamCpaRun now need the library class pool as parameter.
  • Calls to InstructionSequenceBuilder.ldc now optionally accept a ConstantVisitor. The visitor will visit the constant that is referenced by the added instruction.

9.1.4

22 May 07:04
bd3ba7f
Compare
Choose a tag to compare

Version 9.1.4

Improved

  • Add support for dynamic dispatch in ExecutorInvocationUnit. This makes it possible to execute methods based on statically observed types of objects, not only based on the type of the used variables.

API changes

  • Remove ExecutorMatcher and change the Executor interface so that it declares supported methods by MethodSignature wildcards instead.
  • Add @Nullable annotations to MethodSignature.

Kotlin support

  • Update Kotlin dependency to 2.0.0 final release version.

Bugfixes

  • Prevent potential NullPointerException when Kotlin property metadata isVar flag does not correctly indicate the presence of a setter.

9.1.3

29 Apr 13:06
Compare
Choose a tag to compare

Version 9.1.3

Kotlin support

  • Add support for processing Kotlin 2.0 metadata.
  • Update to stable version of the Kotlin metadata library.

9.1.2

04 Apr 16:07
eef07d3
Compare
Choose a tag to compare

Java support

  • Update maximum supported Java class version to 66.65535 (Java 22). (#127)

API changes

  • Remove deprecated ReferenceValueFactory, ParticularReferenceValueFactory should be used instead.
  • Deprecate methods in ValueFactory taking an Object as parameter. The alternatives using ParticularObject should be used instead.

Improved

  • Add support for selective parameter reconstruction to define which methods should have their calls evaluated.
  • Refactor ExecutingInvocationUnit to be customizable using executors. Improve checking whether method instance should be replaced in stack and variables.
  • Support execution of methods that operate on 1D arrays of all primitive and reference types with ReflectionExecutor.
  • Use runtime type instead of static type when possible in ExecutingInvocationUnit.
  • Introduce ParticularObject as the value tracked by ParticularReferenceValue. This makes explicit which kind of values can be tracked during the analysis, and introduces the possibility of tracking a model of the values that differ from the actual tracked object.

Bug fixes

  • Improve Kotlin MultiFileFacade metadata assertions to detect uninitialized references.
  • Fix handling of category 2 values in JvmValueTransferRelation to work correctly with ExecutingInvocationUnit.
  • Fix concurrency problems in CallGraph and ValueFactory ids.
  • Fix a bug in ReturnClassExtractor returning the last parameter type instead of null for primitive return values.
  • Fix ExecutorMethodSignatureMatcher trying to mutate an immutable map.
  • Fix TypedReferenceValue.cast() not handling null values correctly.

9.1.1

29 Nov 17:15
38f2a86
Compare
Choose a tag to compare

Version 9.1.1

Bugfixes

  • Enable fix previously behind system property: fix TypedReferenceValue.generalize() not setting mayBeExtension to true when generalizing to common parent type.
  • Avoid printing PartialEvaluator messages when an ExcessiveComplexityException occurs.
  • Fix incorrect writing of flags for type parameters with name annotations.
  • Fix incorrect writing of flags for reified type parameters.
  • Fix model for types and type parameters, removing the incorrect HAS_ANNOTATION common flag.

Improved

  • Enable new PartialEvaluator error message format by default.
  • Add the ability to implement a custom renaming strategy for ClassReferenceFixer.
  • Add new MaxStackSizeComputer to compute the maximum stack size of a code attribute which is more memory efficient than the existing StackSizeComputer.
  • Add IdentifiedArrayReferenceValue.generalize() to maintain ID when applied to two instances with same ID.
0