pda / aws-keychain Goto Github PK

In macOS Sierra, the keychain file extension has been changed from .keychain to .keychain-db, which causes errors like this when using aws-keychain:

security: SecKeychainCreate ~/Library/Keychains/aws-keychain.keychain: A keychain with the same name already exists

The following appears to fix the issue:

- : ${AWS_KEYCHAIN_FILE="$HOME/Library/Keychains/aws-keychain.keychain"}
+ : ${AWS_KEYCHAIN_FILE="$HOME/Library/Keychains/aws-keychain.keychain-db"}

I did an aws-keychain rm x but then a subsequent ls lists it as still being there though using it generates the migrate message. There are no files in my user Library keychains directory but if I tried to add the item again I get security: SecKeychainCreate /Users/rick/Library/Keychains/aws-keychain.keychain: A keychain with the same name already exists

This is macOS Sierra.

Changing passwords is sometimes required. Frequently, it's recommended even when not required.

Here's how to do it manually:

USER=sk # substitute your username
# a relative path doesn't work
security set-keychain-password /Users/"$USER"/Library/Keychains/aws-keychain.keychain

Zsh completion for:

• subcommands (aws-keychain u<tab> => aws-keychain use etc).
• existing key names (aws-keychain use perso<tab> => aws-keychain use personal)

I've created a formula. At the moment it's just in my personal formulae repo, but maybe you should own it? 😄

• What does it actually do? Writes ~/.aws/credentials etc.
• What tools use that file? http://aws.amazon.com/cli/ and boto …
• … more things?

When you run aws-keychain exec ... the command will be in ps, along with the token.

Why not simply put them in ~/.aws/credentials, where they should be.

I wanted to say thank you for making this tool. It hits a sweet spot of simplicity and solving a problem very very well. I have submitted a homebrew formula for this tool to make it easier for folks to consume it, and I wanted to let you know about that formula so that you might have it updated in the future when you publish new releases.

Homebrew/legacy-homebrew#49776

s3cmd doesn't use ~/.aws/credentials or $AWS_CREDENTIALS_FILE.

Consider adding support for aws-keychain to configure s3cmd credentials.

But… s3cmd might be obsoleted by http://aws.amazon.com/cli/

Like the completion described in #3 but for people who haven't realized Zsh is superior.
Hint: I'm not likely to be the one to implement this.