tag:gpgtools.tenderapp.com,2011-11-04:/discussions/problems/58685-no-secret-keyGPGTools: Discussion 2017-12-10T12:38:26Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/435977402017-10-02T14:46:50Z2017-10-02T14:46:50ZNo secret key<div><p>Hi Eric,</p>
<p>welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.</p>
<p>Was your setup working prior to the update to GPG Suite 2017.1?</p>
<p>If so, with GPG Suite 2017.1 we have upgraded our version of GnuPG (MacGPG2) from GnuPG 2.0 to GnuPG 2.2.</p>
<p>The error message you are reporting indicates that there kay have been a problem migrating your secret key.</p>
<p>Please visit the following <a href="https://gpgtools.tenderapp.com/kb/faq/gpg-suite-20171-gnupg-20-gnupg-22-migration-help#i-am-missing-a-secret-key-">KB-article</a> and let me know if that brings you back to working state.</p>
<p>All the best,<br>
steve</p></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/435977402017-10-12T18:57:05Z2017-10-12T18:57:05ZNo secret key<div><p>Hi Steve,</p>
<p>No, it is the first I am trying to use gpg on a Mac. I have used gpg for years on my Linux machines, but migrated to Mac recently.</p>
<p>I used gpgKeyChain to import my secret and public key, changed the status to ultimate. So in the GPGKeychain window it shows sec/pub and four bright green block on the right. But if I try to sign an email it says ‘no secret key’. If I use the command line gpg -K it shows my secret key. So what is going wrong ?</p>
<p>Vriendelijke groeten,</p>
<p>Eric van Oorschot</p></div>eric.vanoorschottag:gpgtools.tenderapp.com,2011-11-04:Comment/435977402017-10-13T09:17:24Z2017-10-13T09:17:24ZNo secret key<div><p>Could you please send a debug log from your affected machine: Open System Preferences > GPG Suite > Send Report. Check the box to "attach debug log". Since you already described your issue in this discussion, you don't need to add a lot of detail, but please do add the link to your existing discussion, so I can then merge your debug info with this existing discussion.</p>
<p>All the best,<br>
steve</p></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/435977402017-10-13T14:03:57Z2017-10-13T14:03:57ZNo secret key<div><h2><a href="https://gpgtools.tenderapp.com/discussions/problems/60074-gpg-keychain-no-secret-key">Debug Log</a></h2>
<br></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/435977402017-10-14T13:47:04Z2017-10-14T13:47:04ZNo secret key<div><p>Hi Eric,</p>
<p>are you using a smartcard? If so, could you follow this KB-article and see if that brings you back to working state:</p>
<p><a href="https://gpgtools.tenderapp.com/kb/faq/gpg-suite-20171-gnupg-20-gnupg-22-migration-help">https://gpgtools.tenderapp.com/kb/faq/gpg-suite-20171-gnupg-20-gnup...</a></p>
<p>Best,<br>
steve</p></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/435977402017-10-17T17:47:59Z2017-10-17T17:47:59ZNo secret key<div><p>Hi Steve,</p>
<p>The tricky part was in the card reader. Under Linux i used the FSFE fellowship card for my encryption, that worked. But under MacOS i did not have a working card reader. So I tried it the old way, command line encryption. Although i copied the sec and pubring from an ancient USB stick it just did not work, whatever I tried.</p>
<p>Today I installed a card reader, and everything works fine. I still do not understand why the ‘old’ command line method without the card reader no longer works. The only files I copied from the ancient USB stick were the sec en pubring files. And these files were made as back up when I first stared using the card.</p>
<p>But anyway, not it works, signing and encrypting from my email.</p>
<p>Vriendelijke groeten,</p>
<p>Eric van Oorschot</p></div>eric.vanoorschottag:gpgtools.tenderapp.com,2011-11-04:Comment/435977402017-12-10T12:38:25Z2017-12-10T12:38:25ZNo secret key<div><p>Hi Eric,</p>
<p>thank you for your patience.<br>
We are glad to hear that you managed to solve your problem.<br>
Since GnuPG >= 2.1 a different keyring file is used. Now if you copy your old keyring file, <em>after</em> upgrading, the keys in that keyring file won't be migrated to the new format, since GnuPG is flagged as already having performed a migration.<br>
That is probably why the command line encrypt didn't work.</p>
<p>Closing this discussion. Feel free to open a new one anytime should you have questions or run into problems.</p></div>Luke Le