Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
Benoit Viguier
coq-verif-tweetnacl
Commits
24c1c7db
Commit
24c1c7db
authored
Oct 01, 2019
by
Freek Wiedijk
Browse files
why indent the abstract?
parent
1dcdac35
Changes
1
Hide whitespace changes
Inline
Side-by-side
paper/0_abstract.tex
View file @
24c1c7db
% \subsection*{Abstract}
\begin{abstract}
We formally prove that the C implementation of
the X25519 key exchange protocol
in the TweetNaCl library is correct.
We prove both that it correctly implements the protocol from
Bernstein's 2006 paper, as standardized in RFC 7748,
as well that there are no undefined behaviors
like arithmetic overflows
and array out of bound errors.
We also formally prove, based on the work of Bartzia and Strub,
that X25519 is mathematically correct
in that it correctly computes multiplication in the elliptic curve
Curve25519.
We formally prove that the C implementation of
the X25519 key exchange protocol
in the TweetNaCl library is correct.
We prove both that it correctly implements the protocol from
Bernstein's 2006 paper, as standardized in RFC 7748,
as well that there are no undefined behaviors
like arithmetic overflows
and array out of bound errors.
We also formally prove, based on the work of Bartzia and Strub,
that X25519 is mathematically correct
in that it correctly computes multiplication in the elliptic curve
Curve25519.
The proofs are all computer-verified using the Coq theorem prover.
To establish the link between C and Coq we use the
Verified Software Toolchain (VST).
The proofs are all computer-verified using the Coq theorem prover.
To establish the link between C and Coq we use the
Verified Software Toolchain (VST).
\end{abstract}
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment