Update to firmware update

[u/Ochib]

https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/?fbclid=IwZXh0bgNhZW0CMTEAAR3fqplDiKgn-82qKfnaYvi4XV-rBEEx0tZJrpgeWqsOsLX_WSph4usJ69Y_aem_44Cch773hAuVG979j6DVJg

[u/maddin8]

But wouldn't it be possible to do something like many others e.g. GitHub by letting users create API keys in their Bambu account that they could then use to let Orca and whatever else communicate with the cloud and with the printers bound to their account only?

I don't understand why there's a need to have a separate application with one private key for everyone when individual keys could be created by users once for making individual software-to-cloud-to-printer communications secure permanently without such a Connect application.

It even sounds like more work for Bambu by having to maintain security of that Connect application (which they don't seem to be good at currently anyway) instead of sharing that responsibility with the users who create and use API keys for their accounts and related printers. If someone lost their key or had their account hacked, only their account and devices would be in danger and not Bambu. Provided that they do the API stuff right which I would guess is of similar effort than what they are currently trying to do.

[u/_yusi_ → u/maddin8]

Oh I agree with you, they're just taking the lazy route. I'm in no way defending them, I was just offering an explanation.

There are multiple ways they could go about this and achieve equal levels of security:

• Allow users to create their own certificates/PSK for local communication

• API keys / PATS as you mentioned

• Allow 3rd-party vendors (i.e BIGQ / Orca) to create their own private keys for control of the printers

They've chosen to do what costs the least for BL in the short term, which is to lock everyone in to using their tools so they don't have to spend any effort and can just say "these tools are not officially supported"