From: Martin Steigerwald <Martin@lichtvoll.de>
To: Iustin Pop <iusty@k1024.org>
Cc: xfs@oss.sgi.com
Subject: Re: invalidated gpg signatures (was: Re: xfs open questions)
Date: Wed, 28 Jan 2009 23:44:13 +0100 [thread overview]
Message-ID: <200901282344.32351.Martin@lichtvoll.de> (raw)
In-Reply-To: <20090128203703.GB3958@teal.hq.k1024.org>
[-- Attachment #1.1: Type: text/plain, Size: 1954 bytes --]
Am Mittwoch 28 Januar 2009 schrieb Iustin Pop:
> On Wed, Jan 28, 2009 at 09:22:00PM +0100, Martin Steigerwald wrote:
> > Am Mittwoch 28 Januar 2009 schrieb Russell Cattelan:
> > > Russell Cattelan wrote:
> > > > Michael Monnerie wrote:
> > > >> On Mittwoch 28 Januar 2009 Russell Cattelan wrote:
> > > >>> The sig is there, are you saying it's broken somehow?
> > > >>> It might have something to do with the html stripper.
> > > >>
> > > >> Yes, I use kmail (from KDE) which automatically displays mails
> > > >> with gpg- sigs in different colours to easily see if it's
> > > >> correct/trusted/wrong. And on this list, my messages all come
> > > >> with "Invalid Sig".
> > > >
> > > > Well I ran a test email through the test list on oss and it seems
> > > > to work fine.
> > > >
> > > > Let try it here then, I'm going to sign this and see if it come
> > > > back to me with a valid sig.
> > >
> > > Grr try #2
> >
> > Shown as invalid here - as the signature of Michael. I mentioned this
> > a few times already to.
> >
> > Signing this as well, but I expect it will come out as invalid too.
>
> For what is worth, gpg tells me on your email:
>
> gpg: Signature made Wed 28 Jan 2009 09:22:00 PM CET using DSA key ID
> A59984C7 gpg: Good signature from "Martin Steigerwald
> <Martin@Lichtvoll.de>" gpg: aka "Martin Steigerwald
> <Martin.Steigerwald@Web.de>" gpg: aka "Martin
> Steigerwald (Helios) <Martin@Lichtvoll.de>" gpg: aka
> "Martin Steigerwald <Martin.Steigerwald@Googlemail.com>"
>
> So maybe it's not the mailling list itself, but something else?
Strange. A bug in KMail with decoding GPG signaturesin *some* mails?
However I did find this only on the XFS mailing list so far. If I find
time I will take a closer look tomorrow.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-28 22:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 8:28 xfs open questions Michael Monnerie
2009-01-27 13:58 ` Eric Sandeen
2009-01-28 8:37 ` Michael Monnerie
2009-01-28 9:30 ` Mark Goodwin
2009-01-28 15:10 ` Eric Sandeen
2009-01-29 5:27 ` Mark Goodwin
2009-01-29 22:39 ` Christoph Hellwig
2009-01-28 17:04 ` Christoph Hellwig
2009-01-27 23:03 ` Michael Monnerie
2009-01-28 4:16 ` Russell Cattelan
2009-01-28 8:52 ` Michael Monnerie
2009-01-28 14:52 ` Russell Cattelan
2009-01-28 15:09 ` Russell Cattelan
2009-01-28 20:22 ` invalidated gpg signatures (was: Re: xfs open questions) Martin Steigerwald
2009-01-28 20:37 ` Iustin Pop
2009-01-28 22:44 ` Martin Steigerwald [this message]
2009-01-29 18:01 ` Michael Monnerie
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=200901282344.32351.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=iusty@k1024.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.