getsops / getsops/sops

Documentation improvement regarding encrypted key (enc field)

Open
#1,070 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi all,

I would like to understand exactly what the encryptedKey is and why it needs to be stored in the encrypted sops file in the "enc" field.

Could the documentation maybe be extended regarding the field?

Thank you!

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 locating the documentation that describes encrypted SOPS files and the "enc" field. Explain what encryptedKey is and why it is stored there; the work is done when the field and its purpose are clear to readers.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, security
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.