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 15:44:42 +0200 [thread overview]
Message-ID: <m38st79vat.fsf@gnus.org> (raw)
In-Reply-To: <CAD1CDTUFXkhuGyiJcsR5QiRyyZ9gDp+V6N=-ip85_M4p4crp5A@mail.gmail.com> (Julian Scheid's message of "Mon, 8 Jul 2019 22:20:46 -0600")
Julian Scheid <julians37@gmail.com> writes:
> So, to make this work it looks like I'd need either
>
> 1) the fingerprint, but using the hash function as required by the RFC, or
> 2) the certificate as a binary blob.
I think putting the signature itself in the process object (in addition
to all the details) makes some sense, but perhaps it's wastes
unnecessary memory...
There's gnutls-peer-status, and that could also be amended to return the
full certificate. But, again, that's also called for virtually any TLS
connection.
Perhaps a new function to return the actual certificate? And perhaps it
should just return the entire certificate chain?
Anybody got an opinion here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-09 13:44 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
2019-07-09 4:20 ` Julian Scheid
2019-07-09 13:44 ` Lars Ingebrigtsen [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38st79vat.fsf@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).