feat: support passage (.age suffix) #277
Description
Passage is (almost) drop in replacement for pass that uses age as backend written by the creator of age.
Problem arises because age saves file with '.age' suffix while pass does it with '.gpg' suffix. Just symlinking aws-user.gpg -> aws-user.age does the job:
aws-vault add aws-user
ln -s "$PASSAGE_DIR/aws-user.age" "$PASSAGE_DIR/aws-user.gpg"This is not a dealbreaker for adding users since it can easily be wrapped, but session-tokens are problem !
Solution would be to add check not just for .gpg but also for .age. Would send PR but I have never written Go, just read it. If you do not have time can give it a try ...
For reference this is the setup:
export AWS_VAULT_BACKEND=pass
export AWS_VAULT_PASS_CMD="passage"
export AWS_VAULT_PASS_PREFIX="aws"
export AWS_VAULT_PASS_PASSWORD_STORE_DIR="$PASSAGE_DIR"P.S.
I use both pass and passage stuck into same ~/.pass home. First one for secrets I am comfortable putting behind gpg-agent with generous cache time, while second one where I want to enter password (or yubikey) every time. gpg has global cache setup per keyring so I would need to create separate one, sounds like nightmare. Age is so much easier option, perfect for this scenario ...