# NSR_Newest_hash_function
**Repository Path**: tpy123666/NSR_Newest_hash_function
## Basic Information
- **Project Name**: NSR_Newest_hash_function
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No
## Statistics
- **Stars**: 0
- **Forks**: 0
- **Created**: 2021-03-25
- **Last Updated**: 2021-03-25
## Categories & Tags
**Categories**: Uncategorized
**Tags**: None
## README
# NSR_Newest_hash_function
This project is for matched reference log with NSR.
We will not develope SHA3 base code. We just get original code from Keccak Team.
If we have some time, we will change that base code on our own. (If possible..)
SHA2 is an auxiliary tool for verifying implementation conformance.
1. We will find SHA3 hash values and matched that values with NSR due to April 27. --> Clear(April 25)
->Can check hash values result in this web site: https://leventozturk.com/engineering/sha3/
SHA3 stand alone version
SHA3 devide version(init, update, final)
2. Make a HMAC which is SHA3 version due to May 4. --> Clear(May 14)
->Reference site HMAC : https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.198-1.pdf
->Can check HMAC hash values result in this web site: http://www.wolfgang-ehrhardt.de/hmac-sha3-testvectors.html
SHA3 HMAC(Based SHA3 devide version)
3. Make a Hash_DRBG due to MAY 16. --> Clear(June 11)
->Reference site of how to set DRBG: https://github.com/Chronic-Dev/libgcrypt
->Reference site of how to set DRBG: https://tls.mbed.org/ctr-drbg-source-code
->TTAK.KO-12.0190: http://committee.tta.or.kr/data/standard_view.jsp?nowPage=3&pk_num=TTAK.KO-12.0190&commit_code=TC5
->How to install mbed TLS: https://www.lesstif.com/pages/viewpage.action?pageId=29590494
->Recommend to use this web site because TTAK.KO-12.0190 is not perfectly matched which has some bugs: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-90a.pdf
SHA3 DRBG(Based SHA3 stand alone version)
SHA3 DRBG Various values(Based SHA3 stand alone version)
SHA3 DRBG KAT(Based SHA3 stand alone version)
4. Make a HMAC_DRBG due to MAY 23. --> Clear(June 18)
->Reference site HMAC_DRBG: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-90a.pdf
SHA3 HMAC DRBG include various values(Based SHA3 HMAC)
SHA3 HMAC DRBG KAT(Based SHA3 HMAC)
5. Make a PBKDF due to MAY 30. --> Clear(June 26)
->Reference site PBKDF: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-132.pdf
->Reference site PBKDF(Korean ver): http://www.tta.or.kr/data/ttas_view.jsp?totalSu=758&by=desc&order=publish_date&rn=1&pk_num=TTAK.KO-12.0274&nowSu=336
SHA3 HMAC PBKDF(Based SHA3 HMAC)
6. Make a HMAC_KDF due to June 20. --> Clear(June 28)
->Reference site HMAC_KDF: https://nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800-108.pdf
->Reference site HMAC_KDF(Korean ver): https://committee.tta.or.kr/data/standard_view.jsp?commit_code=PG501&firstDepthCode=TC5&nowPage=2&pk_num=TTAK.KO-12.0273&secondDepthCode=PG501
SHA3 HMAC KDF(Based SHA3 HMAC)
Every package have test text input file seems like SHA3-224.txt or HMAC_SHA3-224.txt.
Output file which is test result of the input files is SHA3-224_rsp.txt or HMAC_SHA3-224_rsp.txt
So, If you want to check input files and output files, just go test folder (every package have different name. so if some folder have only text file it might be test folder) and check above 2 sentences.
OS: Window
Compiler: MinGW
IDE: Eclipse
|
SHA3 hash values
|
| SHA3_HMAC |
| SHA3_DRBG |
| SHA3_HMAC_DRBG |
| SHA3_PBKDF |
| SHA3_HMAC_KDF |
OS: Linux
Compiler: Linux
IDE: Eclipse
|
SHA3_DRBG
|
| SHA3_HMAC_DRBG |