Bambu Lab Authorization Control System: Difference between revisions

Line 73:

=== Permanent Nature of the Update ===

Once a printer is updated to the new firmware, users cannot revert to previous versions that allow fuller third-party integration

Once a printer is updated to the new firmware, users cannot revert to previous versions that allow fuller third-party integration{{Citation needed}}. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.

. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.

The manufacturer states this change is required for security, but community members note that many of the security vulnerabilities being addressed stem from Bambu's own cloud-centric design choices rather than inherent risks of local network control<ref>https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/12</ref>. The update forces users into Bambu's ecosystem of applications & cloud services, regardless of their preferences or needs for local network automation.

This has been characterised as a significant post-purchase reduction in functionality for existing owners who bought their printers with the understanding they could use third-party software & home automation tools

This has been characterised as a significant post-purchase reduction in functionality for existing owners who bought their printers with the understanding they could use third-party software & home automation tools{{Citation needed}}. The inability to revert these changes, combined with the mandatory nature of the update for new printers, demonstrates how manufacturers can use software updates to unilaterally modify the capabilities of hardware products after purchase<ref>https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/9</ref>.

. The inability to revert these changes, combined with the mandatory nature of the update for new printers, demonstrates how manufacturers can use software updates to unilaterally modify the capabilities of hardware products after purchase<ref>https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/9</ref>.

For users that would want to use a third-party slicer, Bambu would require those users to download and install Bambu Connect in order to send gcode wirelessly over LAN or over the cloud. While Bambu claims that they were in contact with SoftFever, the developer of OrcaSlicer, as of writing, SoftFever still does not have any keys for Bambu Connect.<ref name=":1">https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q&s=19</ref>

Line 159:

Line 151:

=== Conflict with Open Source and Maker Values ===

Bambu Lab's printers had previously been praised for their integration with open-source tools & community-developed software

Bambu Lab's printers had previously been praised for their integration with open-source tools & community-developed software{{Citation needed}}. The authorization system departs from , moving from an open ecosystem where users could freely modify & automate their printers to a closed, manufacturer-controlled environment. This change impacts:

. The authorization system departs from , moving from an open ecosystem where users could freely modify & automate their printers to a closed, manufacturer-controlled environment. This change impacts:

* Users of open-source slicing software like OrcaSlicer

Line 203:

Line 191:

== Comparisons to Similar Practices by Other Companies ==

Bambu Lab's new authorization & authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as HP or Epson, who have also faced backlash around their handling of digital rights management (DRM)

Bambu Lab's new authorization & authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as HP or Epson, who have also faced backlash around their handling of digital rights management (DRM){{Citation needed}}. These comparisons address:

. These comparisons address:

* '''Forced Updates''': Firmware updates have rendered third-party ink cartridges incompatible, forcing users to purchase proprietary consumables.

* '''Restricted Features''': Scanner/printer combos that will not scan if the ink is empty."

@@ Line 73: / Line 73: @@
 === Permanent Nature of the Update ===
-Once a printer is updated to the new firmware, users cannot revert to previous versions that allow fuller third-party integration
+Once a printer is updated to the new firmware, users cannot revert to previous versions that allow fuller third-party integration{{Citation needed}}. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.
-{{Citation needed}}
-. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.
 The manufacturer states this change is required for security, but community members note that many of the security vulnerabilities being addressed stem from Bambu's own cloud-centric design choices rather than inherent risks of local network control<ref>https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/12</ref>. The update forces users into Bambu's ecosystem of applications & cloud services, regardless of their preferences or needs for local network automation.
-This has been characterised as a significant post-purchase reduction in functionality for existing owners who bought their printers with the understanding they could use third-party software & home automation tools
+This has been characterised as a significant post-purchase reduction in functionality for existing owners who bought their printers with the understanding they could use third-party software & home automation tools{{Citation needed}}. The inability to revert these changes, combined with the mandatory nature of the update for new printers, demonstrates how manufacturers can use software updates to unilaterally modify the capabilities of hardware products after purchase<ref>https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/9</ref>.
-{{Citation needed}}
-. The inability to revert these changes, combined with the mandatory nature of the update for new printers, demonstrates how manufacturers can use software updates to unilaterally modify the capabilities of hardware products after purchase<ref>https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/9</ref>.
 For users that would want to use a third-party slicer, Bambu would require those users to download and install Bambu Connect in order to send gcode wirelessly over LAN or over the cloud. While Bambu claims that they were in contact with SoftFever, the developer of OrcaSlicer, as of writing, SoftFever still does not have any keys for Bambu Connect.<ref name=":1">https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q&s=19</ref>
@@ Line 159: / Line 151: @@
 === Conflict with Open Source and Maker Values ===
-Bambu Lab's printers had previously been praised for their integration with open-source tools & community-developed software
+Bambu Lab's printers had previously been praised for their integration with open-source tools & community-developed software{{Citation needed}}. The authorization system departs from , moving from an open ecosystem where users could freely modify & automate their printers to a closed, manufacturer-controlled environment. This change impacts:
-{{Citation needed}}
-. The authorization system departs from , moving from an open ecosystem where users could freely modify & automate their printers to a closed, manufacturer-controlled environment. This change impacts:
 * Users of open-source slicing software like OrcaSlicer
@@ Line 203: / Line 191: @@
 == Comparisons to Similar Practices by Other Companies ==
-Bambu Lab's new authorization & authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as HP or Epson, who have also faced backlash around their handling of digital rights management (DRM)
+Bambu Lab's new authorization & authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as HP or Epson, who have also faced backlash around their handling of digital rights management (DRM){{Citation needed}}. These comparisons address:
-{{Citation needed}}
-. These comparisons address:
 * '''Forced Updates''': Firmware updates have rendered third-party ink cartridges incompatible, forcing users to purchase proprietary consumables.
 * '''Restricted Features''': Scanner/printer combos that will not scan if the ink is empty."