Timeline for 3D Printing with malicious intent
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2022 at 22:17 | comment | added | Trish | The question actually poses a good thought start for "how to mitigate risks and design a threat model to protect your print farm" - though framed as 'can one make this to damage the printer?' | |
| Jan 11, 2022 at 20:15 | history | became hot network question | |||
| Jan 11, 2022 at 20:11 | answer | added | Trish | timeline score: 3 | |
| Jan 11, 2022 at 20:00 | history | edited | Trish | CC BY-SA 4.0 |
edited tags - The exploits work on any Marlin machine - the ender is not more or less vulnerable than a prusa or any other FDM
|
| Jan 11, 2022 at 14:59 | answer | added | 0scar♦ | timeline score: 2 | |
| Jan 11, 2022 at 12:36 | comment | added | Greenonline♦ | Just my thoughts... I'm tempted to upvote this question, purely for its audacity, as well as its usefulness in making people aware that you could totally shaft a printer if care is not taken with the (G-)code used. Also, it has resulted in a very useful answer (and hopefully others to come). The other negative votes, if given due to a distaste for the topic, I think may be a little unfair - if this were on Meta then yes distaste may be demonstrated by down voting, but on the main site downvotes should be for lack of research, etc. and it seems like the OP has at least done a bit of research. | |
| Jan 11, 2022 at 11:14 | answer | added | OneWasNotEnough | timeline score: 10 | |
| Jan 11, 2022 at 9:54 | history | edited | 0scar♦ | CC BY-SA 4.0 |
No greetings
|
| Jan 11, 2022 at 9:30 | comment | added | OneWasNotEnough | @ChinchillaWafers the information on how to do it is already public as every Gcode and their functions are available from the Firmware vendor's website: marlinfw.org/meta/gcode The threat vector is from unsecured web interfaces primarily. But physical access to the printer will not prevent blatant misuse and abuse. If a hacker has physical access to your printer - you have bigger problems than someone trying to run malicious gcode. Additionally, schools might like to know "how" a student can destroy a printer and what to look for. (Hard rule of no outside Gcode fixes this threat.) | |
| Jan 11, 2022 at 6:07 | comment | added | user10489 | I think it is important to be aware that a gcode can set your temperature to something that can damage the printer. But by the same token, I don't think you should be printing gcode from someone else that hasn't run through your own slicer with your own fine tuning for your printer. | |
| Jan 11, 2022 at 0:38 | comment | added | ChinchillaWafers | I don’t think we should be using 3D Printing Stack Exchange to develop a public blueprint for hackers to destroy people’s 3D printers | |
| Jan 11, 2022 at 0:33 | comment | added | user10489 | Have you done basic research, like examining the list of gcodes recognized by the ender3? | |
| Jan 10, 2022 at 22:43 | history | edited | agarza | CC BY-SA 4.0 |
fixed capitalization, punctuation, grammar, formatting
|
| S Jan 10, 2022 at 22:01 | review | First questions | |||
| Jan 10, 2022 at 22:43 | |||||
| S Jan 10, 2022 at 22:01 | history | asked | newatthis | CC BY-SA 4.0 |