We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Formal reasoning about the security of Amazon Web Services Byron Cook http://www0.cs.ucl.ac.uk/staff/b.cook/CAV18_invited.pdf
It mention a long list of tools:
External tools that we use include Boogie [1], Coq [4], CBMC [2], CVC4 [5], Dafny [6], HOL-light [8], Infer [9], OpenJML [10], SAW [13], SMACK [14], Souffle [37], TLA+ [15], VCC [16], > and Z3 [17].
I'm not sure what's the best format to include the information so I didn't create a pull request. I'll leave it for @ligurio to decide :)
The text was updated successfully, but these errors were encountered:
Yep, it's worth to add. Thanks! @fracting could you create a PR?
Sorry, something went wrong.
Sorry, I'm not sure what's the best format.
Do you prefer:
TLA+ How Amazon Web Services Uses Formal Methods, Use of Formal Methods at Amazon Web Services CBMC Model Checking Boot Code from AWS Data Centers Various other toolsFormal reasoning about the security of Amazon Web Services
TLA+
CBMC
Various other tools
Or do you prefer a long list of tools in details, like:
TLA+ How Amazon Web Services Uses Formal Methods, Use of Formal Methods at Amazon Web Services CBMC Model Checking Boot Code from AWS Data Centers Boogie, Coq, CBMC, CVC4, Dafny, HOL-light, Infer, OpenJML, SAW, SMACK, Souffle, TLA+, VCC, Z3Formal reasoning about the security of Amazon Web Services
Boogie, Coq, CBMC, CVC4, Dafny, HOL-light, Infer, OpenJML, SAW, SMACK, Souffle, TLA+, VCC, Z3
Or any other better solution?
I think it's nice to have https://aws.amazon.com/security/provable-security/ in the table as well. I'm just not sure how to organize the information.
No branches or pull requests
Formal reasoning about the security of Amazon Web Services
Byron Cook
http://www0.cs.ucl.ac.uk/staff/b.cook/CAV18_invited.pdf
It mention a long list of tools:
I'm not sure what's the best format to include the information so I didn't create a pull request. I'll leave it for @ligurio to decide :)
The text was updated successfully, but these errors were encountered: