Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@void.at>
Subject: Re: What method do *you* use for signing Usenet posts?
Date: Mon, 20 Jan 2003 00:29:41 +0000 (UTC)	[thread overview]
Message-ID: <87fzroachf.fsf@eris.void.at> (raw)
In-Reply-To: <87bs2cg0va.fsf@unix.home>

Today, Vasily Korytov <deskpot@myrealbox.com> wrote:
>  asf> I wonder - why does the user have to decide such things? Would
>  asf> it not make more sense to just specify the method and let gnus
>  asf> itself figure out whether it should use mime or not (i.e. if
>  asf> there is a mime part, use detached signatures, if not, use plain
>  asf> pgp)?
> 
> IMHO, the user _has_ to decide it. For example, I prefer PGP/MIME for
> mail, but when I use PGP for Usenet (I usually don't, but that's
> another story), I want RFC1991 PGP.
> 
> I can prefer having PGP/MIME for one recipient, and old style PGP for
> another. 

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

> It may be really useful, so why eliminating this option (why removing
> options anyway -- it's the Outlook way, we all know, in what it
> results)?

I don't intend to rename a common option, I only suggested that the
<secure> code be made to work as expected - secure a message and ensure
that most receipients (even outlook users, stupid email gateways which
don't grok mime) can read and decode it.

> BTW, the behaviour, you want, can be made through hooks.

Absolutely. But in my opinion, it's a reasonable default, so why not
make it one? (-:

-- 
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs




  reply	other threads:[~2003-01-20  0:29 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 [this message]
2003-01-20  0:49             ` Vasily Korytov
2003-01-20  1:17               ` Vasily Korytov
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=87fzroachf.fsf@eris.void.at \
    --to=asf@void.at \
    /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).