From: Andy Schroder <info@AndySchroder•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 15:36:42 -0400 [thread overview]
Message-ID: <557891CA.5010708@AndySchroder.com> (raw)
In-Reply-To: <20150610192004.GB21416@savin.petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]
Andy Schroder
On 06/10/2015 03:20 PM, Peter Todd wrote:
> 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)
>
It's possible that the enigmail extension is not working right, but I
was under the impression that it is just feeding data to gpg and then
receiving the response back. It's possible that your e-mail you just
checked was not sent through mailman since I also replied directly to
you explicitly (in which case the message has not been modified) and you
probably have the setting in the mailing list set to not send duplicate
messages if you are an explicit TO. I just deleted all explicit TOs for
this message, so everyone should be receiving it through the mailing
list and not directly. Is the signature still valid for you now? I think
enigmail can handle messages with some signed and unsigned content, and
maybe PGP/MIME inherently does not support this and a mailing list
re-writing parts of messages is an expected action? If this message
re-writing is an expected action and I'm correct that PGP/MIME does not
support partially signed content, then maybe it is just a recommendation
for this mailing list to not use PGP/MIME for messages sent to the list?
Can anyone else confirm?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
next prev parent reply other threads:[~2015-06-10 19:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:25 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
2015-06-10 19:36 ` Andy Schroder [this message]
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=557891CA.5010708@AndySchroder.com \
--to=info@andyschroder$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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