multiformats / multiformats/multicodec
Add multihash code for AES-CMAC
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 383
- Forks
- 221
- Avg merge
- 24d 6h
- Merged PRs (30d)
- 1
Description
Would it make sense to allocate a multihash code for "AES-CMAC" -128 / -192 / -256 ?
- https://developers.google.com/tink/supported-key-types#mac AES-CMAC
- https://learn.microsoft.com/en-us/uwp/api/windows.security.cryptography.core.macalgorithmnames.aescmac
- https://en.wikipedia.org/wiki/One-key_MAC
- RFC 4493 https://datatracker.ietf.org/doc/html/rfc4493 & https://www.rfc-editor.org/rfc/rfc4493.html
- https://cryptography.io/en/latest/hazmat/primitives/mac/cmac/
- https://crypto.stackexchange.com/search?q=aes-cmac
- https://github.com/megrxu/AES-CMAC
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the multicodec tables and the AES-CMAC references linked in the issue, especially RFC 4493. Determine whether separate codes are needed for the 128-, 192-, and 256-bit variants; done means the allocation decision is agreed and the relevant table is updated.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100