<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — How to verify a certificate chain using WolfSSL]]></title>
		<link>https://www.wolfssl.com/forums/topic2256-how-to-verify-a-certificate-chain-using-wolfssl.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic2256.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in How to verify a certificate chain using WolfSSL.]]></description>
		<lastBuildDate>Tue, 31 Dec 2024 15:22:47 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: How to verify a certificate chain using WolfSSL]]></title>
			<link>https://www.wolfssl.com/forums/post8159.html#p8159</link>
			<description><![CDATA[<p>Hello courtneyendic735, </p><p>My name is Anthony and I am a member of the wolfSSL team.</p><p>We&#039;ve actually noticed the same problem earlier and are looking into a fix.&nbsp; Currently, we have 2 solutions. </p><p>- Please have a look at <a href="https://github.com/wolfSSL/wolfCLU/pull/159">https://github.com/wolfSSL/wolfCLU/pull/159</a> .&nbsp; This is not a long term fix as it has side effects when doing OCSP and CRL verifications. I am currently looking into improving this PR.&nbsp; Stay tuned and monitor that PR please. <br />- Please have a look at <a href="https://github.com/wolfSSL/wolfssl-examples/tree/master/certmanager">https://github.com/wolfSSL/wolfssl-exam … ertmanager</a> .&nbsp; This example will verify the chain as you described. </p><p>Here at wolfSSL we love it when people use our product.&nbsp; Can you let us know a bit about yourself and your project?&nbsp; For example: </p><p>- Where are you geographically located? <br />- What are your goals? <br />- Is this out of professional, academic or personal interest? <br />- Is there an institution associated with this effort? <br />- Any other information you care to share. </p><p>If you would like to share this information confidentially, you can send it to me via email at anthony@wolfssl.com. </p><p>Thanks and let me know if my suggestions help. </p><p>Warm regards, Anthony</p>]]></description>
			<author><![CDATA[null@example.com (anthony)]]></author>
			<pubDate>Tue, 31 Dec 2024 15:22:47 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8159.html#p8159</guid>
		</item>
		<item>
			<title><![CDATA[How to verify a certificate chain using WolfSSL]]></title>
			<link>https://www.wolfssl.com/forums/post8158.html#p8158</link>
			<description><![CDATA[<p>Hello,<br />Assuming we have a certificate chain A-&gt;B-&gt;C with a depth of 3, where A is the root certificate.</p><p>At present, it appears that the WolfSSL command line supports verifying a certificate chain with a maximum depth of 2. Namely either:</p><p>wolfssl verify -CAfile A.crt B.crt<br />or<br /><a href="https://slope3.com"><span style="color: #f8f8f8">slope game</span></a><br />wolfssl verify -CAfile B.crt -partial_chain C.crt<br />But if I want to validate the complete A-&gt;B-&gt;C certificate chain at once, how should I do it? If it is indeed not possible to do this from the command line, could anyone share a code snippet using WolfSSL to accomplish this? Thanks a lot.</p>]]></description>
			<author><![CDATA[null@example.com (courtneyendic735)]]></author>
			<pubDate>Tue, 31 Dec 2024 08:07:02 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8158.html#p8158</guid>
		</item>
	</channel>
</rss>
