kris
/
xmss-KAT-generator
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
75 Commits
1 Branch
488 KiB
Tree: 270e6cd753
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '270e6cd753'
${ noResults }
xmss-KAT-generator/README.md

README.md 1.5 KiB
Raw Normal View History

Clarify compile-time parameters in README
7 years ago
​
​
​
Revert to using runtime-only parameter struct Using global defines for parameters (as seems to be typical in academic crypto code) does not play nice with multithreading at all.
7 years ago
Mention branch-specific purpose on README
7 years ago
Clarify status of run-time parameter selection
7 years ago
​
​
Simplify licensing using LICENSE file
7 years ago
Document and simplify library usage
7 years ago
​
​
​
Simplify licensing using LICENSE file
7 years ago
​
​
 1234567891011121314151617 
  1. ## XMSS reference code

  2. 

  3. This repository contains the reference implementation that accompanies the Internet Draft _"XMSS: Extended Hash-Based Signatures"_, [`draft-irtf-cfrg-xmss-hash-based-signatures`](https://datatracker.ietf.org/doc/draft-irtf-cfrg-xmss-hash-based-signatures/).

  4. 

  5. This reference implementation supports all parameter sets as defined in the Draft at run-time (specified by prefixing the public and private keys with a 32-bit `oid`). Implementations that want to use compile-time parameter sets can remove the `struct xmss_params` function parameter.

  6. 

  7. _While the behavior of the code in this repository is supposed to be stable, the API is not yet fully complete. In particular, the wrapper for run-time parameters does not yet support the back-end functions that make use of BDS traversal (TODO). We will also add more extensive test functionality, making it easier to compare to other XMSS implementations (TODO)._

  8. 

  9. _When using the current code base, please be careful, expect changes and watch this document for further documentation._

  10. 

  11. ### Dependencies

  12. 

  13. For the SHA-2 hash functions (i.e. SHA-256 and SHA-512), we rely on OpenSSL. Make sure to install the OpenSSL development headers. On Debian-based systems, this is achieved by installing the OpenSSL development package `libssl-dev`.

  14. 

  15. ### License

  16. 

  17. This reference implementation was written by Andreas Hülsing and Joost Rijneveld. All included code is available under the CC0 1.0 Universal Public Domain Dedication.