Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #160651 > unrolled thread

Your attempts to communicate

Back to article view | Back to linux.debian.user

Contents

  Your attempts to communicate Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-17 01:50 +0100
    Re: Your attempts to communicate John Hasler <jhasler@newsguy.com> - 2015-11-17 03:10 +0100
      Re: Your attempts to communicate "Thomas Schmitt" <scdbackup@gmx.net> - 2015-11-17 08:50 +0100
    Re: Your attempts to communicate Chris Bannister <cbannister@slingshot.co.nz> - 2015-11-17 06:30 +0100
    Re: Your attempts to communicate <tomas@tuxteam.de> - 2015-11-17 09:10 +0100
      Re: Your attempts to communicate John Hasler <jhasler@newsguy.com> - 2015-11-17 14:10 +0100
        Re: Your attempts to communicate <tomas@tuxteam.de> - 2015-11-17 14:20 +0100
          Re: Your attempts to communicate John Hasler <jhasler@newsguy.com> - 2015-11-17 19:50 +0100
    Re: Your attempts to communicate Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2015-11-17 14:50 +0100
      Re: Your attempts to communicate Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-17 15:20 +0100
        Re: Your attempts to communicate Bob Bernstein <poobah@ruptured-duck.com> - 2015-11-17 19:10 +0100
          Re: Your attempts to communicate Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-17 21:10 +0100
        Re: Your attempts to communicate Christoph Anton Mitterer <calestyo@scientia.net> - 2015-11-17 19:30 +0100
          Re: Your attempts to communicate Bob Bernstein <poobah@ruptured-duck.com> - 2015-11-17 19:50 +0100
            Re: Your attempts to communicate Christoph Anton Mitterer <calestyo@scientia.net> - 2015-11-17 20:00 +0100
              Re: Your attempts to communicate Bob Bernstein <poobah@ruptured-duck.com> - 2015-11-17 20:10 +0100
            Re: Your attempts to communicate Gene Heskett <gheskett@shentel.net> - 2015-11-18 00:20 +0100
              Re: Your attempts to communicate Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-18 00:40 +0100
                Re: Your attempts to communicate Gene Heskett <gheskett@shentel.net> - 2015-11-18 01:10 +0100
          Re: Your attempts to communicate "Thomas Schmitt" <scdbackup@gmx.net> - 2015-11-17 19:50 +0100

#160651 — Your attempts to communicate

My email client chokes on your signature.  If I make any attempt to reply, my 
email client freezes.

So I have deleted both your emails.

Try: sorting out your signature (I don't know what is wrong with it), or 
omitting your signature.

I may not be the only one having problems.

Lisi

[toc] | [next] | [standalone]

#160652

Lisi writes:
> My email client chokes on your signature.  If I make any attempt to reply, my 
> email client freezes.

As he does not use a proper delimiter he doesn't really have a
signature.  His messages end with

Cheers,
Chris.

That's not correct, but it is no excuse for Gmail to freeze up.
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]

#160657

Hi,

Lisi Reisz wrote:
> My email client chokes on your signature.

My alpine mail client showed a warning about MIME signature,
probably because of:

  Content-Type: multipart/signed; micalg="sha-512";
    protocol="application/x-pkcs7-signature";
    boundary="=-q9gdJ6oE7VoDos3CeFlt"


> As he does not use a proper delimiter he doesn't really have a
> signature.  His messages end with
> Cheers,
> Chris

In the mailbox file i do see that part and its MIME headers:

  Cheers,
  Chris
  --=-q9gdJ6oE7VoDos3CeFlt
  Content-Type: application/x-pkcs7-signature; name="smime.p7s"
  Content-Disposition: attachment; filename="smime.p7s"
  Content-Transfer-Encoding: base64

  ...base64.blob...

alpine shows the message, but not the second MIME part.
Strange ...


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#160654

