Re: master 8608c10 01/02: Use a simple list of symbols in GnuTLS peer verification.

Re: master 8608c10 01/02: Use a simple list of symbols in GnuTLS peer verification.

[Lars Magne Ingebrigtsen]

Teodor Zlatanov <tzz@lifelogs.com> writes:

> +DEFUN ("gnutls-peer-status-warning-describe", Fgnutls_peer_status_warning_describe, Sgnutls_peer_status_warning_describe, 1, 1, 0,
> +       doc: /* Describe the warning of a GnuTLS peer status from `gnutls-peer-status'.*/)
> +  (Lisp_Object status_symbol)
> +{
> +  CHECK_SYMBOL (status_symbol);
> +
> +  if ( EQ (status_symbol, intern (":invalid")))
> +    return build_string ("certificate could not be verified");

This is now just a symbol-to-string mapping, so perhaps it should just
be moved to nsm.el instead?

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

Re: master 8608c10 01/02: Use a simple list of symbols in GnuTLS peer verification.

[Ted Zlatanov]

On Tue, 25 Nov 2014 16:15:47 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Teodor Zlatanov <tzz@lifelogs.com> writes:
>> +DEFUN ("gnutls-peer-status-warning-describe", Fgnutls_peer_status_warning_describe, Sgnutls_peer_status_warning_describe, 1, 1, 0,
>> +       doc: /* Describe the warning of a GnuTLS peer status from `gnutls-peer-status'.*/)
>> +  (Lisp_Object status_symbol)
>> +{
>> +  CHECK_SYMBOL (status_symbol);
>> +
>> +  if ( EQ (status_symbol, intern (":invalid")))
>> +    return build_string ("certificate could not be verified");

LMI> This is now just a symbol-to-string mapping, so perhaps it should just
LMI> be moved to nsm.el instead?

`gnutls-boot' uses it, so it wouldn't work. I think.

I looked in GnuTLS but I don't see a convenient way to avoid storing
that data on our side. All the strerror stuff is for error codes but not
verification codes.

Ted