Skip to content

Releases: franceme/cryptoguard

V03.08.00

29 Oct 02:59
Compare
Choose a tag to compare
  • Added the *.in file into the source file (not on the dependency path yet)

    • The input source file does not support classpaths currently
  • Added a flag to not kill the jvm at the end of each test

  • Expanded logging

  • Enhanced and fixed Java Class tests/validation

    • Patched the Java Class fixes to not stop the other test paths
  • Deprecated the auxclasspath argument in favor of pushing it into both source/dependency

  • hashes
    c9a202f454f37b9c975252f1a97570bc1ce7dbc2dc941e22c3787282d34a74f97663340cf9431b7aa47d9fa36ee76ed67d05db80fae346ed599d6ce72fef22c3 cryptoguard.jar
    d53efecf899a58612d87803aeec648c54e54b8a09f6cfe01d07ebeaaa3cb169bacc87f91b7f1226f34d093b9e8406dac252261434bd6256c470201745a52fee0 cryptoguard.tar

V03.07.05

23 Sep 21:40
Compare
Choose a tag to compare
V03.07.05 Pre-release
Pre-release
  • Added flag to disable automatically killing the jvm

  • Tweaked some of the internal functionality for Testing

  • Source/Class files testing still don't work

  • Added the enhanced input

  • Enabled the input.in file (passing in files via 1 input file).

  • Added sanity tests to ensure input.in works

  • hashes
    1e9f7808b27c59f828554db7fec91e34709736ee171cd30aa2d4d4bba62d76889b2a52f1f511bd8d9c44ba684ed8c35e52543501c219dfd3bba4d6a1c413f82d cryptoguard.jar
    532a3033c33f8e1cc19c03be2cb476204932140eb69df6f63eb0c8029e3de484b29905ceb8e4bcfd2e4df4f86d7169d8d783a2b3c4cdb05007476ed9536fa687 cryptoguard.tar

V03.07.01

08 Sep 21:12
f1f6f85
Compare
Choose a tag to compare
V03.07.01 Pre-release
Pre-release
  • Ran the javadoc:fix
  • Fixed the Makefile to use java 8
  • Formatted the project
  • Disabled all of the current tests that are failing, to be fixed

*sha512
f579de198a634b121ccc82f65241f154f24320fd724fa9ed898024433ca59a8ccfc6abeed6af17210714b0220d0d1831f57fe74d8597ec09bcf726f60a766104 cryptoguard.jar
912a966a0b165aa0aa37de418dc825439ba02210116a4ea6c0e0268901c492019c5d50b668a5082eb946d6670d36c35b5b587a682e4f09bb10b4dd6f89f3a258 cryptoguard.tar

V03.07.00

04 Sep 22:59
23282bb
Compare
Choose a tag to compare
  • Added initial wave of heuristics into the program
    heuristics have been added into each of the structures
  • Gradle release now creates a local tar file
  • Gradle release also creates a release file (with jar and tar) and
    writes out the sha512 for each
  • Tests have been updated to the "builder" method
  • Added internal verify class paths Utils method

sha512sums
445c2ef012ef62b3e4c5a7d8aedfbd7e4dfc9cb06b4876fa172b2c34f6828a2986c8220a782573f7aa7bb12d03d153a1db92baeded705a0c56a21fddeae75ef8 cryptoguard.jar
eb7ba4f9323aea5e3718dd77b1392e0a706a8d6e0cddc40a94ba3748a259e5560927d942ede6f8b4118cd098ba18ceb87a1147d6c5682bfbaef505e8f4100717 cryptoguard.tar

V03.06.01 - PATCH RELEASE

17 Jun 01:50
Compare
Choose a tag to compare
Pre-release

This patch release addresses the default values found for marshalling the Methods and Location fields.

If there is an issue with the Method found it'd previously be UNKNOWN, now it has been filtered and won't be shown.

Within the BugLocation field, the default values (0) were pushed through the marshaller (into the output).
These are filtered out.

V03.06.00

03 May 20:21
77a4e36
Compare
Choose a tag to compare

This minor release contains a new "Default" output format, that replaces the Legacy output format as the default format.
This also contains the start of retrieving the target name/version, furthering the logging implementation, and a confirmation to overwrite an existing output file.

sha512| ab738fd8bed2235ecf558bbe007ed59bb7a70e95b981dbc31a879477b5adb451a95d950951cf420d5718a184289326a7ac794b4e213ec2b0f945cc5e579bf3af cryptoguard.jar

V03.05.00

29 Apr 15:04
d4c9e9e
Compare
Choose a tag to compare

Cutting V03.05.00, this contains the following updates,

  • Logging has been partially introduced
  • Readme has been upgraded
  • Makefile now properly points to the sample tests
  • Makefile has been upgraded (proper info out statements)
  • Rolled the used Soot version back to a stable version
  • Merged latest core upgrade
  • Updated Scarf Schema

sha512:
38aa2ca15aaaed85e8922c6a2bc5aba0412fcdd1c0b4ceb8dee1177e23ee0a18223966267e6a4a77fd8ca560a40686fd7ae549489b724d8715179017dd9f9e04 cryptoguard.jar

V03.04.00

08 Apr 19:50
668b202
Compare
Choose a tag to compare
  • The version/name is now properly returned

  • The Unit Test Issues were solved

  • The project tree was cleansed

  • The name was updated

  • sha256 of cryptoguard.jar: 32d231cb4fb4d024a0bf5052700359c289b0241a845c67797b19a62cf85d5679

V03.03.02

16 Mar 03:39
847aade
Compare
Choose a tag to compare

Included several of the high levels updates

  • Added Java File Scanning
  • Updated Core Engine
  • Fixed ScarfXML Output
  • ScarfXML Output takes in a property file
  • The Argument input is heavily enhanced
  • Streaming is now enabled
  • Steaming and block output are have the same parent with strong abstraction

Sha512 of CryptoGuard.jar

  • 4e11cbc000ae3f20dd3a9b29e27f30eb6c8bf414fe74a7aa0e0e62eb72dbb301c21cd2079393d5ede256a5d8754a7e151ad42005a9249a34f14e50e304e2b057

Corresponding to the V01.01 milestone

07 Nov 16:57
Compare
Choose a tag to compare
Pre-release

Added the project version, cleaned the dependencies and set the smell of the code.