From: Peter Todd <pete@petertodd.org>
To: Andy Schroder <info@AndySchroder.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 15:20:04 -0400 [thread overview]
Message-ID: <20150610192004.GB21416@savin.petertodd.org> (raw)
In-Reply-To: <55788C02.1010105@AndySchroder.com>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
On Wed, Jun 10, 2015 at 03:12:02PM -0400, Andy Schroder wrote:
>
> Andy Schroder
>
> On 06/10/2015 03:03 PM, Peter Todd wrote:
> >
> >>4. Seems like digital signatures are always broken on messages because
> >> the list server slightly modifies them (?), so my e-mail client
> >> doesn't verify them all.
> >What type of digital signatures specifically? What email client?
>
> I think they are usually PGP/MIME signatures that are not working
> right. If you'll notice from my e-mail headers:
>
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
> X-Enigmail-Version: 1.6
It might be that Thunderbird doesn't properly handle messages with both
signed and unsigned content. I use mutt myself, which handles it just
fine. (the sigs on your emails verify just fine for instance)
--
'peter'[:-1]@petertodd.org
0000000000000000134f9a433a4bece258b5035ecda33384f820a60493ca2887
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-06-10 19:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:25 [Bitcoin-development] Is SourceForge still trustworthy enough to host this list? xor
2015-06-10 9:35 ` Wladimir J. van der Laan
2015-06-10 16:46 ` Andy Schroder
2015-06-10 18:02 ` Troy Benjegerdes
2015-06-10 18:41 ` Andy Schroder
[not found] ` <DB12E925-11C6-4A82-BC81-FB3DA26BC5B3@newcastle.ac.uk>
[not found] ` <20150610185810.GQ27932@nl.grid.coop>
[not found] ` <DB5PR07MB091974E06974EA88136F60C2B5BD0@DB5PR07MB0919.eurprd07.prod.outlook.com>
2015-06-11 1:46 ` Troy Benjegerdes
2015-06-10 18:28 ` Ivan Brightly
2015-06-10 18:47 ` Troy Benjegerdes
2015-06-10 19:13 ` Ivan Brightly
2015-06-10 18:36 ` s7r
2015-06-10 18:59 ` Andy Schroder
2015-06-10 19:03 ` Peter Todd
2015-06-10 19:12 ` Andy Schroder
2015-06-10 19:20 ` Peter Todd [this message]
2015-06-10 19:36 ` Andy Schroder
2015-06-10 19:43 ` Peter Todd
2015-06-10 20:03 ` Andy Schroder
2015-06-10 19:54 ` Jeff Garzik
2015-06-11 9:27 ` Wladimir J. van der Laan
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=20150610192004.GB21416@savin.petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=info@AndySchroder.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