<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[About the Necessity of Code Signing C++ Plugins]]></title><description><![CDATA[<p dir="auto">Dear Developers,</p>
<p dir="auto">In a changing security landscape Maxon Computer continues to deliver products which protect the systems of our users. In that spirit we announce a change to how we will treat code-signed binaries from third parties in future releases.</p>
<h4>Upcoming Changes to Loading Signed Binaries</h4>
<blockquote>
<p dir="auto"><img src="http://developers.maxon.net/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/26a0.png?v=0b8ddba251d" class="not-responsive emoji emoji-android emoji--warning" style="height:23px;width:auto;vertical-align:middle" title=":warning:" alt="⚠" /> The upcoming releases of Cinema 4D will not accept code signed C++ plugin binaries whose certificate has become invalid. A Cinema 4D installation which attempts to boot with a C++ plugin with such invalid certificate, will inform the user that the respective file is faulty, that the related plugin must be reinstalled, and then <strong>shut down</strong> Cinema 4D. The user will only be able to successfully boot Cinema 4D once he or she has removed your plugin.</p>
</blockquote>
<p dir="auto">It is therefore important that you deliver your C++ plugins in one of the two forms listed below:</p>
<ol>
<li>As signed binaries with a valid certificate,</li>
<li>or as unsigned binaries.</li>
</ol>
<p dir="auto">Plugins for Windows which have been singend with a certificate which at the time of validation has expired are still valid when they are time-stamped and have either no expiration date on the time-stamp or have not yet reached the expiration-date of the time-stamp. In general, you should avoid shipping Windows plugins with an expired certificate.</p>
<h4>About the Necessity of Code Signing</h4>
<p dir="auto"><a href="https://en.wikipedia.org/wiki/Code_signing" target="_blank" rel="noopener noreferrer nofollow ugc">Code signing</a> is the mechanism with which operating systems ensure that a to be executed binary has not been altered since it has been shipped by a vendor. Code signing is therefore not only in the interest of users who want to avoid executing modified binaries but also in the interest of application vendors to signal their trustworthiness.</p>
<p dir="auto">We recommend that all C++ plugins are code signed in the manner lined out in the code signing guides provided by <a href="https://developer.apple.com/support/code-signing/" target="_blank" rel="noopener noreferrer nofollow ugc">Apple</a> and <a href="https://learn.microsoft.com/en-us/windows/win32/seccrypto/cryptography-tools" target="_blank" rel="noopener noreferrer nofollow ugc">Microsoft</a>; we advise against shipping plugins signed with self-provided certificates intended for development only. Our Cinema 4D C++ SDK documentation also contains a section about <a href="https://developers.maxon.net/docs/cpp/2024_3_0/page_maxonapi_dev_macos.html#page_maxonapi_dev_macos_notarization" target="_blank" rel="noopener noreferrer nofollow ugc">code signing on macOS</a>. We plan to add a similar section for Windows in an upcoming release.</p>
<blockquote>
<p dir="auto"><img src="http://developers.maxon.net/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/2139.png?v=0b8ddba251d" class="not-responsive emoji emoji-android emoji--information_source" style="height:23px;width:auto;vertical-align:middle" title=":information_source:" alt="ℹ" /> Code signing is a practice that should be followed for C++ plugin binaries for both on macOS and Windows. For Python plugins singing is technically not necessary but could be viewed as good practice.</p>
</blockquote>
<p dir="auto">If there any open questions, please do not hesitate to ask them in the comments below or reach out to us directly via our <a href="/forum/contact/">contact form</a>.</p>
<p dir="auto">Happy coding,<br />
the Maxon SDK Team</p>
]]></description><link>http://developers.maxon.net/forum//topic/15433/about-the-necessity-of-code-signing-c-plugins</link><generator>RSS for Node</generator><lastBuildDate>Sat, 14 Mar 2026 09:47:19 GMT</lastBuildDate><atom:link href="http://developers.maxon.net/forum//topic/15433.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 18 Mar 2024 13:27:07 GMT</pubDate><ttl>60</ttl></channel></rss>