From: Lars Ingebrigtsen <larsi@gnus.org>
To: Julian Scheid <julians37@gmail.com>
Cc: 35787@debbugs.gnu.org
Subject: bug#35787: 26.2; gnutls: accessing raw server certificate data
Date: Tue, 09 Jul 2019 04:42:58 +0200 [thread overview]
Message-ID: <87r270dj2l.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CAD1CDTUctQqDsT6Kun1yB-eGzAHF8N9Vu3q1nzjamp9pvXq_8w@mail.gmail.com> (Julian Scheid's message of "Sat, 18 May 2019 13:48:47 +1200")
Julian Scheid <julians37@gmail.com> writes:
> Hello, I would like to request a feature: accessing the raw certificate
> of a server connected to via `gnutls-negotiate' (or such).
>
> Currently, `gnutls-peer-status' only allows accessing high-level
> information extracted from the certificate, such as the issuer, but not
> the certificate data itself.
Other details are returned in the process object, like
gnutls_x509_crt_get_fingerprint of the certificate.
> Access to the raw certificate data would allow implementing the
> `tls-server-endpoint' channel binding type as per
> https://tools.ietf.org/html/rfc5929#section-4.1 , which requires
>> [t]he hash of the TLS server's certificate [RFC5280] as it
>> appears, octet for octet, in the server's Certificate message. Note
>> that the Certificate message contains a certificate_list, in which
>> the first element is the server's certificate.
Does this hash relate in any way to gnutls_x509_crt_get_fingerprint?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-09 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 1:48 bug#35787: 26.2; gnutls: accessing raw server certificate data Julian Scheid
2019-07-09 2:42 ` Lars Ingebrigtsen [this message]
2019-07-09 4:20 ` Julian Scheid
2019-07-09 13:44 ` Lars Ingebrigtsen
2019-09-24 5:44 ` Lars Ingebrigtsen
2019-09-24 7:36 ` Julian Scheid
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=87r270dj2l.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=35787@debbugs.gnu.org \
--cc=julians37@gmail.com \
/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.