I see. Thx for taking the time to share this info. Appreciated.
1 Like
I had to do that periodically from the very beginning. Rural internet connections can be a real B.
Found this while looking through new Studio 2.0.2 release notes:
So contributions from OrcaSlicer developers are still welcome, but the same people cannot be trusted with printer control through the cloud. Seems a more than a bit hypocritical.
5 Likes
On a more positive note, Studio 2.0.2.57 will now import settings and Project info from an Orca 2.3.0 .3MF file instead of just the geometry.
More work on this is needed. Even though I cannot find a newer beta than the 2.0.2.57 public release I still received this notice:
But click through this and a couple more warnings and all the settings loaded and I could read the informational pdf shown in the Project tab.
1 Like
anyway you turn its exploitn nothing else…
Give credit where it is due - as Ikarus wrote hypocrits…
1 Like
They offered orca direct integration with Bambu Connect, Orca said no
2 Likes
yeah that will go in history books to teach in the future.
The reality is BL denied Orca any access - Look around on the web Softfever published their response regarding integration … and it did not begin or end with any words offering or allowing the integration but quite the contrary.
3 Likes
So basically “believe my narrative, not what actually happened”
how about no
i think Bambu messed up majorly with the way they handled and way they implemented the printer security - but something was needed, and they warned people like Panda Touch for years and offered Orca integration.
The truth is neither Orca nor Bambu are the villain nor the hero. They do need to learn to get along, and Orca taking puritan stances is not the virtue you think it is.
3 Likes
Man, I think my history books skipped some stuff about the puritans.
1 Like
C++ was in fact used, but only in an obfuscator to decrypt the main JS code when it’s loaded: asarmor/src/encryption/main.cpp at master · sleeyax/asarmor · GitHub
3 Likes
What’s something and why was it needed?
If Bambu Studio can use the “super secure” new network plugin, why can’t Orca Slicer?
3 Likes
To answer your second one first:
because they didn’t want to disclose the code to Orca, so they instead provided a connector. I don’t think it is the right solution, but it’s pretty standard for companies to not want to share network code. Orca refused to accept their connector.
to answer the first question:
are your serious in that you don’t understand why completely insecure access being able to trigger arbitrary prints might be a bad idea?
that’s little better than a remote code execution vulnerability. well it kinda is one but only “sorta like”
here let me send a 256mm^3 of 100% infill multicolor print to your printer, sounds good right?
2 Likes
- username+password has always been required for the MQTT connection. That’s called a “knowledge factor” in the security field, and ensures only you can trigger prints on your own printer.
Good luck trying this, it won’t work.
- The network plugin was closed-source previously as well and Orca loaded it without problems. Slicer interacts with it via function calls etc and doesn’t need to know how it works internally.
4 Likes
like i said - i don’t think their approach to the solution is the correct one. they could have implemented a purely open source and fully secure solution, and their complaints about third party slicers affecting their cloud stability is a them problem and they should have fixed their end.
3 Likes
Better nothing, so that everyone knows it’s not secure (and they can even take their own proactive measures if they care), than fake security that gives people a false sense of security.
1 Like
Won’t work on mine for sure. Because I don’t leave the dang thing turned on 24/7.
And when it is on–it’s monitored!!!
Sorry I forgot that Big Bambu knows what mandatory rules are best for me and my property.
4 Likes
You should have known by now: Big Bambu Brother knows best what’s good for you and what’s not.
1 Like
you’re free to use X1+ third party firmware
ROTFL the MQTT protocol had been reverse engineered. how do you think a panda touch works?!
why is it that people assume just because they don’t know something everyone else doesn’t know it either. lol
2 Likes
You forgot already that this is a response to “not wanting to share code of the network plugin” from a few hours ago?
You cannot accept that you are wrong and then make up completely different strawman arguments that aren’t even related to Orca Slicer (which has only ever used the network plugin, not created the MQTT connection by itself) 
2 Likes