DASCA
/
DASCA
2
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
DASCA combines dynamic and static techniques for analysing code for finding security (i.e., vulnerabilities), safety, or reliability problems.
288 Commits 1 Branch 0 Tags 8.2 MiB
Java 72%
Scala 23.5%
Gradle 2.2%
HTML 1.9%
Groovy 0.4%
Go to file
Achim D. Brucker 6137968cd1 Cleanup: dependencies. 2018-10-26 21:33:08 +01:00
externals Updated WALA reference. 2017-11-14 05:42:20 +00:00
src Cleanup: dependencies. 2018-10-26 21:33:08 +01:00
.gitignore Ignore cache directories. 2018-10-26 21:32:31 +01:00
.gitmodules Make submodule externals/WALA tracking master. 2016-08-20 10:48:55 +01:00
CITATION Added ESSoS 2016 publication. 2016-07-28 23:51:21 +01:00
LICENSE Initial commit 2015-05-30 23:28:28 +02:00
README.md Documented PDE and JSDT requirements. 2018-05-05 06:58:47 +01:00

README.md

DASCA

Installation

Prerequisites

Checkout

Note that this repository imports WALA as a submodule. Thus, you either need to recursively clone this repository, e.g.,

git clone --recursive https://git.logicalhacking.com/DASCA/DASCA.git

or execute git submodule update --init --recursive after cloning the repository.

Resolving external dependencies

  • Ensure that the environment variable ANDROID_HOME is set correctly and that the Android SDK has API 19 installed, i.e., ${ANDROID_HOME}/platforms/android-19/android.jar should be a valid path.
  • Install apktool_2.3.0.jar into your local maven repository:
cd $(mktemp -d)
wget https://bitbucket.org/iBotPeaches/apktool/downloads/apktool_2.3.0.jar
mvn install:install-file -Dfile=apktool_2.3.0.jar -DgroupId=apktool -DartifactId=apktool -Dpackaging=jar -Dversion=2.3.0

WALA configuration

DASCA (and the underlying WALA setup) is tested with Java version 8. If DASCA is installed using Java 8, there should be no need for updating the WALA configuration.

If you experience problems or want to optimize the performance (e.g., by analyzing the programs based on a different Java version), you might need to configure the location of the Java JDK. The JDK used as part of the static analysis is configured in the wala.properties file, e.g.

cd DASCA/
echo "java_runtime_dir = <PATH-TO-JDK>" >> externals/WALA/com.ibm.wala.core/dat/wala.properties

Don't forget to adjust the path to the Java JDK accordingly, i.e., the <PATH-TO-JDK> should point to the directory containing the file rt.lib.

How to Compile

First check that the variable JAVA_HOME is configured correctly, e.g.:

export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64

Second, resolve the dependencies using maven:

cd src/com.logicalhacking.dasca.parent/
mvn -P wala clean verify -DskipTests=true

After this, all projects can be imported into a fresh Eclipse workspace using File -> Import -> Maven -> Existing Maven Projects:

  1. Select the DASCA src folder as source for the import
  2. Import all offered projects (WALA and DASCA)

While some WALA projects may contain compilation errors, all DASCA projects (i.e., com.logicalhacking.dasca.*) should compile without errors.

Team

Main contact: Achim D. Brucker

Contributors

License

This project is licensed under the Eclipse Public License 1.0.

Publications