<?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 — Bad Doc]]></title>
		<link>https://www.wolfssl.com/forums/topic1756-bad-doc.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic1756.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Bad Doc.]]></description>
		<lastBuildDate>Mon, 07 Jun 2021 14:58:52 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Bad Doc]]></title>
			<link>https://www.wolfssl.com/forums/post6085.html#p6085</link>
			<description><![CDATA[<div class="quotebox"><cite>dgarske wrote:</cite><blockquote><p>Hi Scott,</p><p>Thanks for your feedback on Doxygen quality and will bring up with the team. We strive to keep things well documented, provide timely support and quality examples.</p><p>David Garske, wolfSSL</p></blockquote></div><p>David,<br />I am trying to figure out how to set an alternate name in a certificate...</p><p>The doc for &quot;wc_SetAltNames&quot;...<br /><a href="https://www.wolfssl.com/doxygen/group__ASN.html#ga90a550d9a47432f95083a8e4fe7e3626">https://www.wolfssl.com/doxygen/group__ … e4fe7e3626</a><br />gives this example...</p><div class="codebox"><pre><code>// initialize myCert
if(wc_SetSubject(&amp;myCert, ”./path/to/ca-cert.pem”) != 0) {
    // error setting alt names
}</code></pre></div><p>Subject is NOT Alternate name</p>]]></description>
			<author><![CDATA[null@example.com (Scotty2541)]]></author>
			<pubDate>Mon, 07 Jun 2021 14:58:52 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6085.html#p6085</guid>
		</item>
		<item>
			<title><![CDATA[Re: Bad Doc]]></title>
			<link>https://www.wolfssl.com/forums/post6082.html#p6082</link>
			<description><![CDATA[<p>Thanks. <br />As I look for answers, troubleshooting issues, examples, etc...&nbsp; I can show lots of issues.</p><p>I could constantly post things, but I don&#039;t want to just come across as antagonistic.</p><p>I&#039;ve also though the best example was the MSDN (from about 15 years ago).&nbsp; No one seems willing to put effort into following that model anymore.</p><p>Not just in WolfSSL...&nbsp; literally everywhere I see these shortcut tools used, the content is horrid.</p>]]></description>
			<author><![CDATA[null@example.com (Scotty2541)]]></author>
			<pubDate>Fri, 04 Jun 2021 18:05:02 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6082.html#p6082</guid>
		</item>
		<item>
			<title><![CDATA[Re: Bad Doc]]></title>
			<link>https://www.wolfssl.com/forums/post6081.html#p6081</link>
			<description><![CDATA[<p>Hi Scott,</p><p>Thanks for your feedback on Doxygen quality and will bring up with the team. We strive to keep things well documented, provide timely support and quality examples.</p><p>David Garske, wolfSSL</p>]]></description>
			<author><![CDATA[null@example.com (dgarske)]]></author>
			<pubDate>Fri, 04 Jun 2021 17:44:00 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6081.html#p6081</guid>
		</item>
		<item>
			<title><![CDATA[Bad Doc]]></title>
			<link>https://www.wolfssl.com/forums/post6072.html#p6072</link>
			<description><![CDATA[<p>Hello,<br />Not a question... a complaint.</p><p>It has always been my conclusion that anyone who uses &quot;Doxygen&quot; is demonstrating how lacks their work effort it... The output from it is virtually useless.&nbsp; Developers spend more time in headers formatting, commenting, etc...&nbsp; then just writing good doc.&nbsp; Because it spits out header comments as it&#039;s source.</p><p>Bereft of examples, lacking cross references, one has to know exactly what one is looking for in order to find it.&nbsp; A serious &quot;cart before the horse&quot; situation.</p><p>But developers slap some comments in the headers, let it spit out useless HTML, and they think the job is done.<br />Then it remains untouched, out of date from enhancements, broken information when something is changed... Because it&#039;s forgotten.</p><p>If a real document was part of the package, then a real task of updating it would exist.<br />(The only &quot;real&quot; doc I can find on this product is a PDF from version 3)</p><p>From here:<br /><a href="https://www.wolfssl.com/doxygen/group__CertsKeys.html#ga08310060e40ffdd4adb66ceca15af4c5">https://www.wolfssl.com/doxygen/group__ … eca15af4c5</a></p><p>&quot; Certificate file type found in asn_public.h enum CertType. &quot;</p><p>Go ahead... click it.&nbsp; It takes you here<br /><a href="https://www.wolfssl.com/doxygen/asn__public_8h.html">https://www.wolfssl.com/doxygen/asn__public_8h.html</a></p><p>There isn&#039;t any &quot;CertType&quot; defined anywhere on that page.<br />Try typing CertType into the search box...&nbsp; Nothing.</p><p>Now start aimlessly wandering through it&#039;s useless menu system hoping to stumble on what you are looking for.</p><p>Don&#039;t think this is just the first incident where I can&#039;t find something, and now left wandering aimlessly.&nbsp; Nor the second time.&nbsp; Nor the tenth time...&nbsp; It gets old really fast.</p><p>Broken documentation.&nbsp; Created by an inferior system.</p>]]></description>
			<author><![CDATA[null@example.com (Scotty2541)]]></author>
			<pubDate>Fri, 04 Jun 2021 12:04:17 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6072.html#p6072</guid>
		</item>
	</channel>
</rss>
