Creality K2 series GPLv3 violation: Difference between revisions
No edit summary |
editorial changes |
||
| Line 12: | Line 12: | ||
This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line: | This licensing issue systemically affects the firmware images distributed across the entire flagship K2 hardware line: | ||
* '''K2 SE:''' V2.3.6.49 (`CR4CU220812S11_ota_img_V2.3.6.49.img`) | *'''K2 SE:''' V2.3.6.49 (`CR4CU220812S11_ota_img_V2.3.6.49.img`) | ||
* '''K2:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) | *'''K2:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) | ||
* '''K2 Pro:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) | *'''K2 Pro:''' V1.1.5.5 (`CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img`) | ||
* '''K2 Plus:''' V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`) | *'''K2 Plus:''' V1.1.5.5 (`CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img`) | ||
==Incident== | ==Incident== | ||
Creality distributes pre-compiled shared library objects (`.so`) and object files (`.o`) inside Klipper's core directory structures without providing the corresponding source code. These files handle proprietary hardware wrappers and communicate intimately with the GPLv3 host: | Creality distributes pre-compiled shared library objects (`.so`) and object files (`.o`) inside Klipper's core directory structures without providing the corresponding source code. These files handle proprietary hardware wrappers and communicate intimately with the GPLv3 host: | ||
* `serial_485_wrapper.so` (Manages RS-485 serial communication bus) | *`serial_485_wrapper.so` (Manages RS-485 serial communication bus) | ||
* `box_wrapper.so` | *`box_wrapper.so` | ||
* `filament_rack_wrapper.so` | *`filament_rack_wrapper.so` | ||
* Compiled `.o` object files tied directly to the Color Format System (CFS) multi-material management library. | *Compiled `.o` object files tied directly to the Color Format System (CFS) multi-material management library. | ||
Following a formal compliance demand issued on May 14, 2026, and an official acknowledgment from front-line support on May 15, 2026, a 14-day compliance deadline was established on May 20, 2026. Because compliance was not met, the violation trail was formally logged with the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) on May 27, 2026. Creality continues to distribute the K2 hardware and locked-down firmware images to retail consumers while remaining in active violation of the GPLv3 license terms. | Following a formal compliance demand issued on May 14, 2026, and an official acknowledgment from front-line support on May 15, 2026, a 14-day compliance deadline was established on May 20, 2026. Because compliance was not met, the violation trail was formally logged with the Software Freedom Conservancy (SFC) and the Free Software Foundation (FSF) on May 27, 2026. Creality continues to distribute the K2 hardware and locked-down firmware images to retail consumers while remaining in active violation of the GPLv3 license terms. | ||
===[Company]'s response=== | ===[Company]'s response=== | ||
On May 24, 2026, Creality sent a written response stating: ''"Due to the involvement of custom firmware modules, underlying dependencies, and the need to clarify copyrights from multiple parties, the compilation of relevant materials requires a considerable period of time. Currently, we are unable to directly provide the corresponding source code or updated repository links."'' | On May 24, 2026, Creality sent a written response stating: ''"Due to the involvement of custom firmware modules, underlying dependencies, and the need to clarify copyrights from multiple parties, the compilation of relevant materials requires a considerable period of time. Currently, we are unable to directly provide the corresponding source code or updated repository links."'' | ||
| Line 34: | Line 30: | ||
On May 31, 2026, Creality deflected subsequent inquiries regarding the legal implications of copyleft contamination to standard customer service troubleshooting scripts, closed active communication on the ticket, and forwarded the entire case history to their internal legal department and R&D managers without providing a compliance timeline. | On May 31, 2026, Creality deflected subsequent inquiries regarding the legal implications of copyleft contamination to standard customer service troubleshooting scripts, closed active communication on the ticket, and forwarded the entire case history to their internal legal department and R&D managers without providing a compliance timeline. | ||