Gnus development mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@s.netic.de>
Subject: Re: MML, message-send-hook and automatically GnuPG-signing messages.
Date: 18 Jan 2000 14:50:33 +0100	[thread overview]
Message-ID: <87ya9n7al2.fsf@deneb.cygnus.argh.org> (raw)
In-Reply-To: Jonas Steverud's message of "18 Jan 2000 13:57:55 +0100"

Jonas Steverud <d4jonas@dtek.chalmers.se> writes:

> If I understand it correctly this would work:
> In message-send-hook having a function adding
> <#encrypted>/<#/encrypted> (or whatever) around the entire text and
> then having a buffer that looks like:
> 
> ----------8<--------
> -----texts follows...----
> <#encrypted>
> Some text...
> <#attachment ...>
> ...more text.
> -- 
> .sig
> <#/encrypted>
> ----------8<--------

Yes, that's the idea.  You probably want to add extra information to the
`<#encrypted>' tag, for example the recpients' key ID.

> I will dig into it later when I have a Gnus that works with
> mml-blah-alist.

Glad you found it.  I guess the variable is only defined if `mml' has
been loaded, which happens automatically when you compose a message
(and not upon Gnus startup).

> > I don't think an additional hook is required, in fact, I would be
> > surprised. ;)
> 
> See other mail, I found message-send-*-hook. I blame the manual.

`message-send-*-hook' won't work, that's too late.  You have to bind
`mm-use-ultra-safe-encoding' to `t' while encoding the parts over which
the signature is to be calculated (this prohibits 8-bit data and other
nasty things, as mandated by RFC 2015).

> > You only need additional data structures for decrypting and verifying
> > signatures.
> 
> You forgot the `"' around the word "only"... ;-)

Well, I should have put it before `for'. ;)

> I spoke with the people in se.dator.sys.unix (swedish *nix group) and
> the conclusion was that although it was not 100% safe one could fairly
> sure that it was safe enough to use on Linux/Solaris. 

Linux and Solaris are completely different in this regard. Solaris
(at least the version I tested) is safe, while Linux isn't.

> There where possibilities to intercept my passphrase but the work
> and luck that was needed was too great. You needed to be root to
> begin with (which is a bit hard on a well administred system).

In fact, this is not necessary, and that's the problem. :(




  parent reply	other threads:[~2000-01-18 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <wtnpuv5wurx.fsf@licia.dtek.chalmers.se>
2000-01-16  8:14 ` Florian Weimer
     [not found]   ` <wtn3drwabws.fsf@licia.dtek.chalmers.se>
2000-01-17 21:42     ` Kai Großjohann
2000-01-18  5:26     ` Florian Weimer
     [not found]       ` <wtnr9ffbrbs.fsf@licia.dtek.chalmers.se>
2000-01-18 11:39         ` Florian Weimer
     [not found]           ` <wtn1z7f8rl8.fsf@licia.dtek.chalmers.se>
2000-01-18 13:50             ` Florian Weimer [this message]
     [not found]               ` <wtn7lh7id3y.fsf@licia.dtek.chalmers.se>
2000-01-18 19:12                 ` Florian Weimer

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=87ya9n7al2.fsf@deneb.cygnus.argh.org \
    --to=fw@s.netic.de \
    /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).