gpg: error retrieving 'me@example.com' via WKD

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
4
down vote

favorite
1












I am trying to encrypt a file locally and I get an error. me@example.com is a placeholder for my email address, a public key exists for that in my keyring and also on key servers. My private key is located on a hardware key (Yubikey). I can decrypt previously encrypted files with no problem. Here is the error:



➜ ~ gpg -e -r me@example.com somefile.txt 
gpg: error retrieving 'me@example.com' via WKD: General error
gpg: me@example.com: skipped: General error
gpg: somefile.txt encryption failed: General error


What does this error mean and how can I solve it?



P.S. There is only one more thing that might be related. My public key is expired.







share|improve this question


















  • 1




    WKD is the web key directory. Is adding the -vv option providing more insight what's going wrong?
    – Jens Erat
    Nov 19 '17 at 13:48










  • Adding -vv prints four more lines, three of them being gpg: Note: signature key ... expired and the last one gpg: <ke_id> skipped: Unusable public key. Apparently everything boils down to the key being expired.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:16










  • Extending the key solved the problem.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:23










  • Glad you figured it out on your own. Feel free to add this as an answer -- this seems a rather new combination of weird error message and actual issue.
    – Jens Erat
    Nov 19 '17 at 21:55














up vote
4
down vote

favorite
1












I am trying to encrypt a file locally and I get an error. me@example.com is a placeholder for my email address, a public key exists for that in my keyring and also on key servers. My private key is located on a hardware key (Yubikey). I can decrypt previously encrypted files with no problem. Here is the error:



➜ ~ gpg -e -r me@example.com somefile.txt 
gpg: error retrieving 'me@example.com' via WKD: General error
gpg: me@example.com: skipped: General error
gpg: somefile.txt encryption failed: General error


What does this error mean and how can I solve it?



P.S. There is only one more thing that might be related. My public key is expired.







share|improve this question


















  • 1




    WKD is the web key directory. Is adding the -vv option providing more insight what's going wrong?
    – Jens Erat
    Nov 19 '17 at 13:48










  • Adding -vv prints four more lines, three of them being gpg: Note: signature key ... expired and the last one gpg: <ke_id> skipped: Unusable public key. Apparently everything boils down to the key being expired.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:16










  • Extending the key solved the problem.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:23










  • Glad you figured it out on your own. Feel free to add this as an answer -- this seems a rather new combination of weird error message and actual issue.
    – Jens Erat
    Nov 19 '17 at 21:55












up vote
4
down vote

favorite
1









up vote
4
down vote

favorite
1






1





I am trying to encrypt a file locally and I get an error. me@example.com is a placeholder for my email address, a public key exists for that in my keyring and also on key servers. My private key is located on a hardware key (Yubikey). I can decrypt previously encrypted files with no problem. Here is the error:



➜ ~ gpg -e -r me@example.com somefile.txt 
gpg: error retrieving 'me@example.com' via WKD: General error
gpg: me@example.com: skipped: General error
gpg: somefile.txt encryption failed: General error


What does this error mean and how can I solve it?



P.S. There is only one more thing that might be related. My public key is expired.







share|improve this question














I am trying to encrypt a file locally and I get an error. me@example.com is a placeholder for my email address, a public key exists for that in my keyring and also on key servers. My private key is located on a hardware key (Yubikey). I can decrypt previously encrypted files with no problem. Here is the error:



➜ ~ gpg -e -r me@example.com somefile.txt 
gpg: error retrieving 'me@example.com' via WKD: General error
gpg: me@example.com: skipped: General error
gpg: somefile.txt encryption failed: General error


What does this error mean and how can I solve it?



P.S. There is only one more thing that might be related. My public key is expired.









share|improve this question













share|improve this question




share|improve this question








edited Nov 19 '17 at 13:37

























asked Nov 19 '17 at 13:27









Mehdi Sadeghi

18010




