Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPG signing silently fails on incorrect settings #5574

Open
PerchunPak opened this issue Feb 4, 2025 · 5 comments
Open

GPG signing silently fails on incorrect settings #5574

PerchunPak opened this issue Feb 4, 2025 · 5 comments
Labels
polish🪒🐃 Make existing features more convenient and more consistent

Comments

@PerchunPak
Copy link

Description

For some reason, GPG signing doesn't work for me. If I do a commit using jj and then do git log --show-signatures, there are no signatures. GitHub also doesn't see my signature.

Steps to Reproduce the Problem

https://asciinema.org/a/q7t4a2003pIMKbwC7VEC6fIFD

jj sign from #4747 https://asciinema.org/a/dYHq59eXmgxW4TOYQ9ipNLMBD

Expected Behavior

$ git log --show-signatures -1
────────────────────────────────────────────────┐
commit 12da68c03b11c2be6776941f00da6aa043bb2b92 │
────────────────────────────────────────────────┴
gpg: Signature made Tue 04 Feb 2025 07:01:35 AM CET
gpg:                using RSA key BBB51142959D8549A3D2F6C5313F67D1EAB770F9
gpg: Good signature from "Perchun Pak <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: BBB5 1142 959D 8549 A3D2  F6C5 313F 67D1 EAB7 70F9
Author: PerchunPak <[email protected]>
Date:   Tue Feb 4 07:01:35 2025 +0100

    test

Actual Behavior

No signature present

Specifications

@bnjmnt4n
Copy link
Member

bnjmnt4n commented Feb 4, 2025

Can you confirm that you've correctly set the required settings: https://jj-vcs.github.io/jj/latest/config/#gnupg-signing? Posting your configuration would be helpful for debugging.

@PerchunPak
Copy link
Author

my ~/.config/jj/config.toml

[core]
fsmonitor = "watchman"

[core.watchman]
register_snapshot_trigger = true

[signing]
key = "313F67D1EAB770F9"
sign-all = true

[user]
email = "[email protected]"
name = "PerchunPak"
$ jj config
operation.hostname = "perchun-laptop"
operation.username = "perchun"
ui.pager = "less"
ui.editor = "nvim"
core.fsmonitor = "watchman"
core.watchman.register_snapshot_trigger = true
signing.key = "313F67D1EAB770F9"
signing.sign-all = true
user.email = "[email protected]"
user.name = "PerchunPak"

@bnjmnt4n
Copy link
Member

bnjmnt4n commented Feb 4, 2025

It looks like you're missing signing.backend = "gpg"?

@PerchunPak
Copy link
Author

PerchunPak commented Feb 4, 2025

Oh, you're correct! I though gpg is the default value

It should not silently fail though (at least jj sign)

@pylbrecht
Copy link
Contributor

It should not silently fail though (at least jj sign)

Very valid point. I will take care of that in #4747.

@PerchunPak PerchunPak changed the title GPG signing doesn't work GPG signing silently fails on incorrect settings Feb 4, 2025
@PhilipMetzger PhilipMetzger added the polish🪒🐃 Make existing features more convenient and more consistent label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
polish🪒🐃 Make existing features more convenient and more consistent
Projects
None yet
Development

No branches or pull requests

4 participants