Hi,
How to encrypt model developed in QSPICE for public release? (Including Verilog and Analog blocks)
Regards,
Heisenberg
Hi,
How to encrypt model developed in QSPICE for public release? (Including Verilog and Analog blocks)
Regards,
Heisenberg
Hi, Heisenberg.
I assume that “Verilog and Analog blocks” means compiled code. For those, simply don’t share the source code, share only the DLL.
This doesn’t prevent someone from reverse-engineering/decompiling the DLL, of course. But there’s no way to prevent that since encrypting the DLL in any way would prevent Windows from loading it.
–robert
Hi,
I understand we can do C++ and Verilog models as dlls. What about analog blocks? Can we encrypt the same after netlist is generated?
Regards,
Heisenberg
Yes, you can encrypt analog blocks. The QSPICE help file outlines the relevant commands if you search for “encrypt”. You mark the parts of the netlist you wish to encrypt with .prot and .unprot, and then invoke QUX.exe with the -ProtectSelections or -ProtectSubcircuits option. Be sure to save a separate copy of the file you’re encrypting before running this command, as it will overwrite the source.
Gee, Jeff, sort of sad to hear that. I do hope that folk decide to share freely…
–robert
Robert,
You are a poster child for open sharing of interesting circuits. Contributors like you benefit the community.
Encryption has its place. For example, a vendor can share simulation results with a potential customer during a project proposal, but not reveal confidential details that could aid competitors.
You’re right, of course, Jeff. Further, if I need a good model of a specific device, I’d rather have an encrypted model than no model or a poor one.
I hope I didn’t step on any toes. Call me a dreamer.
–robert
Robert- Yes, that’s the tradeoff. The encryption tools are there if someone wants to use them. I do hope you keep your work open for everyone to appreciate.
No worries – I’m not clever enough to have anything worth protecting…
Thanks Jeff,
Regards,
Heisenberg