Notices by Kitsune Yasu (kitsune_yasu@waldbewohner.eu)

@fribbledom@mastodon.social

Argumentum ad hominem? Really?

Do you really have nothing meaningful to add to our discussion? Do you really need to attack the other side, instead of providing real evidence?

@fribbledom@mastodon.social

Additionally, BambuLab is very open to 3rd-Party Contributions: https://blog.bambulab.com/custom-firmware-plan-and-our-principles-on-ecosystem/

While most companies just say that they will not support hardware with Custom Firmware, BambuLab ensures that they will make a best-effort attempt to support printers with custom firmware that have had genuine hardware failures as a result of manufacturing defects

@fribbledom@mastodon.social try to catch up on the news first, so we can have a more informed discussionI'd like to have qualified sources and not some randoms in forums talking/speculating about things.

As far as I can see, BambuLab has already published ways for 3rd-Party Tools to still be able to work with their 3D-Printers.
And yes, I agree that it is not very comfortable if you need an additional tool to be able to send things to your printer.

But at the same time, you argue, that BambuLab is not interested in helping 3rd-Parties, which is wrong.
If they would like to restrict 3rd-Parties, they would not have developed the Connector, cause it is already integrated into their Network-Plugin for the Bambu Studio Slicer.

Additionally, there are some FAQs (which they updated 2 days ago) with the following statements:Our team is actively working on submitting the integration code for Bambu Connect. Once submitted, it will be up to Orca to decide when and if to incorporate it into the slicer, enhancing the user experience. We anticipate the code will be available on GitHub within the next few days, ready for integration into the Orca codebase.It’s important to note that this update is not intended to restrict third-party software use. In fact, we’ve actively collaborated with third-party print farm management software providers in the past and continue to support such partnerships. To further improve the user experience, we are introducing a new software solution that will address these limitations and enhance overall print farm management capabilities.In these cases, we cannot guarantee long-term support for unofficial accessories unless they have been approved by us in advance. Once we became aware of the Panda accessories, we communicated these updates to their creators.
That said, we welcome official collaborations with companies interested in developing accessories for Bambu Lab printers, as we have successfully partnered with other companies in the past, including E3D and Slice Engineering.https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/

@fribbledom@mastodon.social They patch the issue and don't need to leak it anymore.

@fribbledom@mastodon.social Bambu Lab will release technical documentation, new software, and offer support to assist partners in adapting their systems and developing software solutions compatible with the new X Series firmware and authorization controls.https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/

Yep, sounds that they are not interested in working with maintainers of other slicers /s

@fribbledom@mastodon.social I didn't claim otherwise :neofox_wink:

And you can revoke access for exposed keys in your API, so nothing is broken.

@fribbledom@mastodon.social Yes, but read the article.

THIS IS A BETA

The app is only there, so maintainers of slicers don't need to implement an Auth-System, as long as it is in an experimental phase.

@fribbledom@mastodon.social

Just to make sure nobody overreacts to this:It seems like many ppl are misinterpreting the implications

These keys can only be used to replicate what bambu connect is doing (talking to official API servers in a very limited manner) without relying on closed source binaries.

The overall device security isn't "broken" because of this and it won't allow third party slicers to use e.g. camera live view eitherhttps://www.reddit.com/r/BambuLab/comments/1i4k9m2/comment/m7zxwlb/

@fribbledom@mastodon.social This would still require you to have an additional piece of software that allows the authentication on top of the default protocol.

I agree that there should be an open solution for others in the long run.

@fribbledom@mastodon.social well, that's unfortunate if this is really genuine

But I still appreciate the effort Bambu made ti develop this software to allow other slicers to still communicate with the printer.
If they really wanted to cut off the access, they didn't need to write this connector.

@fribbledom@mastodon.social offer a solution that literally ships their private key to everyone's desktop. It's been leaked by now. Where is the source for that claim? I've neither heard nor I can find anything related to a leaked private key.

And if you talk about possibilities, you don't need to ship the private key, you can use certificates for that.

@fribbledom@mastodon.social Want to use another slicer to send your job to the printer? Sorry, no.I'd argue that this part is quite misleading.let's not pretend this has anything to do with securityWell, if you want to make sure, that only authorized people can use the printer, than you need to add an authentication layer into the current protocol.
This system also prevents people, that can access your WLAN, to manipulate your printer as long as they don't have authorization to use it.

@fribbledom@mastodon.social that's not true, you still can use other Slicers as described in the linked article, you just need an additional piece of software to sign your requests, to make sure that the printer cannot be used from unauthorized users