The 3D printing community is experiencing significant turbulence following Bambu Lab's announcement of firmware update 1.08.03.00, which introduces a new authorization control system that effectively restricts third-party software access to their printers.
Security Update or Control Mechanism?
The update, marketed as a security enhancement, requires users to route their print jobs through Bambu's proprietary Bambu Connect software, even when operating in LAN mode. This has raised serious concerns about privacy and device autonomy among users. Community members have noted that the requirement for cloud connectivity and the introduction of additional proprietary software layers could pose security risks rather than enhance protection.
It seems to require the cloud to print remotely. I don't want to have to use an SD card or whatever nonsense each time I need to start a print, nor use the tiny slow touch screen to do what I need.
Technical Implications and Community Response
The firmware update implements certificate-based encryption for printer communications, likely using x509 certificates. While Bambu Lab positions this as a security measure, technical analysis from the community suggests these certificates could be reverse-engineered, potentially leading to a cat-and-mouse game between the manufacturer and third-party developers.
Open Source Impact
The change has particularly affected users of OrcaSlicer and other open-source solutions, who now face limited functionality unless they adopt Bambu's official software. This move has been interpreted by some as a step backward for open-source 3D printing, with users expressing concern about the precedent it sets for hardware control and ecosystem lock-in.
Key Impact Points:
- Affects: X, P, and A series Bambu printers
- Required Software: Bambu Connect client
- Affected Functions:
- Print job initiation (Cloud and LAN)
- Calibrations
- AMS settings
- Network plugin functionality
Privacy and Data Collection Concerns
Some community members have raised alarming concerns about potential data collection and privacy implications. There are suggestions that the new interface code, running on host computers, could be more challenging to firewall effectively compared to the previous device-level controls, potentially enabling unwanted data transmission.
The situation continues to evolve, with the community actively seeking alternative solutions, including the possibility of open-source firmware development, especially after reports of private keys being leaked. For now, many users are choosing to delay the firmware update while waiting for clearer solutions or community-driven alternatives to emerge.
Reference: FW 1.08.03.00 from Bambu WILL BREAK ORCASLICER for X, P and A series #8063