Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Canonical methods for digitally signing and verifying
Date: 17 Dec 2000 12:40:35 -0500	[thread overview]
Message-ID: <ltu283c5f0.fsf@asfast.com> (raw)
In-Reply-To: <ilu4s0387py.fsf@localhost.localdomain>

Simon Josefsson <sj@extundo.com> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
> > Assuming that my Spanish friend is using an email agent such as
> > Outlook or Netscape to read my letters, and assuming that she does
> > nothing to decode or verify my signature, is it likely that those two
> > email clients do the right thing with the quoted printable text that
> > I'm sending via gnus within my digitally signed message, and that the
> > characters will be converted back into the 8bit Spanish characters
> > when my friend is reading her email?
> 
> Yes.

Thanks.  Not using either of those two programs for email, it would
have been hard for me to verify this myself.  Therefore, your answer
was quite helpful.

And congratulations for deciphering and understanding my long,
run-on sentence!  :)


> > I'd like to start digitally signing ALL my outgoing messages
> 
> Signing posts to public mailing lists is not generally useful, IMHO.
> (Mostly because of all programs out there with poor MIME support, not
> to mention PGP/MIME or S/MIME.)  Some ML managers will even destroy
> your signature to make it even more of a hassle.

Well, I was thinking of configuring gnus to always sign my outgoing
emails, but I guess that isn't a good idea.  I suppose that I'll have
to put something into my gnus setup to make the decision on a
group-by-group basis as to whether a message gets signed or not.

It doesn't appear that `gnus-posting-styles' can help me with this,
right?

Therefore, here's my idea as to how to do this: I'll use
`gnus-message-mode-hook' to set a buffer-specific variable based on
the group name.  This variable will be a flag which is set to `t' if I
want to sign my messages by default.  Then, since I already have a
wrapper around `message-send-and-exit', in this wrapper I'll look at
this buffer-specific flag to determine whether I sign the message or
not.

How does this idea sound?  Has anyone come up with other, more
elegant ways to do this sort of thing?

Thanks in advance.

-- 
 Lloyd Zusman
 ljz@asfast.com



  reply	other threads:[~2000-12-17 17:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-15 17:39 Lloyd Zusman
2000-12-15 18:01 ` Kai Großjohann
2000-12-15 18:50   ` Lloyd Zusman
2000-12-15 18:57     ` ShengHuo ZHU
2000-12-15 21:08       ` Lloyd Zusman
2000-12-15 21:30         ` ShengHuo ZHU
2000-12-15 21:45           ` Lloyd Zusman
2000-12-17 14:04             ` Simon Josefsson
2000-12-17 17:40               ` Lloyd Zusman [this message]
2000-12-17 20:55                 ` Charles Sebold

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=ltu283c5f0.fsf@asfast.com \
    --to=ljz@asfast.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).