diff --git a/content/documentation/_index.md b/content/documentation/_index.md index 7a0d24c..473a16f 100644 --- a/content/documentation/_index.md +++ b/content/documentation/_index.md @@ -3,7 +3,7 @@ title: "Documentation" date: 2018-09-03T19:48:11+02:00 --- -CogniCrypt comprises two features to assist in the usage of cryptographic APIs. First, its code generator CogniCryptGEN may generate code wrappers around cryptographic APIs that implement programming tasks involving cryptography. Currently, CogniCryptGEN supports code generation for five such tasks. CogniCrypt also employs a suite of static code analyses CogniCryptSAST constantly running the background and checking for misuses of cryptographic APIs. Thanks to its tight integration with Eclipse, developers are being alerted of misuses by means of regular Eclipse error markers. Both CogniCryptGEN and CogniCryptSAST are parameterized and configured by rules in the specification languge CrySL. For more details on all three, please refer to their corresponding tutorial pages: +CogniCrypt comprises two features to assist in the usage of cryptographic APIs. First, its code generator CogniCryptGEN may generate code wrappers around cryptographic APIs that implement programming tasks involving cryptography. Currently, CogniCryptGEN supports code generation for five such tasks. CogniCrypt also employs a suite of static code analyses CogniCryptSAST constantly running the background and checking for misuses of cryptographic APIs. Thanks to its tight integration with Eclipse, developers are being alerted of misuses by means of regular Eclipse error markers. Both CogniCryptGEN and CogniCryptSAST are parameterized and configured by rules in the specification language CrySL. For more details on all three, please refer to their corresponding tutorial pages: * [CrySL - Usage Specifications for Cryptographic APIs](crysl) @@ -19,9 +19,11 @@ Through its preference menu, CogniCrypt may be configured in several different w Preferences -* `Source of CrySL Rules` : Users may select in this table which CrySL rules CogniCrypt should include in its analyis and code generation. By default, there are three rule sets, one for the JCA, one for BouncyCastle, and one for Google Tink. However, users may add new ruleset through the button below the table. +* `Source of CrySL Rules` : Users may select in this table which CrySL rules CogniCrypt should include in its analysis and code generation. By default, there are three rule sets, one for the JCA, one for BouncyCastle, and one for Google Tink. However, users may add new ruleset through the button below the table. -* `Select Custom Rules` : As explained [here](crysl), users may write their own custom CrySL rules in CogniCrypt directly if they do not want to specify a complete rule set. For CogniCrypt to use these custom rules, a user has to enable this option here. +* `Select Custom Rules` : As explained [here](crysl), users may write their own custom CrySL rules in CogniCrypt directly if they do not want to specify a complete ruleset. For CogniCrypt to use these custom rules, a user has to enable this option here. Users may add their custom rules via a URL (Add Remote Ruleset) or from their local machine (Add Local Ruleset). + +* `Load Rules From Analyzed Project's Directory` : When this is enabled, CogniCryptSAST would automatically look into the analyzed project directory for CrySL rules. * `Enable Automated Analysis when Saving` : When this option is enabled, CogniCryptSAST executes whenever a source-code file is saved. Otherwise, the user has to trigger CogniCryptSAST manually @@ -31,8 +33,10 @@ Through its preference menu, CogniCrypt may be configured in several different w * `Include Dependencies to Analysis` : When enabled, CogniCryptSAST not only checks the application code directly, but any library code the application code depends on. +* `Suppress warnings related to legacy code generated by CogniCrypt` : If a user chooses to support legacy systems in the CogniCryptGEN wizard, they might not opt for the highest security requirements. Therefore, they can choose a less secure configuration by enabling this checkbox. + * `Call-graph construction algorithm` : Users may select which algorithm CogniCryptSAST uses for call-graph construction. -* `Error-Warning Types` : By means of these options, users may set the severity CogniCryptSAST's error types are reported with. They may chosse between Error, Warning, Info, or Ignore. +* `Error-Warning Types` : By means of these options, users may set the severity CogniCryptSAST's error types are reported with. They may choose between Error, Warning, Info, or Ignore. * `Persist Code-generation Configuration` : If enabled, CogniCryptGEN stores the configuration it uses to generate code for a cryptographic use case into the root folder of the user's project. diff --git a/content/documentation/preferences.jpg b/content/documentation/preferences.jpg new file mode 100644 index 0000000..cafba32 Binary files /dev/null and b/content/documentation/preferences.jpg differ diff --git a/content/documentation/preferences.png b/content/documentation/preferences.png deleted file mode 100644 index 0b8a3c2..0000000 Binary files a/content/documentation/preferences.png and /dev/null differ