18010







  • 1




    WKD is the web key directory. Is adding the -vv option providing more insight what's going wrong?
    – Jens Erat
    Nov 19 '17 at 13:48










  • Adding -vv prints four more lines, three of them being gpg: Note: signature key ... expired and the last one gpg: <ke_id> skipped: Unusable public key. Apparently everything boils down to the key being expired.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:16










  • Extending the key solved the problem.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:23










  • Glad you figured it out on your own. Feel free to add this as an answer -- this seems a rather new combination of weird error message and actual issue.
    – Jens Erat
    Nov 19 '17 at 21:55












  • 1




    WKD is the web key directory. Is adding the -vv option providing more insight what's going wrong?
    – Jens Erat
    Nov 19 '17 at 13:48










  • Adding -vv prints four more lines, three of them being gpg: Note: signature key ... expired and the last one gpg: <ke_id> skipped: Unusable public key. Apparently everything boils down to the key being expired.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:16










  • Extending the key solved the problem.
    – Mehdi Sadeghi
    Nov 19 '17 at 21:23










  • Glad you figured it out on your own. Feel free to add this as an answer -- this seems a rather new combination of weird error message and actual issue.
    – Jens Erat
    Nov 19 '17 at 21:55







1




1




WKD is the web key directory. Is adding the -vv option providing more insight what's going wrong?
– Jens Erat
Nov 19 '17 at 13:48




WKD is the web key directory. Is adding the -vv option providing more insight what's going wrong?
– Jens Erat
Nov 19 '17 at 13:48












Adding -vv prints four more lines, three of them being gpg: Note: signature key ... expired and the last one gpg: <ke_id> skipped: Unusable public key. Apparently everything boils down to the key being expired.
– Mehdi Sadeghi
Nov 19 '17 at 21:16




Adding -vv prints four more lines, three of them being gpg: Note: signature key ... expired and the last one gpg: <ke_id> skipped: Unusable public key. Apparently everything boils down to the key being expired.
– Mehdi Sadeghi
Nov 19 '17 at 21:16












Extending the key solved the problem.
– Mehdi Sadeghi
Nov 19 '17 at 21:23




Extending the key solved the problem.
– Mehdi Sadeghi
Nov 19 '17 at 21:23












Glad you figured it out on your own. Feel free to add this as an answer -- this seems a rather new combination of weird error message and actual issue.
– Jens Erat
Nov 19 '17 at 21:55




Glad you figured it out on your own. Feel free to add this as an answer -- this seems a rather new combination of weird error message and actual issue.
– Jens Erat
Nov 19 '17 at 21:55










1 Answer
1






active

oldest

votes

















up vote
5
down vote



accepted










Extending key expiration date fixed the problem. The error message was misleading. However adding -vv as Jens Erat suggested produced some useful error messages such as gpg: Note: signature key ... expired and gpg: ... skipped: Unusable public key that helped finding the actual error.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f405599%2fgpg-error-retrieving-meexample-com-via-wkd%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    5
    down vote



    accepted










    Extending key expiration date fixed the problem. The error message was misleading. However adding -vv as Jens Erat suggested produced some useful error messages such as gpg: Note: signature key ... expired and gpg: ... skipped: Unusable public key that helped finding the actual error.






    share|improve this answer
























      up vote
      5
      down vote



      accepted










      Extending key expiration date fixed the problem. The error message was misleading. However adding -vv as Jens Erat suggested produced some useful error messages such as gpg: Note: signature key ... expired and gpg: ... skipped: Unusable public key that helped finding the actual error.






      share|improve this answer






















        up vote
        5
        down vote



        accepted







        up vote
        5
        down vote



        accepted






        Extending key expiration date fixed the problem. The error message was misleading. However adding -vv as Jens Erat suggested produced some useful error messages such as gpg: Note: signature key ... expired and gpg: ... skipped: Unusable public key that helped finding the actual error.






        share|improve this answer












        Extending key expiration date fixed the problem. The error message was misleading. However adding -vv as Jens Erat suggested produced some useful error messages such as gpg: Note: signature key ... expired and gpg: ... skipped: Unusable public key that helped finding the actual error.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 '17 at 15:04









        Mehdi Sadeghi

        18010




        18010



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f405599%2fgpg-error-retrieving-meexample-com-via-wkd%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay