The catch worth underlining on that Creality line: CWE-494 isn’t just a license footnote, it’s a live supply chain hole. Fetching an unsigned blob and running it from a server you don’t control means anyone who compromises or MITMs that endpoint can push code to every machine that pulls it. That’s a potential RCE path onto my shop floor, not just a missing source tarball. This is the part that should scare working pros, not just the FOSS crowd.
@3D_Musketeers@IntCyberDigest@GamersNexus Could you forward the info you have? and possibly docs the printer came with(manual. Safety notice etc.), we'd like to inspect the compliance of the device.
@1llegalEngineer@i2cjak Muahaha! I'll catalog and list some of this stuff. Eventually. Likely end of the year.
And yep one or two sizes down from the photonicinduction/styropyro ones.
So hold please.
@reprinted3D It all boils down to: are your parts acting as expected or are they typical cheap crap ? in such a case anything can happen. At least limit the psu. Cheap buck converters are also often an emc nightmare in case the thing is glitching you know where to look.
@reprinted3D If the device expects negotiation it may refuse function. With the cc lines via 5k1 you'd set it at 5V@whatever amps available.
Your supply should be at least current limited. In yoir config its up to the device to not kill itself/start a fire. Usb wants control from both ends.