From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnimap ports and protocols
Date: Fri, 01 Oct 2010 14:44:39 -0500 [thread overview]
Message-ID: <87r5g9itp4.fsf@lifelogs.com> (raw)
In-Reply-To: <m3iq1lu3hi.fsf@quimbies.gnus.org>
On Fri, 01 Oct 2010 21:17:45 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> The GnuTLS layer should handle all of that. Gnus should not know about
>> certificate management; just like passwords or accepting SSH keys,
>> that's completely irrelevant to reading mail.
LMI> Yeah, but I was just wondering where the gnutls layer would stash
LMI> information like that. We certainly don't want the user to be queried
LMI> about the invalid certificate every time she connects to the IMAP
LMI> server, so it needs to be saved somewhere.
>> So I think Fgnutls_boot will need work and so on. It's not bad. I may
>> use auth-source.el to store the accepted certificates in a netrc file or
>> in the Secrets API.
LMI> The netrc file is for Humans, I think. Perhaps you can stash this in
LMI> Customize? :-)
Maybe. There's also the "trust file" concept which contains accepted
certificate authorities as a bundle. Maybe I can create a trust file to
contain accepted server certificates. GnuTLS doesn't allow multiple
trust files so this may get complicated. I'll ask gnutls-devel.
Ted
next prev parent reply other threads:[~2010-10-01 19:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:55 Lars Magne Ingebrigtsen
2010-10-01 1:00 ` Daniel Pittman
2010-10-01 13:43 ` Ted Zlatanov
2010-10-01 14:52 ` Ted Zlatanov
2010-10-01 15:19 ` Lars Magne Ingebrigtsen
2010-10-01 15:29 ` Frank Schmitt
2010-10-01 15:34 ` Lars Magne Ingebrigtsen
2010-10-01 15:46 ` Ted Zlatanov
2010-10-01 16:25 ` Lars Magne Ingebrigtsen
2010-10-01 16:45 ` Ted Zlatanov
2010-10-01 18:29 ` Lars Magne Ingebrigtsen
2010-10-01 18:41 ` Ted Zlatanov
2010-10-01 18:47 ` Lars Magne Ingebrigtsen
2010-10-01 19:05 ` Ted Zlatanov
2010-10-01 19:17 ` Lars Magne Ingebrigtsen
2010-10-01 19:44 ` Ted Zlatanov [this message]
2010-10-01 18:18 ` Sivaram Neelakantan
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=87r5g9itp4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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).