Apparently some group has broken Bambus encryption.

Apparently, as he claims, the logs reveal not only (further) licensing issues with Bambu, they also apparently send the complete Model you want to print to Bambu, which would be a huge issue for any companies using them.

What do you think?
Anyone ever checked on the size of the logs? Does it make sense that they actually send the whole Model?

/e: clarification, apparently the logs do not get sent to bambu by default on every print (even while in LAN-Mode) as it can be understood here, but all of this info is in the logs you can manually choose to send to Bambu (i.e. in the case of an issue with a print(/er) bambu is reasonably likely to ask for this).

  • @TheYangOP
    link
    English
    11 year ago

    I don’t think it’s necesarrily nothing, as sending all of that data is so comprehensive it should be communicated clearly by bambu, and it seems (but I don’t know!) That it isn’t.
    Sometimes you might want/need help and don’t want to send everything.

    For a lot of stuff partial gcode / sensor data around the issue should suffice for example.

    But it sounded way worse before the clarification, when I understood that it was sending those logs all the time.

    The open source license issues will be interesting, but probably irrelevant. We already can be rather sure that they already are in violation with BambuStudio and no one wants to spend the money to do anything about it.

    • AnonStoleMyPants
      link
      fedilink
      English
      11 year ago

      Sure yes I agree that it is shady and weird that they just don’t say what data is being sent. Not really sure why they don’t.

      It’s not that the data being sent is like too much or too in detail (though maybe WiFi ssid is unnecessary), it’s just that the company is weirdly not being upfront about this.