"Security" on behalf of the user is a complete red herring. You can't print to my 2d printer or my 3d printer, but I can, with "any old device or application". Because they're on my network, not public on the internet.

I disagree. These devices can easily burn down people's homes if given bad G-code. Then they would be sued into the dirt for a security whole a mile wide. Looking at the changes this is about liability.

How is an electron app that just adds another step solving the problem? They should have just secured their api properly instead of using security as an excuse to cut out third party software that will get around an inevitable subscription.

Because authenticated commands removes the liability issue. Hacking the device vs we knowingly let anything send g-code.

This is basically the equivalent to having passwords on a MySQL database or redis server.

Why on earth would they add a subscription? That makes absolutely no sense business wise. No one would buy their printers, and they don't have a captured market to strong arm anyone.

Why would they add a subscription? Uhm print farms already have subscription based software. Bambu would just be an easier entry. They already have screenshots of it on their wiki.

If it can burn down your house with the wrong G-code, adding a cloud service is not the way to fix that.

There shouldn’t be a single printer on the market that doesn’t come with basic emergency cutoff features.

And a firmware hack could burn down my house with my laser printer. Yet that's not possible, because neither printer talks outside my network, at all.

You mean like when Bambu issues a firmware update remotely and many printers which were sitting idle just start printing without being commanded by the user? [1]

I personally do not want my printer connected to any vendor's server in any way...IMHO, there is no reason for it.

[1] https://www.reddit.com/r/3Dprinting/comments/15sfisq/bambula...

> Bambu is patching a security issue.

This isn't a security fix. As a security protocol, it wouldn't pass any kind of security audit. A security fix would be something based on a per user credential, not on obscurity.

> Personally I don't want any device or application to send any old G-code to my printer.

Username/password over TLS would do that better than what Bambu Lab is proposing, as an extremely simplistic example.

And LAN-only mode should work without any external connections yet it looks like it'll require it for authentication. That defeats the whole idea of LAN-only!

> Username/password over TLS would do that better than what Bambu Lab is proposing

Already works that way and isn't affected by this update: https://wiki.bambulab.com/en/security-incidents-cloud-traffi..., https://github.com/Doridian/OpenBambuAPI/blob/main/mqtt.md#l...

> Bambu is patching a security issue. Personally I don't want any device or application to send any old G-code to my printer. Like say command the printer to basically destroy itself.

Why not implement some kind of open authentication? One that other slicers can implement.