3.5.0 broken on Sierra about aws-vault HOT 12 CLOSED

I had to build from 1c5c5f26e90951f63d8c4b79890d8914db9b5e81 to get this working on sierra. Latest 3.5.0 release build was broken for me

from aws-vault.

Thanks @stevehodgkiss, I wonder if this is a keyring permissions bug. The error The user name or passphrase you entered is not correct. is a catch-all for a variety of permissions bugs. Could I trouble you to use the Keychain Access utility to repair your keychain permissions?

from aws-vault.

The discrepancy between .keychain and .keychain-db should be a red herring. We use the .keychain filename and OSX translates it to the new .keychain-db internally.

from aws-vault.

I'm going to close this. Please feel free to re-open @stevehodgkiss if you are still having issues.

from aws-vault.

Broken in what way?

On Tue., 18 Oct. 2016 at 4:28 am, ndaversa [email protected] wrote:

I had to build from 1c5c5f2 to get this
working on sierra. Latest 3.5.0 release build was broken for me

—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
#96 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA9jvqkeq7e-hxHFqw0ByKpHkhERDWVks5q07AqgaJpZM4KHQyv
.

from aws-vault.

Broken in what way?

I was getting the same No credentials found for profile "profilenamehere" problem

from aws-vault.

Did you reboot?
On Tue., 18 Oct. 2016 at 6:51 am, ndaversa [email protected] wrote:

Broken in what way?

I was getting the same No credentials found for profile "profilenamehere"
problem

—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
#96 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA9jhfu1ZUoE570H3s9pelw9dWa2Q2Yks5q09GqgaJpZM4KHQyv
.

from aws-vault.

Did you reboot?

lol, no I did not. However the 1c5c5f26e90951f63d8c4b79890d8914db9b5e81 version worked without a reboot.

from aws-vault.

Bet it would fix the issue :)
On Tue., 18 Oct. 2016 at 7:08 am, ndaversa [email protected] wrote:

Did you reboot?

lol, no I did not. However the 1c5c5f2
version worked without a reboot.

—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
#96 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA9jnMTUuJBYuOWF0A7CuOPU9cvxQeHks5q09WtgaJpZM4KHQyv
.

from aws-vault.

Bet it would fix the issue :)

I wouldn't be surprised.

from aws-vault.

If it persisted beyond a reboot, it would actually be an amazing thing, because then I could possibly fix it. As it stands, I believe this is another echo of the dreaded #49, which is actually a Keychain issue.

from aws-vault.

For comparison, we are all on Sierra :)

from aws-vault.