Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: timotheus <timotheus@tstotts.net>
Cc: emacs-devel@gnu.org, mh-e-devel@lists.sourceforge.net, ding@gnus.org
Subject: Re: smime.el: security concerns?
Date: Fri, 13 Jul 2007 19:08:57 -0400	[thread overview]
Message-ID: <E1I9UFt-0006fB-PW@fencepost.gnu.org> (raw)
In-Reply-To: <m2tzs8b57h.fsf@tstotts.net> (message from timotheus on Fri, 13 Jul 2007 13:09:54 -0400)

      - `call-process' / `call-process-region' (temporary files in /tmp/?)
      - environment variable(s) for password passing
      - documentation encourages use of un-passworded .pem
      - password caching via elisp instead of external agent
	- personally avoid, even for tramp + SSH
      - the very manual .pem key/crt setup was tricky

We have eliminated the same problems in the rest of Emacs; shouldn't
we fix smime.el to get rid if them too?



  reply	other threads:[~2007-07-13 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  3:58 proposed patch to enable MH-E usage of GNU + EPG timotheus
2007-07-12 21:23 ` Richard Stallman
2007-07-13  5:31   ` Bill Wohler
2007-07-13 15:14     ` timotheus
2007-07-13 16:13       ` smime.el: security concerns? (was: proposed patch to enable MH-E usage of GNU + EPG) Reiner Steib
2007-07-13 17:09         ` smime.el: security concerns? timotheus
2007-07-13 23:08           ` Richard Stallman [this message]
2007-07-13 23:09       ` proposed patch to enable MH-E usage of GNU + EPG Richard Stallman
2007-07-14  0:30         ` timotheus
2007-07-13 23:10     ` Richard Stallman

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=E1I9UFt-0006fB-PW@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=mh-e-devel@lists.sourceforge.net \
    --cc=timotheus@tstotts.net \
    /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).