Empty passphrase breaks keychain
Closed this issue · 9 comments
Running match development will ask for passphrase to encrypt the repopsitory. Not typing any password just hitting enter throws an error message correctly, but next time when I want to run match development again, it won't accept any password and throws the following error
security: SecKeychainAddInternetPassword <NULL>: The specified item already exists in the keychain.
After deleting the corresponding match entries from the keychain, match development with a supplied password runs perfectly again.
Can you share your version of match and the full log please?
It doesn't throw any Ruby exception, it just goes on and on until I delete the corresponding keychain entry:
[17:26:52]: Enter the passphrase that should be used to encrypt/decrypt your certificates
[17:26:52]: This passphrase is specific per repository and will be stored in your local keychain
[17:26:52]: Make sure to remember the password, as you'll need it when you run match on a different machine
Passphrase for Git Repo: *****************
Type passphrase again: *****************
security: SecKeychainAddInternetPassword <NULL>: The specified item already exists in the keychain.
[17:26:55]: Enter the passphrase that should be used to encrypt/decrypt your certificates
[17:26:55]: This passphrase is specific per repository and will be stored in your local keychain
[17:26:55]: Make sure to remember the password, as you'll need it when you run match on a different machine
Passphrase for Git Repo: *****************
Type passphrase again: *****************
security: SecKeychainAddInternetPassword <NULL>: The specified item already exists in the keychain.
[17:27:12]: Enter the passphrase that should be used to encrypt/decrypt your certificates
[17:27:12]: This passphrase is specific per repository and will be stored in your local keychain
[17:27:12]: Make sure to remember the password, as you'll need it when you run match on a different machine
Passphrase for Git Repo: *****************
Type passphrase again: *****************
Yes, that happened to me as well.
@mcz Which entries did you removed?
All "match" entries. Search for match in keychain.
On Thu, 25 Feb 2016 at 20:39, Ricardo Pereira notifications@github.com
wrote:
Yes, that happened to me as well.
@mcz https://github.com/mcz Which entries did you removed?—
Reply to this email directly or view it on GitHub
#124 (comment).
@mcz Thanks. Do you have 2 step auth on?
Nope.
On Thu, 25 Feb 2016 at 22:02, Ricardo Pereira notifications@github.com
wrote:
@mcz https://github.com/mcz Thanks. Do you have 2 step auth on?
—
Reply to this email directly or view it on GitHub
#124 (comment).
Got the same issue
I was able to fix the problem. In my case, it wasn't because of an empty passphrase, but it seemed like the passphrase I used was too long. I generated it with a keepass.
I simply used match change_password with a shorter password and everything works now.
The first password had 100 characters, the new one has 40. Is there a limit to that?
This issue was migrated to fastlane/fastlane#1985. Please post all further comments there.
fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