From: Elias Oltmanns <eo@nebensachen.de>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: [Patch] Make tls.el support certificate verification
Date: Fri, 16 Nov 2007 18:22:52 +0100 [thread overview]
Message-ID: <87d4uaksur.fsf@denkblock.local> (raw)
In-Reply-To: v9r6j0frah.fsf@marauder.physik.uni-ulm.de
Hi Reiner,
Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> On Thu, Nov 08 2007, Elias Oltmanns wrote:
>
>> Simon Josefsson <simon@josefsson.org> wrote:
>>> Let's wait for copyright papers and then apply the patch in both
>>> CVS's.
>>
>> Papers have been signed and receipt has been acknowledged. Please
>> apply.
>
> Thanks.
>
>> Could someone please look at [1] and [2] as well? These patches are bug
>> fixes and recent bug reports wrt agentised servers (see [3]) seem to be
>> related.
>
> Could you please provide ChangeLog entries for these patches?
Well, I sent ChangeLog entries a week ago (see [1] and [2]) but nothing
has shown up in cvs yet. The same applies to my tls.el patch although
I'm probably to be blamed for that since I haven't provided a ChangeLog
entry for that one yet. So, here it goes:
--8<---------------cut here---------------start------------->8---
* tls.el: Check certificates against trusted root certificates. Also,
provide an option to check if GNU TLS complained about a mismatch
between the hostname provided in the certificate and the name of the
host connnecting to. New (customizable) variables are: tls-checktrust,
tls-untrusted, tls-hostmismatch.
--8<---------------cut here---------------end--------------->8---
BTW: It has happened several times in the past that messages I sent to
the ding list went (seemingly) unnoticed. This is particularly annoying
if the message actually contains a ready made patch to fix a bug and all
I'm asking for is to review the patch and tell me what's wrong with it
so it can be committed eventually. Curiously enough, the message I
finally got a response to (the one that started this thread) was about
adding a new feature rather than fixing a bug in existing code. It also
strikes me that this message went to both, the ding list as well as
emacs-devel. This makes me wonder whether I should generally send
patches to the emacs-devel list rather than the ding list even if they
concern the gnus trunk. Or should I just Cc one of the Gnus developers
instead? In that case, is there a source where I can see who is
maintaining which part of Gnus?
Regards,
Elias
[1] <http://permalink.gmane.org/gmane.emacs.gnus.general/65609>
[2] <http://permalink.gmane.org/gmane.emacs.gnus.general/65611>
next prev parent reply other threads:[~2007-11-16 17:22 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d4uaksur.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=ding@gnus.org \
--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.