Skip to content

Commit

Permalink
Merge pull request #43 from svenfeld/add_change_to_trigger_action
Browse files Browse the repository at this point in the history
Update _index.md
  • Loading branch information
schlichtig committed Jun 7, 2024
2 parents bf6dc99 + 64378d2 commit 6a2ab0b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/documentation/crysl/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Both [CogniCrypt<sub>GEN</sub>](/cognicrypt/documentation/codegen) and [CogniCry

## Syntax of the Domain-Specific Language CrySL

Rules in CogniCrypt are written in *CrySL*. *CrySL* is a domain-specific language for the specification of correct cryptography API uses in Java. The Eclipse plugin CogniCrypt ships with an XText editor that supports the *CrySL* syntax. *CrySL* generally encodes a white-list approach and specifies how to *correctly* use crypto APIs. We discuss some of the most important concepts of the rule language here, the [research paper](http://drops.dagstuhl.de/opus/volltexte/2018/9215/pdf/LIPIcs-ECOOP-2018-10.pdf) provides more detailed insights on the language. CogniCrypt ships with a default rule set for the [Java Cryptographic Architecture (JCA)](https://docs.oracle.com/en/java/javase/14/security/java-cryptography-architecture-jca-reference-guide.html). At the bottom of this page, you may find a description of this rule set. On top of this rule set, rule sets for [BouncyCastle](https://www.bouncycastle.org/documentation.html), both for its lightweight API as well as JCA provider, and [Google Tink](https://github.com/google/tink) are available for download from within the CogniCrypt preferences. Custom rules may also be added.
Rules in CogniCrypt are written in *CrySL*. *CrySL* is a domain-specific language for the specification of correct cryptography API uses in Java. The Eclipse plugin CogniCrypt ships with an XText editor that supports the *CrySL* syntax. *CrySL* generally encodes a white-list approach and specifies how to *correctly* use crypto APIs. We discuss some of the most important concepts of the rule language here, the [research paper](http://drops.dagstuhl.de/opus/volltexte/2018/9215/pdf/LIPIcs-ECOOP-2018-10.pdf) provides more detailed insights on the language. CogniCrypt ships with a default rule set for the [Java Cryptographic Architecture (JCA)](https://docs.oracle.com/en/java/javase/14/security/java-cryptography-architecture-jca-reference-guide.html). At the bottom of this page, you find a description of this rule set. On top of this rule set, rule sets for [BouncyCastle](https://www.bouncycastle.org/documentation.html), both for its lightweight API as well as JCA provider, and [Google Tink](https://github.com/google/tink) are available for download from within the CogniCrypt preferences. Custom rules may also be added.

Each *CrySL* rule is a specification of a single Java class. A short example of a *CrySL* rule for `javax.crypto.Cipher` is shown below.

Expand Down

0 comments on commit 6a2ab0b

Please sign in to comment.