Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
I understand Quartus can handle encrypted core input files (RTL IP's).
To ensure these core details remain 'secret' the output files (see attached picture, red circles) also should be encrypted in my view; is this the case?
Otherwise reverse engineering of the outputs can result in enclosing the encrypted IP's.
Thanks,
TvD
Link Copied
Hi @TvD
With some effort, the original content can be reverse engineered.
You can encrypt your files with the IEEE 1735 Encryption Standard before sharing the design with end customers, in order to protect the IP contents.
You may checkout the webpage here for further details.
Best Regards,
Richard Tan
p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.
You may also checkout the below KDB to keep your design files private for any security reasons.
Best Regards,
Richard Tan
p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.
Hi @TvD ,
I have yet to receive any response from you to the previous question/reply/answer that I have provided but I believed that I have answered your question.
With that, I will now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.
Best Regards,
Richard Tan
p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.
Community support is provided Monday to Friday. Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.