spdx / spdx/cryptographic-algorithm-list

Chacha / Salsa / Chacha20 / Salsa20 case

Open
#44 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
No language data
Stars
8
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Rationale

We have in the List chacha(salsa)

Chacha is an evolution of Salsa. Both should be included on the list. The number behind these algorithms correspond to rounds, that is, the number of repetitions of the encryption process, which mixes the content.

What do we do with Salsa20 or Chacha8, for instance? Can the rounds be considered as a parameter?

This case needs to be evaluated, discussed and agreed.

Description

We have in the list

  • chacha(salsa)
  • salsa20

We need to:

  • Include the algorithms chacha and salsa
  • Define how do we express the rounds, like chacha8, chacha12 or salsa20, for instance. Could this be ?

Remember that the conversation about how to define the parameters is pending #25 #39

Is there any other algorithm affected by this so we should included in this conversation?

Actions

  • Change the algorithm name from chacha(salsa) to chacha
  • Confirm if there are additional algorithms affected by this definition of "rounds"
  • Agree on a way to define rounds among the different options, for chacha and salsa

DoD

  • PR that changes the algorithm name from chacha(salsa) to chacha #46
    • PR merged

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current algorithm list, the pending parameter discussions in issues #25 and #39, and PR #46. The work is done when the affected algorithms and a rounds-expression convention are agreed, the list is updated accordingly, and the referenced PR is merged.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.