SOPS 1.17 work in Ubuntu but same version failing in RHEL
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Hello sops folks, can someone please explain why sops 1.17 is failing in RHEL! it's definitely not permissions issue, our EC2 instance has got access to the KMS key and I have checked it by using sops v3.0.5 which works perfect.
Now I can decrypt same file using same KMS key and sops 1.17 on my Ubuntu machine. Could you please advise what's wrong with sops 1.17 on RHEL? we are installing it using pip. Please note that if I install the latest one (3.0.4) which I did using RPM, it works fine.
Appreciate your help. Thank you.
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.
Research direction
The report only identifies SOPS 1.17 installed with pip on RHEL, compared with SOPS 3.0.4 from an RPM and SOPS 1.17 on Ubuntu. Start by reproducing decryption with the same KMS key in those environments and comparing the failure details. Done means identifying the version or platform difference and documenting a supported resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, linux, python
- Domain
- cloud, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100