From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gpg signature verification failures
Date: Sun, 18 Sep 2016 12:32:09 -0700 (PDT) [thread overview]
Message-ID: <1543516.AyAsJL8d1W@dell_xps> (raw)
In-Reply-To: <20160918184154.9472.11713EF6@matica.foolinux.mooo.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On Sunday 18 Sep 2016 11:47:05 Ian Zimmerman wrote:
> On 2016-09-18 18:34, Mick wrote:
> > > http://marc.info/?l=mutt-users&m=147417981514310&w=2
> > >
> > > So, what's going on? This would seem to be a Big Deal [TM].
> >
> > The way some clients attach gpg signatures (in line, or multipart)
> > makes a difference, depending on the receiving mail client.
>
> It's happening with multipart/signed messages, which to me implies that
> what I extract is exactly, byte by byte, what was attached and signed.
>
> > I have seen bad signatures in this M/L but it is not a regular
> > occurrence.
>
> Your own message re: TaskCoach fails to verify, and that's what prompted
> me to post about it here.
Failing to verify is not the same as bad signature. It may fail to verify if
the keyservers are unreachable by the client. This could be because of traffic,
DDoS attacks, etc.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-09-18 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 17:10 [gentoo-user] gpg signature verification failures Ian Zimmerman
2016-09-18 17:34 ` Mick
2016-09-18 18:47 ` [gentoo-user] " Ian Zimmerman
2016-09-18 19:32 ` Mick [this message]
2016-09-18 20:13 ` Ian Zimmerman
2016-09-18 21:45 ` Neil Bothwick
2016-09-18 22:00 ` Alecks Gates
2016-09-18 22:33 ` Mick
2016-09-18 23:19 ` »Q«
2016-09-18 22:36 ` »Q«
2016-09-19 16:40 ` Ian Zimmerman
2016-09-19 16:53 ` Neil Bothwick
2016-09-19 20:37 ` Ian Zimmerman
2016-09-19 22:01 ` Mick
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=1543516.AyAsJL8d1W@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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