unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: Elias Oltmanns <eo@nebensachen.de>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: [Patch] Make tls.el support certificate verification
Date: Mon, 26 Nov 2007 15:47:48 +0100	[thread overview]
Message-ID: <87myt1dpwr.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <v9oddi1k94.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 25 Nov 2007 15:18:31 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

>> After all, the mail server needn't have a certificate signed by one
>> of the well known CAs and may still be valid.  Besides, users might
>> want to specify the set of trusted root certificates depending on
>> the server emacs is connecting to.  All this seems to make proper
>> documentation more important than presetting any defaults.  Do you
>> think the provided doc strings can serve this purpose or should I
>> squeeze in a few sentences somewhere else?
>
> As tls.el is not specific to Gnus (it is in lisp/net in Emacs 22), it
> should probably not be documented in gnus.texi, maybe in
> smtpmail.texi, e.g. (info "(smtpmail)Authentication").

Gnus isn't the best place to document it, but I'm not sure smtpmail is
better.  Will it be found by searching through the normal emacs manuals?
Maybe even writing a new tls.texi to discuss all TLS related stuff is
warranted.  I don't know what the policy on new *.texi files is, if we
have too many already or whether having one per elisp package is
actually a good idea.

/Simon

  reply	other threads:[~2007-11-26 14:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 23:08 [Patch] Make tls.el support certificate verification Elias Oltmanns
2007-09-24  7:12 ` Simon Josefsson
2007-09-24 16:27   ` Reiner Steib
2007-09-25 14:42     ` Simon Josefsson
2007-11-08 18:44       ` Elias Oltmanns
2007-11-08 19:52         ` Reiner Steib
2007-11-16 17:22           ` Elias Oltmanns
2007-11-16 22:38             ` Reiner Steib
2007-11-16 23:07               ` Elias Oltmanns
2007-11-24 21:31                 ` Reiner Steib
2007-11-25  0:35                   ` Elias Oltmanns
2007-11-25 14:18                     ` Reiner Steib
2007-11-26 14:47                       ` Simon Josefsson [this message]
2007-11-27 11:10                   ` Elias Oltmanns
2007-11-28 22:05                     ` Reiner Steib
2007-11-28 22:08                     ` Coding conventions (was: [Patch] Make tls.el support certificate verification) Reiner Steib

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87myt1dpwr.fsf@mocca.josefsson.org \
    --to=simon@josefsson.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=eo@nebensachen.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.
Code repositories for project(s) associated with this public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).