sharpetronics/liboqs
1
0
Fork 0
mirror of https://github.com/open-quantum-safe/liboqs.git synced 2025-12-07 00:02:12 -05:00
Code Issues Projects Releases Wiki Activity

Point README to coding conventions wiki page.

Browse Source
This commit is contained in:
Douglas Stebila 2016-09-12 14:24:58 -04:00 committed by GitHub
parent 6e2db4028e
commit ae9d5cde35
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -49,7 +49,7 @@ We hope OQS will provide a framework for many post-quantum implementations.
In the immediate term, if you have feedback on our API ([kex.h](https://github.com/open-quantum-safe/liboqs/blob/master/src/kex/kex.h) or [rand.h](https://github.com/open-quantum-safe/liboqs/blob/master/src/rand/rand.h)), please contact us so we can ensure our API covers a wide range of implementation needs.
If you have or are writing an implementation of a post-quantum key exchange algorithm, we hope you will consider making an implementation that meets our API so that others may use it and would be happy to discuss including it directly in liboqs.
If you have or are writing an implementation of a post-quantum key exchange algorithm, we hope you will consider making an implementation that meets our API so that others may use it and would be happy to discuss including it directly in liboqs. Please take a look at our [coding conventions](https://github.com/open-quantum-safe/liboqs/wiki/Coding-conventions).
If you would like to use liboqs in an application-level protocol, please get in touch and we can provide some guidance on options for using liboqs.
@ -78,7 +78,6 @@ We plan to be making the following updates over the next month:
- Benchmarking scripts for key exchange algorithms
- Detailed Doxygen documentation for existing API and public functions
- Modular build system
- Coding guidelines
Over the next few months, we plan to be making the following updates: