Research

Deliberate mistakes could be the key to protecting 3D printed parts from theft

CAD model of a 3D printable cube with embedded flaw (sphere). Image credit Nikhil Gupta, Ph.D.
Comments (6)
  1. =/ now how does one export an stl that is printable on multiple machines with any slicer. this “encryption” method has NO cross platform capability.

    1. That’s stupid. Now designers can’t protect their stl files we might as well not even make the stl available in the first place. The only person who will be able to steal it is the printing bureau and they already have the stl file and working slicer.

    2. Mars Suica says:

      For instance a user can tell you their machine, slicer and material. You then synthesize an STL and a set of slicing parameters.

      The print will fail if a third party attempts to naively print the STL using different build parameters, machine, or material. To print the object successfully, the third party will have to intercept the part’s metadata – the slicing parameters and machine/material target.

      This is security by obscurity, however. If the third party creates an algorithm that automatically reverse engineers the part, then there is no benefit. And I somewhat down that the difficulty of building such an algorithm is guaranteed mathematically, as in other cryptographic security protocols.

    3. This is not helpful. What happens when I want to code once and deploy many places. I do this with my software. I cannot do this with my models that I print on either a makerbot, EOS metal printers, or other FormLABs SLA machines as each vendor uses a different slicer and new slicers are always being made and improved upon. I export one 1 highest resolution STL. I’m not going to waste additional cpu time on extra versions of my model for every printer. That should be the slicer’s responsibility software & ecosystem – wise — to parse an stl to g-code print instructions given a printer it connects to/supports. Furthermore, the future of engineering high quality models is in parametric nurbs modelling — something like solidworks that runs a nurbs kernel like rhino, saving your surfaces and curves as actual math and not polygonal approximations. You can reverse engineer any open source slicer which will be the most popular solution for hackers as most slicers are open source and non-proprietary.

  2. Viktor Jondal James Mcarthur maybe we should reach out to them

  3. Sell your prints, not your files.

Leave a Reply