cryptoSubClass values associated to the new cryptoClass values
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- markdown, yaml
- Domain
- cryptography
Research direction
Read issues #71 and #68 and review the linked proposal before assessing the three new cryptoClass categories. Then inspect the affected algorithm YAML files and the list properties description .md file; done requires group consensus, updated classifications and descriptions, and links to the resulting PR and documentation.
Written by the indexing model from the issue text.
Description
Background
There is a new List structure based on an extended number of cryptoClass values.
- Check #71 the new cryptoClass values do not have any cryptoSubClass value associated at this point.
- Check the umbrella ticket for all the work on restructuring the list #68
Rationale
It would be ideal to classify the algorithms under the new cryptoClass values, that is:
- Message-Authentication-Code
- Key-Derivation-Function
- Random-Number-Generator
by cryptoSubClass values
Description
Define values for the cryptoSubClass property corresponding to the following cryptoClass
- Message-Authentication-Code
- Key-Derivation-Function
- Random-Number-Generator
Add the description to the corresponding list properties description document and add the values to the affected algorithms from the list (yaml files).
Actions
- Create a proposal
- Provide a rationale, the proposed values and the list of algorithms affected
- Reach consensus about the proposal within the Cryptography Group
- Submit the PR
- Include the content for the properties description file and the algorithms affected
- Review and approve the PR
DoD
- Link to the proposal
- Consensus reached?
- Link to the PR
- Lin to the new List's properties description .md file
- Dominant language
- No language data
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from spdx/cryptographic-algorithm-list
-
bug
Difficulty 2/5 1-2 days Newbie friendliness 72/100
spdx/cryptographic-algorithm-list#92 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
spdx/cryptographic-algorithm-list#88 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
spdx/cryptographic-algorithm-list#84 · 1 comment ·
-
documentation enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in spdx/cryptographic-algorithm-list
Similar issues
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
IBM/OpenJCEPlus#1822 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
objects
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
snapshot-labs/snapshot.js#1247 · 1 comment ·