Gnus development mailing list
 help / color / mirror / Atom feed
From: deskpot@myrealbox.com (Vasily Korytov)
Subject: Re: What method do *you* use for signing Usenet posts?
Date: Mon, 20 Jan 2003 04:17:49 +0300	[thread overview]
Message-ID: <8765skaabm.fsf@unix.home> (raw)
In-Reply-To: <878yxgabna.fsf@unix.home> (deskpot@myrealbox.com's message of "Mon, 20 Jan 2003 03:49:13 +0300")

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

>>>>> "VK" == Vasily Korytov writes:

>>>>> "asf" == Andreas Fuchs writes:
 asf> IMHO, there is no way to prefer one over the other: If there are mime
 asf> parts in the message, it should be signed as a multipart, and if there
 asf> is no mime part in it, gnus should not put one in, for size and
 asf> compatibility considerations.

 VK> Ha. Seems, you simply don't know much about ``compatibility
 VK> considerations''. Some MUAs only have the support for RFC1991, some --
 VK> only for 2015. So there's a good reason to specify it sometimes
 VK> manually.

Yeah, one thing more about ``compatibility considerations'' and ``broken
email gateways'', both mentioned by you. Well, I had a POP3 accound on
the M$ME server -- and this machine did weird things with PGP
signatures. The signed part was left, the signature was cut, the whole
former message was attached as application/ms-tnef -- having a normal
PGP-signed message on the SMTP input. So, the signatures were
practically deleted. But in RFC1991-style messages this stupid Exchange
couldn't find the text part -- and removed everything.

So, nothing is so simple. RFC1991 isn't the compatibility aid, as you
propose it to be.

---Vas

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-01-20  1:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 17:26 Kirk Strauser
2003-01-19 18:12 ` Josh Huber
2003-01-19 18:34   ` Kirk Strauser
2003-01-19 20:03 ` Vasily Korytov
2003-01-19 21:19   ` Xavier MAILLARD
2003-01-19 22:18   ` Kirk Strauser
2003-01-19 23:02     ` Simon Josefsson
2003-01-19 23:19     ` Vasily Korytov
2003-01-19 23:30       ` Andreas Fuchs
2003-01-19 23:43         ` Josh Huber
2003-01-20  7:45           ` Andreas Fuchs
2003-01-21  6:07             ` Lars Magne Ingebrigtsen
2003-01-21  8:46               ` Xavier MAILLARD
2003-01-21 10:03                 ` Lars Magne Ingebrigtsen
2003-01-21  9:31               ` Andreas Fuchs
2003-01-21  9:48                 ` Andreas Fuchs
2003-01-21 10:05                 ` Lars Magne Ingebrigtsen
2003-01-19 23:45         ` Vasily Korytov
2003-01-20  0:29           ` Andreas Fuchs
2003-01-20  0:49             ` Vasily Korytov
2003-01-20  1:17               ` Vasily Korytov [this message]
2003-01-20 10:25         ` Simon Josefsson

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=8765skaabm.fsf@unix.home \
    --to=deskpot@myrealbox.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;
as well as URLs for NNTP newsgroup(s).