From: teatime@gmx.com (Jan Spakula)
Subject: [sup-talk] gpg signatures are not valid of sig present
Date: Mon, 19 May 2008 17:04:39 -0500 [thread overview]
Message-ID: <1211234574-sup-2131@aconcagua> (raw)
In-Reply-To: <1211233254-sup-8091@south>
Excerpts from William Morgan's message of Mon May 19 16:41:46 -0500 2008:
> Reformatted excerpts from Jan Spakula's message of 2008-05-15:
> > I've just recently discovered that gpg signatures generated by sup are
> > not verifiable (BAD signature result from gpg) on other e-mail clients
> > (tried with mutt and claws-mail), when I have nonempty signature.
>
> Turns out this was a newline issue. I think I've tracked it down. Do a
> git pull and try again.
Works now. Thanks for the fix!
--
Jan
prev parent reply other threads:[~2008-05-19 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 4:42 Jan Spakula
2008-05-19 21:41 ` William Morgan
2008-05-19 22:04 ` Jan Spakula [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1211234574-sup-2131@aconcagua \
--to=teatime@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox