Git signing commit issue





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I have setup a gpg key :
gpg: WARNING: unsafe ownership on homedir '/home/anonymous/.gnupg'
/home/anonymous/.gnupg/pubring.kbx
---------------------------------
pub rsa4096/BA4FF7362A7BD6EF 2018-11-24 [SC]
40CF42C51EFF9574102F3060BA4FF7362A7BD6EF
uid [ultimate] **** (first key) <****@example.com>
sub rsa4096/05ED809ACFF9175E 2018-11-24 [E]



And I have configured git global like such
git config --global user.signingkey BA4FF7362A7BD6EF


But when I try to commit :
git commit -a -S -m 'git commit'


I get the following error:
error: gpg failed to sign the data
fatal: failed to write commit object










share|improve this question























  • Do you have the rights to write in the folder? Could be also because is a hidden folder?

    – b-fg
    Nov 25 '18 at 1:25











  • Have you configure which gpg program to use ?

    – vishnu narayanan
    Nov 25 '18 at 3:23











  • GIT_TRACE=1 git commit -a -S -m 'git commit' Run with GIT_TRACE to get a more detailed log of what's happening. It can give you an idea of what's going wrong. Share the log if you are not able to figure it out.

    – vishnu narayanan
    Nov 25 '18 at 3:25













  • @vishnu After running the command : GIT_TRACE=1 git commit -a -S -m 'git commit' the output was : 05:56:12.959594 git.c:328 trace: built-in: git 'commit' '-a' '-S' '-m' 'git commit' 05:56:12.960518 run-command.c:626 trace: run_command: 'gpg' '--status-fd=2' '-bsau' 'B3AB7B429CF88DA7' error: gpg failed to sign the data fatal: failed to write commit object

    – Bee Kay
    Nov 25 '18 at 5:58













  • I'm getting the same error, and I wonder if this is a bug with the new version of gpg. What version of gpg and gpg-agent are you using? What happens when you try echo "test" | gpg --verbose --clearsign

    – Alexander
    Nov 26 '18 at 18:26


















1















I have setup a gpg key :
gpg: WARNING: unsafe ownership on homedir '/home/anonymous/.gnupg'
/home/anonymous/.gnupg/pubring.kbx
---------------------------------
pub rsa4096/BA4FF7362A7BD6EF 2018-11-24 [SC]
40CF42C51EFF9574102F3060BA4FF7362A7BD6EF
uid [ultimate] **** (first key) <****@example.com>
sub rsa4096/05ED809ACFF9175E 2018-11-24 [E]



And I have configured git global like such
git config --global user.signingkey BA4FF7362A7BD6EF


But when I try to commit :
git commit -a -S -m 'git commit'


I get the following error:
error: gpg failed to sign the data
fatal: failed to write commit object










share|improve this question























  • Do you have the rights to write in the folder? Could be also because is a hidden folder?

    – b-fg
    Nov 25 '18 at 1:25











  • Have you configure which gpg program to use ?

    – vishnu narayanan
    Nov 25 '18 at 3:23











  • GIT_TRACE=1 git commit -a -S -m 'git commit' Run with GIT_TRACE to get a more detailed log of what's happening. It can give you an idea of what's going wrong. Share the log if you are not able to figure it out.

    – vishnu narayanan
    Nov 25 '18 at 3:25













  • @vishnu After running the command : GIT_TRACE=1 git commit -a -S -m 'git commit' the output was : 05:56:12.959594 git.c:328 trace: built-in: git 'commit' '-a' '-S' '-m' 'git commit' 05:56:12.960518 run-command.c:626 trace: run_command: 'gpg' '--status-fd=2' '-bsau' 'B3AB7B429CF88DA7' error: gpg failed to sign the data fatal: failed to write commit object

    – Bee Kay
    Nov 25 '18 at 5:58













  • I'm getting the same error, and I wonder if this is a bug with the new version of gpg. What version of gpg and gpg-agent are you using? What happens when you try echo "test" | gpg --verbose --clearsign

    – Alexander
    Nov 26 '18 at 18:26














1












1








1








I have setup a gpg key :
gpg: WARNING: unsafe ownership on homedir '/home/anonymous/.gnupg'
/home/anonymous/.gnupg/pubring.kbx
---------------------------------
pub rsa4096/BA4FF7362A7BD6EF 2018-11-24 [SC]
40CF42C51EFF9574102F3060BA4FF7362A7BD6EF
uid [ultimate] **** (first key) <****@example.com>
sub rsa4096/05ED809ACFF9175E 2018-11-24 [E]



And I have configured git global like such
git config --global user.signingkey BA4FF7362A7BD6EF


But when I try to commit :
git commit -a -S -m 'git commit'


I get the following error:
error: gpg failed to sign the data
fatal: failed to write commit object










share|improve this question














I have setup a gpg key :
gpg: WARNING: unsafe ownership on homedir '/home/anonymous/.gnupg'
/home/anonymous/.gnupg/pubring.kbx
---------------------------------
pub rsa4096/BA4FF7362A7BD6EF 2018-11-24 [SC]
40CF42C51EFF9574102F3060BA4FF7362A7BD6EF
uid [ultimate] **** (first key) <****@example.com>
sub rsa4096/05ED809ACFF9175E 2018-11-24 [E]



And I have configured git global like such
git config --global user.signingkey BA4FF7362A7BD6EF


But when I try to commit :
git commit -a -S -m 'git commit'


I get the following error:
error: gpg failed to sign the data
fatal: failed to write commit object







git gnupg






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 25 '18 at 1:21









Bee KayBee Kay

62




62













  • Do you have the rights to write in the folder? Could be also because is a hidden folder?

    – b-fg
    Nov 25 '18 at 1:25











  • Have you configure which gpg program to use ?

    – vishnu narayanan
    Nov 25 '18 at 3:23











  • GIT_TRACE=1 git commit -a -S -m 'git commit' Run with GIT_TRACE to get a more detailed log of what's happening. It can give you an idea of what's going wrong. Share the log if you are not able to figure it out.

    – vishnu narayanan
    Nov 25 '18 at 3:25













  • @vishnu After running the command : GIT_TRACE=1 git commit -a -S -m 'git commit' the output was : 05:56:12.959594 git.c:328 trace: built-in: git 'commit' '-a' '-S' '-m' 'git commit' 05:56:12.960518 run-command.c:626 trace: run_command: 'gpg' '--status-fd=2' '-bsau' 'B3AB7B429CF88DA7' error: gpg failed to sign the data fatal: failed to write commit object

    – Bee Kay
    Nov 25 '18 at 5:58













  • I'm getting the same error, and I wonder if this is a bug with the new version of gpg. What version of gpg and gpg-agent are you using? What happens when you try echo "test" | gpg --verbose --clearsign

    – Alexander
    Nov 26 '18 at 18:26



















  • Do you have the rights to write in the folder? Could be also because is a hidden folder?

    – b-fg
    Nov 25 '18 at 1:25











  • Have you configure which gpg program to use ?

    – vishnu narayanan
    Nov 25 '18 at 3:23











  • GIT_TRACE=1 git commit -a -S -m 'git commit' Run with GIT_TRACE to get a more detailed log of what's happening. It can give you an idea of what's going wrong. Share the log if you are not able to figure it out.

    – vishnu narayanan
    Nov 25 '18 at 3:25













  • @vishnu After running the command : GIT_TRACE=1 git commit -a -S -m 'git commit' the output was : 05:56:12.959594 git.c:328 trace: built-in: git 'commit' '-a' '-S' '-m' 'git commit' 05:56:12.960518 run-command.c:626 trace: run_command: 'gpg' '--status-fd=2' '-bsau' 'B3AB7B429CF88DA7' error: gpg failed to sign the data fatal: failed to write commit object

    – Bee Kay
    Nov 25 '18 at 5:58













  • I'm getting the same error, and I wonder if this is a bug with the new version of gpg. What version of gpg and gpg-agent are you using? What happens when you try echo "test" | gpg --verbose --clearsign

    – Alexander
    Nov 26 '18 at 18:26

















Do you have the rights to write in the folder? Could be also because is a hidden folder?

– b-fg
Nov 25 '18 at 1:25





Do you have the rights to write in the folder? Could be also because is a hidden folder?

– b-fg
Nov 25 '18 at 1:25













Have you configure which gpg program to use ?

– vishnu narayanan
Nov 25 '18 at 3:23





Have you configure which gpg program to use ?

– vishnu narayanan
Nov 25 '18 at 3:23













GIT_TRACE=1 git commit -a -S -m 'git commit' Run with GIT_TRACE to get a more detailed log of what's happening. It can give you an idea of what's going wrong. Share the log if you are not able to figure it out.

– vishnu narayanan
Nov 25 '18 at 3:25







GIT_TRACE=1 git commit -a -S -m 'git commit' Run with GIT_TRACE to get a more detailed log of what's happening. It can give you an idea of what's going wrong. Share the log if you are not able to figure it out.

– vishnu narayanan
Nov 25 '18 at 3:25















@vishnu After running the command : GIT_TRACE=1 git commit -a -S -m 'git commit' the output was : 05:56:12.959594 git.c:328 trace: built-in: git 'commit' '-a' '-S' '-m' 'git commit' 05:56:12.960518 run-command.c:626 trace: run_command: 'gpg' '--status-fd=2' '-bsau' 'B3AB7B429CF88DA7' error: gpg failed to sign the data fatal: failed to write commit object

– Bee Kay
Nov 25 '18 at 5:58







@vishnu After running the command : GIT_TRACE=1 git commit -a -S -m 'git commit' the output was : 05:56:12.959594 git.c:328 trace: built-in: git 'commit' '-a' '-S' '-m' 'git commit' 05:56:12.960518 run-command.c:626 trace: run_command: 'gpg' '--status-fd=2' '-bsau' 'B3AB7B429CF88DA7' error: gpg failed to sign the data fatal: failed to write commit object

– Bee Kay
Nov 25 '18 at 5:58















I'm getting the same error, and I wonder if this is a bug with the new version of gpg. What version of gpg and gpg-agent are you using? What happens when you try echo "test" | gpg --verbose --clearsign

– Alexander
Nov 26 '18 at 18:26





I'm getting the same error, and I wonder if this is a bug with the new version of gpg. What version of gpg and gpg-agent are you using? What happens when you try echo "test" | gpg --verbose --clearsign

– Alexander
Nov 26 '18 at 18:26












0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53463893%2fgit-signing-commit-issue%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53463893%2fgit-signing-commit-issue%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







這個網誌中的熱門文章

Tangent Lines Diagram Along Smooth Curve

Yusuf al-Mu'taman ibn Hud

Zucchini