<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Openssl Installation In Yocto Image and Configuration in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662961#M101807</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can doublecheck if it the issue is connected to network connectivity not to wget itself with the command like "telnet google.com 443":&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$ telnet google.com 443&lt;BR /&gt;Trying 74.125.232.227...&lt;BR /&gt;Connected to google.com.&lt;BR /&gt;Escape character is '^]'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are getting something like "Unable to connect to remote host: Connection refused" instead of "Connected"&lt;BR /&gt;it means that port 443 is closed on some point between telnet and google.com.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Also for diagnostic please try "curl &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fgoogle.com" rel="nofollow" target="_blank"&gt;https://google.com&lt;/A&gt;&lt;SPAN&gt;" instead of wget. You can get some more output.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day, &lt;BR /&gt;Victor &lt;BR /&gt; &lt;BR /&gt;----------------------------------------------------------------------------------------------------------------------- &lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you! &lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Feb 2017 06:26:29 GMT</pubDate>
    <dc:creator>b36401</dc:creator>
    <dc:date>2017-02-06T06:26:29Z</dc:date>
    <item>
      <title>Openssl Installation In Yocto Image and Configuration</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662958#M101804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to connect with websites using &lt;STRONG&gt;"Secure HTTP"&lt;/STRONG&gt; protocol for that I have installed openssl_1.0.2h in Yocto Image but I am unable to connect with google.com ( Note: I have tried to connect with different sites but here I am taking example of "google.com" ) using secure HTTP protocol (i.e. When I am trying to Run the following command "wget &lt;A href="https://google.com"&gt;https://google.com&lt;/A&gt;", then I am getting Network is unreachable error.). Here is the log for command run:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;root@imx6qsabresd:~# wget &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fgoogle.com" rel="nofollow" target="_blank"&gt;https://google.com&lt;/A&gt;&lt;BR /&gt;Connecting to google.com (216.58.196.110:443)&lt;BR /&gt;wget: error getting response: Network is unreachable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am able to ping the google.com (i.e. Internet is available on board). Here is the log of ping command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;root@imx6qsabresd:~# ping google.com&lt;BR /&gt;PING google.com (216.58.196.110): 56 data bytes&lt;BR /&gt;64 bytes from 216.58.196.110: seq=0 ttl=56 time=8.656 ms&lt;BR /&gt;64 bytes from 216.58.196.110: seq=1 ttl=56 time=8.578 ms&lt;BR /&gt;64 bytes from 216.58.196.110: seq=2 ttl=56 time=8.704 ms&lt;BR /&gt;^C&lt;BR /&gt;--- google.com ping statistics ---&lt;BR /&gt;3 packets transmitted, 3 packets received, 0% packet loss&lt;BR /&gt;round-trip min/avg/max = 8.578/8.646/8.704 ms&lt;BR /&gt;&lt;A href="mailto:root@imx6qsabresd:~"&gt;root@imx6qsabresd:~#&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And also I am able to connect with the google.com using insecure HTTP protocol (i.e. "wget &lt;A href="http://google.com"&gt;http://google.com&lt;/A&gt;"&amp;nbsp;is downloading its index.html ). Here is the log for the command run:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;root@imx6qsabresd:~# wget &lt;A href="http://google.com"&gt;http://google.com&lt;/A&gt;&lt;BR /&gt;Connecting to google.com (216.58.196.110:80)&lt;BR /&gt;Connecting to &lt;A href="https://community.nxp.com/www.google.co.in" target="test_blank"&gt;www.google.co.in&lt;/A&gt; (216.58.200.3:80)&lt;BR /&gt;index.html 100% |***********************************************************************************************************************| 12452 0:00:00 ETA&lt;BR /&gt;root@imx6qsabresd:~#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So why it is not connecting with URL's (i.e. webites) using "https" &amp;nbsp;protocol, is there any openssl configuration is required or any other dependencies package need to be installed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Feb 2017 11:50:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662958#M101804</guid>
      <dc:creator>devendrasinghba</dc:creator>
      <dc:date>2017-02-02T11:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Openssl Installation In Yocto Image and Configuration</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662959#M101805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It seems port 433 (https) is disabled somewhere with network configuration (possibly on the router). &lt;BR /&gt;You need to check it. &lt;BR /&gt; &lt;BR /&gt;Please note that wget supports proxy. So you can simply set https_proxy option if you have some local proxy server in your network. &lt;BR /&gt; &lt;BR /&gt;By the way let me remind one more usefull option regarding to https: --no-check-certificate.&lt;BR /&gt;This option avoids certificate verification.&lt;BR /&gt;It is not related to current connectivity issue however there is a chance that when you fix network configuration you met certificate issue next.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Victor&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Feb 2017 08:45:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662959#M101805</guid>
      <dc:creator>b36401</dc:creator>
      <dc:date>2017-02-03T08:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Openssl Installation In Yocto Image and Configuration</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662960#M101806</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have checked about port 443, it is not disabled in Router by running the same command on the Ubuntu Machine, it is running without any problem. So I don't think there is a problem with router configuration. There is some other problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Feb 2017 12:28:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662960#M101806</guid>
      <dc:creator>devendrasinghba</dc:creator>
      <dc:date>2017-02-03T12:28:50Z</dc:date>
    </item>
    <item>
      <title>Re: Openssl Installation In Yocto Image and Configuration</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662961#M101807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can doublecheck if it the issue is connected to network connectivity not to wget itself with the command like "telnet google.com 443":&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$ telnet google.com 443&lt;BR /&gt;Trying 74.125.232.227...&lt;BR /&gt;Connected to google.com.&lt;BR /&gt;Escape character is '^]'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are getting something like "Unable to connect to remote host: Connection refused" instead of "Connected"&lt;BR /&gt;it means that port 443 is closed on some point between telnet and google.com.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Also for diagnostic please try "curl &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fgoogle.com" rel="nofollow" target="_blank"&gt;https://google.com&lt;/A&gt;&lt;SPAN&gt;" instead of wget. You can get some more output.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day, &lt;BR /&gt;Victor &lt;BR /&gt; &lt;BR /&gt;----------------------------------------------------------------------------------------------------------------------- &lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you! &lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Feb 2017 06:26:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Openssl-Installation-In-Yocto-Image-and-Configuration/m-p/662961#M101807</guid>
      <dc:creator>b36401</dc:creator>
      <dc:date>2017-02-06T06:26:29Z</dc:date>
    </item>
  </channel>
</rss>

