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

clearsign produces detached signatures #189

Open
PomposusMaximus opened this issue Jul 6, 2024 · 1 comment
Open

clearsign produces detached signatures #189

PomposusMaximus opened this issue Jul 6, 2024 · 1 comment

Comments

@PomposusMaximus
Copy link

PomposusMaximus commented Jul 6, 2024

Good morning

is it by intention that GPGME::Crypto.clearsign(text) produces detached signatures? At least, the signed data is not included in the result. Should this not be an equivalent to calling :~$: gpg --clearsign [text] on the command-line?
Directing the output to a file (option :output) does only produce the same, for me useless, output: a signature inside a PGP-encrypted block, but the signed data is not included.

If you do produce “inline” clear singed text, please show me your authentic code example.

TIA

@PomposusMaximus
Copy link
Author

It appears, that also
sig2 = crypto.sign(text, :mode => GPGME::SIG_MODE_CLEAR)
does not produce an inline-signature. Like with clearsign(), the signed content is missing.

Meanwhile
GPGME::Ctx.new {|ctx| ctx.sign(text, output, GPGME::SIG_MODE_CLEAR)}
works alright.

The problem – if I understand anything at all – is with GPGME::Crypto, irrespective of the signing method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant