<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[wolfSSL - Embedded SSL Library — How to use socket-type BIOs?]]></title>
	<link rel="self" href="https://www.wolfssl.com/forums/feed-atom-topic1441.xml" />
	<updated>2019-09-19T13:53:37Z</updated>
	<generator>PunBB</generator>
	<id>https://www.wolfssl.com/forums/topic1441-how-to-use-sockettype-bios.html</id>
		<entry>
			<title type="html"><![CDATA[Re: How to use socket-type BIOs?]]></title>
			<link rel="alternate" href="https://www.wolfssl.com/forums/post4875.html#p4875" />
			<content type="html"><![CDATA[<p>Hi ENOTTY,</p><p>We put up an example for using the BIO compatibility layer with SSL here:<br /><a href="https://github.com/wolfSSL/wolfssl-examples/pull/171">https://github.com/wolfSSL/wolfssl-examples/pull/171</a></p><p>Thanks,<br />David Garske, wolfSSL</p>]]></content>
			<author>
				<name><![CDATA[dgarske]]></name>
				<uri>https://www.wolfssl.com/forums/user1863.html</uri>
			</author>
			<updated>2019-09-19T13:53:37Z</updated>
			<id>https://www.wolfssl.com/forums/post4875.html#p4875</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: How to use socket-type BIOs?]]></title>
			<link rel="alternate" href="https://www.wolfssl.com/forums/post4869.html#p4869" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>dgarske wrote:</cite><blockquote><p>The BIO_write expects WOLFSSL_BIO_SSL for an SSL socket write. Have you tried setting up a BIO with that type?</p></blockquote></div><p>Hi David,</p><p>Thanks for replying.&nbsp; Are there examples somewhere of creating a BIO of the SSL type and using it?&nbsp; OpenSSL&#039;s man pages have an example using BIO_new_ssl_connect but that is not one of WolfSSL&#039;s supported APIs.</p>]]></content>
			<author>
				<name><![CDATA[ENOTTY]]></name>
				<uri>https://www.wolfssl.com/forums/user3320.html</uri>
			</author>
			<updated>2019-09-19T00:09:35Z</updated>
			<id>https://www.wolfssl.com/forums/post4869.html#p4869</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: How to use socket-type BIOs?]]></title>
			<link rel="alternate" href="https://www.wolfssl.com/forums/post4867.html#p4867" />
			<content type="html"><![CDATA[<p>Hi ENOTTY,</p><p>The BIO_write expects WOLFSSL_BIO_SSL for an SSL socket write. Have you tried setting up a BIO with that type?</p><p>We have some BIO enhancements in the queue. See this pull request: <a href="https://github.com/wolfSSL/wolfssl/pull/2462">https://github.com/wolfSSL/wolfssl/pull/2462</a></p><p>Thanks,<br />David Garske, wolfSSL</p>]]></content>
			<author>
				<name><![CDATA[dgarske]]></name>
				<uri>https://www.wolfssl.com/forums/user1863.html</uri>
			</author>
			<updated>2019-09-18T16:54:15Z</updated>
			<id>https://www.wolfssl.com/forums/post4867.html#p4867</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[How to use socket-type BIOs?]]></title>
			<link rel="alternate" href="https://www.wolfssl.com/forums/post4864.html#p4864" />
			<content type="html"><![CDATA[<p>Hi all,</p><p>I&#039;m using a library designed for OpenSSL.&nbsp; The library&#039;s API takes BIO pointers.&nbsp; It later calls BIO_read() and BIO_write() on that BIO pointer.</p><p>If I use the WolfSSL API normally, the WOLFSSL structure doesn&#039;t fill in the biord and biowr fields, so SSL_get_rbio/SSL_get_wbio won&#039;t provide me a BIO to pass to the third party library.</p><p>I can successfully create a socket BIO using BIO_new_socket with an opened/connected socket file descriptor, pass it to SSL_set_bio, then SSL_connect().&nbsp; Everything succeeds.</p><p>SSL_write() of a char * buffer also succeeds.&nbsp; But if I replace that with a BIO_write(), no data is sent.<br />BIO_write doesn&#039;t handle BIOs of type WOLFSSL_BIO_SOCKET, so it doesn&#039;t actually work on my BIO.</p><p>Thanks</p>]]></content>
			<author>
				<name><![CDATA[ENOTTY]]></name>
				<uri>https://www.wolfssl.com/forums/user3320.html</uri>
			</author>
			<updated>2019-09-17T17:25:10Z</updated>
			<id>https://www.wolfssl.com/forums/post4864.html#p4864</id>
		</entry>
</feed>
