Update installed: Password Fails
How do I correct this? I get a notice of upgrade, allow it, go to send an encrypted message to test and asks for password. Repeats, repeats, repeats. Mail won't send, probably won't decrypt either. Is it because I had an older version installed? Would the upgrade correct/incorporate that?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by meNeither on 07 Dec, 2017 02:08 AM
Got a similar problem with version 2.7.1 (build 1254) on macOS Sierra 10.12.6. It’s possible for me to send encrypted messages. I have to re-enter my passphrase every single time, but the email will be sent. After receiving the encrypted message, the password prompt will open again, but won’t accept the correct passphrase.
2 Posted by mikexryan on 07 Dec, 2017 02:31 AM
I do have a backup system and may have to go back to previous version if I can't resolve this. macOS 10.11.6
I won't go to Sierra. It disrupts too many older reliable items/features.
3 Posted by meNeither on 07 Dec, 2017 03:37 AM
I‘m sorry for being unclear. I just wanted to confirm, that your problem exists on Sierra, too. It seems to me, that the newest release introduces a bug regarding passphrases.
Because of this, I cannot decrypt the messages I receive.
4 Posted by mikexryan on 07 Dec, 2017 05:04 PM
Without an answer I'm forced to move back. Why would you release an upgrade if it weren't throughly tested? This is not a game, it's a major piece of security. If you're using macOSX my advice is to avoid GPG. This upgrade has ended any respect I had for the product. Time to pull out the linux machine dam it.
5 Posted by Branden Siu on 07 Dec, 2017 05:24 PM
I have similar issue on the new update, on 10.13.1, After receiving the encrypted message, the password prompt will open again, but won’t accept the correct passphrase.
Support Staff 6 Posted by Luke Le on 07 Dec, 2017 05:48 PM
Hi mike and others,
we are very sorry you are experiencing issues with the latest release of GPG Suite.
We believe this might be related due to a custom install of gpg which you have on your computers along side MacGPG2 from GPG Suite.
Please run the following command and let us know what the output is:
In order to be able to help each of you in the most efficient manner, we would like to ask you to create separate discussions. While the problem might seem to be same, the reason for it is very often not.
Thanks
7 Posted by Branden Siu on 07 Dec, 2017 06:11 PM
gpg (GnuPG) 1.4.9
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
Branden Siu | EPAC Technologies, Inc.
510.317.7979 x236 office | 510.300.2036 direct | [email blocked] <mailto:[email blocked]>
2561 Grant Avenue, San Leandro, CA 94579
- This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited
8 Posted by Branden Siu on 07 Dec, 2017 06:25 PM
seems my key show unknown now
Gundams-Panel:~ brandensiu$ /usr/local/bin/gpg --version
gpg (GnuPG) 1.4.9
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
Branden Siu | EPAC Technologies, Inc.
510.317.7979 x236 office | 510.300.2036 direct | [email blocked] <mailto:[email blocked]>
2561 Grant Avenue, San Leandro, CA 94579
- This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited
9 Posted by Branden Siu on 07 Dec, 2017 06:31 PM
Thanks, I think i found the answer
Support Staff 10 Posted by Luke Le on 07 Dec, 2017 06:32 PM
We can confirm that we have found the issue in our code and it's only triggered by a custom gpg build installed under /usr/local/bin/gpg which is why we have not been able to find it earlier in our testing.
Please run the following command as a temporary fix:
That should fix the problem you all are having
A permanent fix and better compatibility with custom GnuPG versions will be included in a future release.
11 Posted by Branden Siu on 07 Dec, 2017 06:36 PM
already did. will keep an eye on it, but thanks for your time!
12 Posted by alp on 07 Dec, 2017 06:37 PM
Luke
Thank you for the work around!
13 Posted by mikexryan on 07 Dec, 2017 09:01 PM
gpg (GnuPG) 1.4.9
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
14 Posted by mikexryan on 07 Dec, 2017 09:11 PM
The sudo is not working:
--Company-5:~ mikexryan$ sudo mv /usr/local/bin/gpg /usr/local/bin/gpg-v1 Password:
Shows a small key next to password, won't let me input a password, don't know which password it wants, system? gpg password? Either way, won't let me type in. I shouldn't be posting my private info here, don't appreciate it at all but here's what I get:
Out of of business right now and I've got five online stores, can't confirm any purchases. So angry over this. I'm dead in the water ARGGGHHH!
Support Staff 15 Posted by Luke Le on 07 Dec, 2017 09:12 PM
Hi mike,
if you hop onto our live chat for a minute we'll get you sorted:
https://www.hipchat.com/gyyOrLdWt
16 Posted by mikexryan on 07 Dec, 2017 09:15 PM
I can't deal with customers and live chat at the same time. Too angry and will take day off tomorrow and remove the whole dam thing, go back to linux. So angry.
Support Staff 17 Posted by Luke Le on 07 Dec, 2017 09:17 PM
If you are not familiar with Terminal, the quickest way back is to simply re-install 2017.1:
https://releases.gpgtools.org/GPG_Suite-2017.1.dmg
Hope that helps.
Support Staff 18 Posted by Steve on 07 Dec, 2017 10:09 PM
@Mike: re your terminal questions. The fact that you do not see typing when typing your password in terminal is by design and expected.
Your admin password is being requested for the sudo command. So enter the password you use to log into your mac and see if that does the trick.
Best,
steve
19 Posted by meNeither on 08 Dec, 2017 12:06 AM
@Luke Le: Thank you. Your suggestion solved the problem for me. :)
20 Posted by Guido on 08 Dec, 2017 03:27 PM
Hi,
thank you for the work around it works for me
I fixed the issue
Support Staff 21 Posted by Steve on 10 Dec, 2017 03:49 PM
Thanks for the feedback @Guido and @meNeither. Glad, this is solved for you. I'm closing this discussion. Should you need further assistance or have questions you can re-open this discussion here or open a new one any time.
Should anybody still be facing issues, please do file a new discussion and we will make sure to help you out getting your setup fixed.
Best,
steve
Steve closed this discussion on 10 Dec, 2017 03:49 PM.
Steve closed this discussion on 14 Dec, 2017 04:33 PM.