Re: Built-in TLS vs. nnimap security

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> We need the callbacks for custom certificate verification, but what
> Romain describes simply needs the :verify-flags, :verify-error, and
> :verify-hostname-error flags to `gnutls-negotiate'.
> `open-gnutls-stream' doesn't pass them currently.  So the question is,
> should they be:
>
> 1) always enabled, and the user has to Customize to turn them off per
> host or globally
>
> 2) always disabled, and the user has to Customize to turn them on per
> host or globally
>
> 3) when connecting to an unknown hostname, the user is asked and then we
> save the results

I think the user should be queried if the certificate is "wrong".  I.e.,
if it's for the wrong hostname or expired and stuff like that.  And then
we should save the result.

> Similarly we should make the :priority-string and :min-prime-bits
> customizable per host, right now they are global as you and Lawrence
> Mitchell implemented them.
>
> Similarly we should have a way to set :trustfiles, :crlfiles, and
> :keylist per host or globally.  For all these settings I don't know if
> (1) or (2) or (3) is the best approach.

Yeah, the per-host storage thing is slightly tricky...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/