Sidhanti Sudheendra

When using the latest version of SOPS v3.8.1, I too notice the issue where sops fails to read the SOPS_AGE_KEY environment variable. SOPS version 3.7.3 does not exhibit this problem....

Still getting the same error when exporting or adding the environment variable before the binary: ```bash ➜ export SOPS_AGE_KEY=$(age -d ~/.config/sops/age/age-key.txt) ➜ ~/apps/sops/sops-v3.7.3.darwin.arm64 -d secret.enc.json|cat ───────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── │ STDIN ───────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── 1...

The `SOPS_AGE_KEY_FILE` env var is not set. If I use/set the `SOPS_AGE_KEY_FILE` env var with the decrypted (i.e. non password-protected) key file then the decryption works fine in both versions.

As sure as I can be :) ```bash ➜ unset SOPS_AGE_KEY ; unset SOPS_AGE_KEY_FILE ➜ export SOPS_AGE_KEY_FILE= ; export SOPS_AGE_KEY= ; ➜ echo $SOPS_AGE_KEY_FILE $SOPS_AGE_KEY ➜ export SOPS_AGE_KEY=$(age -d ~/.config/sops/age/age-key.txt)...

You were correct, it was my bad between unset vs export. Once I only unset the env var that worked. Thanks for helping with that!