Changelog

AQL / AQL-System: Changelog

2.0.0

• Moved to Java 17
• Added subjects of interest: Sources, Sinks, Slice, Arguments (see Queries & Questions)
• Changed/Added question ending symbols: ?, ! and .
• Operators must now end with an ending symbol
• New default operators: MINUS, INTERSECT and SIGN
• New FILTER operator options
• Added configurable rules (rules.xml) to allow custom transformations (removed default transformations)
• Added the possibility to attach linenumbers to statements in AQL-Answers
• Reworked graph visualization of AQL-Answers
• Added <androidBuildTools> to configurations
• Introduced default tools for: Sources, Sinks, Intents, IntentFilters, IntentSinks, IntentSources, Arguments (with respect to features used by an app), Permissions
• Introduced default operator for: SIGN
• Added the possibility to use online configurations or receive configurations from AQL-WebServices
• ...

1.2.0

Configuration Upgrades

Along with the release of version 1.2.0 the structure of configurations has changed (see XML Schema Definition file).

The AQL-System now allows to configure external tools:

<tool name="AwesomeDroidExternal" version="1.3.3.7" external="true">
	<priority>1</priority>
	<execute>
		<url>http://awesome.droid.com:1337/AQL-WebService/ask</url>
		<username>droid</username>
		<password>****</password>
	</execute>
	<path>/path/to/directory/for/temporary/files</path>
	<questions>IntraAppFlows</questions>
</tool>

For internal tools the following is required:

<tool name="AwesomeDroidInternal" version="1.3.3.7" external="false">
	<priority>1</priority>
	<execute>
		<run>/path/to/AwesomeDroid/run.sh %MEMORY% %ANDROID_PLATFORMS% %APP_APK%</run>
		<result>/path/to/AwesomeDroid/results/%APP_APK_FILENAME%_result.txt</result>
		<instances>0</instances>
		<memoryPerInstance>4</memoryPerInstance>
	</execute>
	<path>/path/to/AwesomeDroid</path>
	<questions>IntraAppFlow</questions>
</tool>

Thus, the attribute external="false" has to be set and the element <execute> must be specified.

---

Remark: Old configurations had no <execute> element. However, all subelements for internal tools should already be existent.