On Tue, Nov 17, 2015 at 12:42:55AM +0000, Lisi Reisz wrote:
> My email client chokes on your signature.  If I make any attempt to reply, my 
> email client freezes.
> 
> So I have deleted both your emails.
> 
> Try: sorting out your signature (I don't know what is wrong with it), or 
> omitting your signature.
> 
> I may not be the only one having problems.

Maybe it's because he uses openssl to sign his mail?

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

[toc] | [prev] | [next] | [standalone]

#160658

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Nov 17, 2015 at 12:42:55AM +0000, Lisi Reisz wrote:
> My email client chokes on your signature.  If I make any attempt to reply, my 
> email client freezes.
> 
> So I have deleted both your emails.
> 
> Try: sorting out your signature (I don't know what is wrong with it), or 
> omitting your signature.
> 
> I may not be the only one having problems.

FWIW, mutt copes fine. It even hands over to OpenSSL to check sig.

Perhaps a bug in KMail?

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlZK2EEACgkQBcgs9XrR2kaosACeL+b0kSohhuxvRkS3ycgBQw6T
sGEAnibtKc8Sqsp2Kc495UwC9/UCJdQV
=+8pC
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#160666

Chris Bannister writes:
> Perhaps a bug in KMail?

Or Gmail buggering up the OpenSSL signature in such a way as to tickle a
bug in Kmail.  I would expect Gmail to mangle cryptographic signatures.
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]

#160667

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Nov 17, 2015 at 07:08:18AM -0600, John Hasler wrote:
> Chris Bannister writes:
> > Perhaps a bug in KMail?
> 
> Or Gmail buggering up the OpenSSL signature in such a way as to tickle a
> bug in Kmail.  I would expect Gmail to mangle cryptographic signatures.

Sure, I would expect Gmail to do nearly anything, but KMail falling flat
on its face due to mangled input coming from somewhere out there is in
my eyes a bug (or worse). Saying "Uh, sorry, I can't grok this mail" would
be OK, naturally.

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlZLIFgACgkQBcgs9XrR2kboDACcDK6Z9sbsyYQfvgczCGS+wQvl
+f0AnidsFIHIuyCTs1S003Qfkm8GSUt9
=b719
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#160686

tomas writes:
> Sure, I would expect Gmail to do nearly anything, but KMail falling
> flat on its face due to mangled input coming from somewhere out there
> is in my eyes a bug (or worse).

Yes, I said it was a bug in Kmail.  I was pointing out that it may be
one that is only triggered when a particular type of signature is
mangled by Gmail, which might explain why only Lisi sees it.
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]

#160668

Am 17.11.2015 um 01:42 schrieb Lisi Reisz:

> My email client chokes on your signature.  If I make any attempt to reply, my 
> email client freezes.

Then your mail client is broken.

