all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: What level to put STARTTLS certificates
Date: Wed, 15 Jun 2011 15:01:58 -0500	[thread overview]
Message-ID: <87mxhisw21.fsf@lifelogs.com> (raw)
In-Reply-To: m3vcw7ymlz.fsf@quimbies.gnus.org

On Wed, 15 Jun 2011 20:29:28 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> ;;(setq smtpmail-starttls-credentials
LMI> ;;      '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert")))

LMI> But it strikes me that this is probably on the totally wrong level.  I
LMI> mean, any TLS connection can have user keys/certs connected to them, so
LMI> it seems to me that the right level to control this is on the
LMI> network-stream.el level, and not on the
LMI> smtpmail.el/pop3.el/nntp.el/imap.el level.

LMI> So I think I'll get rid of that variable, and put this stuff into
LMI> network-stream.el instead.

Cool.

LMI> I'm thinking the right place to stash this is in ~/.authinfo, since
LMI> these are credentials.  The format will be

LMI> machine smtp.gmail.com port 587 tls-key file:~/.my_smtp_tls.key tls-cert file:~/.my_smtp_tls.cert

LMI> Any objections?

Why do you need a file: prefix?  It should only work with local files
(we pass the file names in `gnutls-boot' to GnuTLS with
`gnutls_certificate_set_x509_key_file' so remote files can't work).  We
could support inlined certificates I guess, but it seems like it's
better to assume the token is a file name and extend it later.  It's by
far the most common case and the only one gnutls.c supports right now.

Looks good otherwise.

Ted




  reply	other threads:[~2011-06-15 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 18:29 What level to put STARTTLS certificates Lars Magne Ingebrigtsen
2011-06-15 20:01 ` Ted Zlatanov [this message]
2011-06-15 21:25   ` Lars Magne Ingebrigtsen
2011-06-16  3:43     ` Ted Zlatanov
2011-06-21 19:28       ` Lars Magne Ingebrigtsen

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=87mxhisw21.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.