<?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>Secure Authentication中的主题 statically linking OpenSSL engine for SE050</title>
    <link>https://community.nxp.com/t5/Secure-Authentication/statically-linking-OpenSSL-engine-for-SE050/m-p/1367411#M611</link>
    <description>&lt;P&gt;For an embedded system we need a statically linked engine for OpenSSL. For this we set "OPENSSL_NO_DYNAMIC_ENGINE", but the source file "ax_sssEngine_main.c" contains the following lines which disables this possibility for OpenSSL versions starting with 1.1 (which we are using):&lt;/P&gt;&lt;P&gt;#if (OPENSSL_VERSION_NUMBER &amp;lt; 0x10100000L)&lt;BR /&gt;#else&lt;BR /&gt;#ifdef OPENSSL_NO_DYNAMIC_ENGINE&lt;BR /&gt;#undef OPENSSL_NO_DYNAMIC_ENGINE&lt;BR /&gt;#endif&lt;BR /&gt;#endif&lt;/P&gt;&lt;P&gt;We're currently using Middleware 3.0.6 but this code sequence is the same even in V3.3.&lt;/P&gt;&lt;P&gt;We dont' know how to load the engine as the function "&lt;SPAN&gt;EngineEmbSe_Load" is no longer defined after "#undef OPENSSL_NO_DYNAMIC_ENGINE". As I assume there is a reason for the above mentioned code so I fear that simply removing the "#unset..." will not be a solution.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;How can we get a statically linked engine for OpenSSL 1.1?&lt;/P&gt;</description>
    <pubDate>Fri, 05 Nov 2021 15:45:53 GMT</pubDate>
    <dc:creator>fus</dc:creator>
    <dc:date>2021-11-05T15:45:53Z</dc:date>
    <item>
      <title>statically linking OpenSSL engine for SE050</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/statically-linking-OpenSSL-engine-for-SE050/m-p/1367411#M611</link>
      <description>&lt;P&gt;For an embedded system we need a statically linked engine for OpenSSL. For this we set "OPENSSL_NO_DYNAMIC_ENGINE", but the source file "ax_sssEngine_main.c" contains the following lines which disables this possibility for OpenSSL versions starting with 1.1 (which we are using):&lt;/P&gt;&lt;P&gt;#if (OPENSSL_VERSION_NUMBER &amp;lt; 0x10100000L)&lt;BR /&gt;#else&lt;BR /&gt;#ifdef OPENSSL_NO_DYNAMIC_ENGINE&lt;BR /&gt;#undef OPENSSL_NO_DYNAMIC_ENGINE&lt;BR /&gt;#endif&lt;BR /&gt;#endif&lt;/P&gt;&lt;P&gt;We're currently using Middleware 3.0.6 but this code sequence is the same even in V3.3.&lt;/P&gt;&lt;P&gt;We dont' know how to load the engine as the function "&lt;SPAN&gt;EngineEmbSe_Load" is no longer defined after "#undef OPENSSL_NO_DYNAMIC_ENGINE". As I assume there is a reason for the above mentioned code so I fear that simply removing the "#unset..." will not be a solution.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;How can we get a statically linked engine for OpenSSL 1.1?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2021 15:45:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/statically-linking-OpenSSL-engine-for-SE050/m-p/1367411#M611</guid>
      <dc:creator>fus</dc:creator>
      <dc:date>2021-11-05T15:45:53Z</dc:date>
    </item>
  </channel>
</rss>

