Welcome to Oitswilliam Pang's Blogs!
After years of wait for not using the wiki for the non-wiki related blogs to this platform, it's finally here.
After years of wait for not using the wiki for the non-wiki related blogs to this platform, it's finally here.
The true end of the legacy projects (but not Sheer).
Today is a talk about not just recent, but what I think is the biggest controversy that's bigger than A1 wire burning; its security enhancements, called Authorization Control System. Bambu claims that this will reduce remote attacks and exposures, and my thought, is in case if someone is stupid enough to open it via port forwarding. But people think it's a step ahead of squeezing the open ecosystem.
The Authorization Control System is a feature that lets printer require keys before being controlled, It can only be from first-party slicer app and companion apps (unless otherwise if they change decisions). This feature does not limit statistical interactions or starting a print job that's already on the card, among other things, but it limits control-related interactions and other critical operations. Users who do not want this feature can keep their firmware, but not if they received the printer with this firmware from start, cause this does not let them downgrade the firmware.
This has been fallen down to three sections, closing down the ecosystem, easy reverse engineering and dated terms.
This move has been known that it will affect community-maintained slicers, Home Assistant automations and dedicated controller devices (i.e. BTT Panda Touch). To address this, Bambu has unveiled a dedicated companion app called Bambu Connect that allows sending print jobs outside Bambu's own "unmodified-by-community" slicer and it's mobile companion app, and control the printer like on own slicer. I think not everyone likes this, as it adds three additional steps, and jogging the printhead will become cumbersome.
People have said that this is a step ahead of becoming the HP (inkjet) printers in 3D (or of 3D printing), where they will not do anything, including scanning if one ink was empty, or beg for subscription. Or even worse, they will no longer support generic or third-party filaments, I myself included, which Bambu said they don't have intent on this or never; the other was over two years ago. At least my Canon paper printer does anything, even print, and even if the ink is empty. I can also use non-Canon cartridges to print on papers, even though losing exclusive features that can only be accessed on the Internet, but I have never tried it.
Since Bambu Connect used Electron as it's base, and not using in-house encryption, people have figured out how to crack down the keys used by Bambu Connect, within a day of it's beta release. And has been shared to the wiki that's against companies abusing their customers. The key might be rotated later.
Louis flamed the responsibility of baseless allegations back to Bambu when he got gaslit by Bambu's tactics of trying to remove archives captured by third-parties and the list of things that Bambu will not do when compared with the ToU.
I have pointed out that section 7.4 of the terms of use has explicitly said that users may no longer send new print jobs if new (stable, not beta) updates are found, but on the blog post regarding the controversy said (let's just say) this update is optional. This has confused a lot of people into thinking to update, per ToU, or not, for the sake of third-party integrations.
What I think is they missed the terms "Unless if explicitly specified," or "unless if the update is marked optional".
Currently, I doubt it, but they have addressed most problems including solving LAN mode requirements being too strict by introducing developer mode in LAN mode. This allows third-party integrations to control the printer, but have to sacrifice for local intruders who play tricks with your printers remotely, yep "local" because there is no proof on this mode allowing remote attacks from the Internet.
They are also ready to talk with accessory vendors on gaining such restricted features.
Maybe this feature was made for users who have zero knowledge of networking, but still I doubt if this feature actually work against brute-force attack or something like that.
If you have things to point out, please send message on my Facebook page, or email me yo [at] oitswilliam [dot] com.
Short update: add new links, clarify ownership and add suggestion information Short update 2: forgot to add introduction and forgot about the actual name yeesh Update on January 22: specified new reason on why Louis got gaslit
Moved from William Pang Central
This post was originated from my first "blog" site (via Wix cuz I want WYSIWYG) that decided to go abandoned just after this. The exact date was forgotten until I find it archive yay I knew how to archive pages at bare minimum!
This is the history of the Bunny 350 logos.
Before the name is changing or creating the first logo, William Pang was drawn the players that named "Bunny350" and "Jumping250".