<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<p style="color: #777777;">

<a href="https://gitlab.com/j29280">jgh</a>

commented:

</p>

<div style="">

<p dir="auto">Fair comment.  Most commonly it'll be just the leaf, but... if we allow for an indefinite number and

combination, that means a bitfield - which no longer fits with the gnutls_session_get_flags() interface.</p>

<p dir="auto">So that would be a new api call, which I'd fully understand if you don't really want to do.

If you do - one bit position per chain position; bit0 for the leaf, bit set for ocsp-status-of-this-cert-sent.</p>

<p dir="auto">Perhaps punt on the chain-status support (we can't parse a 1.3 servercert at this time; gnutls_ext_raw_parse() crashes) and just return a single bit via gnutls_session_get_flags() if <em>any</em>

status was transmitted?</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/829#note_260526515">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/sent_notifications/64974e8aa5caab7ff6dbb0cf651857d2/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/issues/829#note_260526515"}}</script>

</p>

</div>

</body>

</html>