Decrypting a enc.env file throwing error of extra text "\x0d"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
I'm able to encrypt .env file with command
sops -e .env > enc.env
To decrypt enc.env I'm using command
sops --input-type dotenv --decrypt --output-type dotenv .\enc.env > .\.env
Above command throwing error: parsing time "2022-12-23T08:18:47Z\x0d": extra text: "\x0d"
The same command working fine for yaml file
command to encrypt:
sops -e .\docker-compose.yaml > .\docker-compose.yaml.enc
command to decrypt:
sops --input-type yaml --decrypt --output-type yaml .\docker-compose.yaml.enc > .\docker-compose.yaml
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
Reproduce the Windows dotenv encryption and decryption commands from the issue, then trace sops's dotenv input/output handling and its parsing of the timestamp containing \x0d. Compare this path with the working YAML commands. Done means decrypting enc.env succeeds without the extra-text error and preserves the expected dotenv values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100