getsops / getsops/sops

Support en-/decryption using XChaCha20+Poly1305

Open
#803 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
23.1k
Forks
1.1k
Avg merge
1d 11h
Merged PRs (30d)
9

Description

In order to have a reasonable alternative to AES256-GCM, I want to have the data encrypted using XChaCha20+Poly1305.

There are some use-cases to this:

  • providing choices to the user
  • prepare for broken or flawed hardware implementations
  • avoid the risk of some potential attacks (e.g. timing)
  • higher throughput on platforms without hardware support

Although this sounds like advocating for the alternative, I am just paranoid enough to simply want an alternative to be there.

References:

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

The issue names no repository files or tests. Start by comparing the referenced Go chacha20poly1305 implementation with the repository’s current AES-256-GCM path, then determine the needed API, nonce handling, and data-format compatibility. Done means XChaCha20-Poly1305 encryption and decryption are supported with tests covering the new option.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.