> So I have deleted both your emails.
> 
> Try: sorting out your signature (I don't know what is wrong with it),

AFAICT nothing is wrong with it.
BTW: it's not a signature in the sense of some text at the bottom of a
message but a detached cryptographic signature.

> or 
> omitting your signature.

Or even better: you could use a mail client that actually works.

-- 
Regards
  mks

[toc] | [prev] | [next] | [standalone]

#160669

On Tuesday 17 November 2015 13:42:54 Markus Schc3b6nhaber wrote:
> Am 17.11.2015 um 01:42 schrieb Lisi Reisz:
> > My email client chokes on your signature.  If I make any attempt to
> > reply, my email client freezes.
>
> Then your mail client is broken.
>
> > So I have deleted both your emails.
> >
> > Try: sorting out your signature (I don't know what is wrong with it),
>
> AFAICT nothing is wrong with it.
> BTW: it's not a signature in the sense of some text at the bottom of a
> message but a detached cryptographic signature.
>
> > or
> > omitting your signature.
>
> Or even better: you could use a mail client that actually works.

He seemed not be getting replies so I was trying to suggest what might be 
wrong.

I can live without being able to read emails form one individual ever.  If it 
happens with a lot of people I shall indeed report a bug.

Lisi

[toc] | [prev] | [next] | [standalone]

#160679

[Multipart message — attachments visible in raw view] — view raw

I believe the poster is trying to sign his messages with 
smime. My fairly recent version of alpine 2.20 tells me that his 
messages bear a "cryptographic signature," but that those 
signatures cannot be "verified."

Please allow me to do the samd, i.e. sign with smime.

-- 
Bob Bernstein

[toc] | [prev] | [next] | [standalone]

#160695

On Tuesday 17 November 2015 17:31:06 Bob Bernstein wrote:
> I believe the poster is trying to sign his messages with
> smime. My fairly recent version of alpine 2.20 tells me that his
> messages bear a "cryptographic signature," but that those
> signatures cannot be "verified."
>
> Please allow me to do the samd, i.e. sign with smime.

Yours is fine.  "Not enough information to check signature validity."  But I 
haven't downloaded your key.

I have been using KMail for years.  It is not perfect.  This is the first time 
I have hit this.  If it applies only to me, as seemsoot be the case, then it 
is a non-issue.

Lisi

[toc] | [prev] | [next] | [standalone]

#160683

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2015-11-17 at 14:18 +0000, Lisi Reisz wrote:
> I can live without being able to read emails form one individual
> ever.

Gosh... I never got so much meta-answers around one of my mails
itself...

In any case, if your MUA crashes based on whichever mail it reads,...
than it's likely a bug, and possible even a security critical bug.
Even if my MUA[0] would send bogus mails, then you client should still
fail gracefully on them.

Anyway,.. I don't think that anything is wrong with the S/MIME that
Evolution applies, in fact, as you could read, other people could
verify it.

If not, a reason may be that you don't trust the CA, which signed my
user cert, but even that wouldn't be a reason to crash.


Cheers,
Chris.


[0] And as you can see from the headers, I'm using Evolution, which is
in my personal opinion the worst piece of software existing (it even
caused data corruption to mails,... I just haven't found time to dump
it where it belongs to

[toc] | [prev] | [next] | [standalone]

#160684

On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:

> Anyway,.. I don't think that anything is wrong with the S/MIME 
> that Evolution applies, in fact, as you could read, other 
> people could verify it.

Aha. Did evolution verify my smime sig in the message I just 
sent to the list?

If the Debian Social Contract permitted wagering, I would stack 
a few chips that your answer to that would be "no."

FULL DISCLOSURE: I haven't taken a look at my smime config here 
on alpine in quite some time...

Thanks,

-- 
Bob Bernstein

[toc] | [prev] | [next] | [standalone]

#160688

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2015-11-17 at 13:40 -0500, Bob Bernstein wrote:
> Aha. Did evolution verify my smime sig in the message I just
> sent to the list?
Nope, your cert has expired on 2015-03-12.

Chris.

[toc] | [prev] | [next] | [standalone]

#160690

[Multipart message — attachments visible in raw view] — view raw

On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:

> ..your cert has expired on 2015-03-12.

That's helpful, thank you.

It explains why the message's sig cannot even be verified by the 
running instance of alpine that created it (if I look at said 
message in my sent messages file).

I think alpine should refuse to use an expired cert. Hmmm... 
Perhaps I should query the alpine list on that point?

_Or_, perhaps I should re-dedicate myself to learning about 
smime 
and stop expecting that, if I make enough tweaks, it will "just 
work."

Oh well, Thanks all,

-- 
Bob Bernstein

[toc] | [prev] | [next] | [standalone]

#160709

On Tuesday 17 November 2015 13:40:06 Bob Bernstein wrote:

> On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
> > Anyway,.. I don't think that anything is wrong with the S/MIME
> > that Evolution applies, in fact, as you could read, other
> > people could verify it.
>
> Aha. Did evolution verify my smime sig in the message I just
> sent to the list?
>
> If the Debian Social Contract permitted wagering, I would stack
> a few chips that your answer to that would be "no."
>
> FULL DISCLOSURE: I haven't taken a look at my smime config here
> on alpine in quite some time...
>
> Thanks,

Showed in yellow here, indicating it could not be verified.  Same kmail 
as Lisi's.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#160710

On Tuesday 17 November 2015 23:18:01 Gene Heskett wrote:
> On Tuesday 17 November 2015 13:40:06 Bob Bernstein wrote:
> > On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
> > > Anyway,.. I don't think that anything is wrong with the S/MIME
> > > that Evolution applies, in fact, as you could read, other
> > > people could verify it.
> >
> > Aha. Did evolution verify my smime sig in the message I just
> > sent to the list?
> >
> > If the Debian Social Contract permitted wagering, I would stack
> > a few chips that your answer to that would be "no."
> >
> > FULL DISCLOSURE: I haven't taken a look at my smime config here
> > on alpine in quite some time...
> >
> > Thanks,
>
> Showed in yellow here, indicating it could not be verified.  Same kmail
> as Lisi's.

Yes - I turn the yellow off because I can't read it, but it said that it could 
not be verified.  How do you get on with Chris's signature?  Is the bug, if 
it be a bug, mine alone?

Lisi
>
>
> Cheers, Gene Heskett

[toc] | [prev] | [next] | [standalone]

#160713

On Tuesday 17 November 2015 18:33:04 Lisi Reisz wrote:

> On Tuesday 17 November 2015 23:18:01 Gene Heskett wrote:
> > On Tuesday 17 November 2015 13:40:06 Bob Bernstein wrote:
> > > On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
> > > > Anyway,.. I don't think that anything is wrong with the S/MIME
> > > > that Evolution applies, in fact, as you could read, other
> > > > people could verify it.
> > >
> > > Aha. Did evolution verify my smime sig in the message I just
> > > sent to the list?
> > >
> > > If the Debian Social Contract permitted wagering, I would stack
> > > a few chips that your answer to that would be "no."
> > >
> > > FULL DISCLOSURE: I haven't taken a look at my smime config here
> > > on alpine in quite some time...
> > >
> > > Thanks,
> >
> > Showed in yellow here, indicating it could not be verified.  Same
> > kmail as Lisi's.
>
> Yes - I turn the yellow off because I can't read it, but it said that
> it could not be verified.  How do you get on with Chris's signature? 
> Is the bug, if it be a bug, mine alone?
>
> Lisi
>
> > Cheers, Gene Heskett

I did not try to reply.  If I am to have trouble, that is the trigger.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#160685

Hi,

> other people could verify it.

Urm, not in my case. It's just that alpine can stand it.

The error message when opening
  Message-ID: <1447719799.6941.4.camel@scientia.net>
is
  Couldn't verify S/MIME signature: certificate verify error

The header 
  Content-Type: multipart/signed; micalg="sha-512";
      protocol="application/x-pkcs7-signature";
      boundary="=-q9gdJ6oE7VoDos3CeFlt"
brings me to
  https://www.rfc-editor.org/rfc/rfc2311.txt
  https://www.rfc-editor.org/rfc/rfc2315.txt
where i stand somewhat clueless.

The mail from Bob Bernstein
  Message-ID: <alpine.DEB.2.20.1511171226140.24000@qrovna.ybpnyqbznva>
has
  Content-Type: multipart/signed; protocol="application/pkcs7-signature";
    micalg=sha1; BOUNDARY="8323328-613464707-1447781475=:24000"
It produces the same error message in alpine:
  Couldn't verify S/MIME signature: certificate verify error

Locally installed alpine -v says
  Alpine 2.11 (DEB 23 2013-08-11) built Mon Sep 8 02:01:57 UTC 2014 on brahms


Have a nice day :)

Thomas

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web