Virus warning with 4.4.15 klipper update

[jleadbetter]

I'm getting a virus warning in Chrome and Windows Defender when downloading the 4.4.15 release. To say this is worrisome is an understatement.

[CChen616]

We've checked the files and they're safe. These warnings can pop up with certain types of files or newer downloads. Feel free to double-check with other antivirus software if you're still unsure.

[CChen616]

Just a heads up, the update package includes components intended for use with QIDI Link, which might be flagged by antivirus software as high risk or potentially malicious. However, these components are safe and will not harm your computer. They are designed to run on the printer only after the update is installed.

[xTremePower]

Hello, can you explain me this joke ?!!

I own 4 Qidi, but in the max 3 firmwares no problem detected, in the Q1 no matter how i try, always show this

[xTremePower]

Just a heads up, the update package includes components intended for use with QIDI Link, which might be flagged by antivirus software as high risk or potentially malicious. However, these components are safe and will not harm your computer. They are designed to run on the printer only after the update is installed.

Hello,
Okay maybe, but I really have big trouble to trust someone who say me, don't wory it's a fake positive, just let it run, it's safe ...

[ShootLessDie]

Hello, I am also getting this virus warning in addition to the one in the screenshot above. Please fix.

[CChen616]

It's hard to remove the warning, so for those who are still concerned about the security alert, here is a temporary workaround:

1. Log into the printer's system using an SSH tool such as MobaXterm.
   username: root
   passwd: makerbase
2. Download this zip file, then use the SSH tool to upload the extracted files to the system.
   auto_update.zip
3. Change working directory to where the files are using cd command, for example:

cd /home/mks

and run the provided command.

bash auto_update.sh

4. After a while, you should see the screen begin to flash as the update proceeds. Wait for the update to complete.

The zip file utilizes an automatic update component introduced in version 4.4.15. After updating to this version, you can use the automatic update feature on the screen to update, bypassing the need to download the update package.

The update process requires an internet connection. For users without network access in their printing environment, it is still recommended to add the downloaded update package to the whitelist of your security software.

[greg9504]

I have version 4.4.16 firmware installed (factory). When I run autoupdate I get "Failed to obtain online version information." Error. Printer is connected to wifi and has access to internet. I can not download the latest firmware because it is immediately flagged as having a virus.

[CChen616]

If you can access the printer through Qidi Link but cannot update online, it is likely because the printer's system time is not synchronized, causing SSL certificate verification with the remote server to fail.

You can try using an SSH tool (I recommend Mobaxterm) to enter the printer system and run the following commands:

# username: mks
# password: makerbase
sudo apt-get remove --purge chrony
sudo systemctl start systemd-timesyncd
sudo systemctl enable systemd-timesyncd
sudo timedatectl set-ntp true
# set timezone
dpkg-reconfigure tzdata 

to synchronize the time.

Alternatively, you can add the update package to your antivirus software's whitelist.

[greg9504]

Hello @CChen616,

The second command failed

mks@mkspi:~$ sudo apt-get remove --purge chrony
[sudo] password for mks:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  chrony*
0 upgraded, 0 newly installed, 1 to remove and 230 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 147811 files and directories currently installed.)
Purging configuration files for chrony (3.4-4+deb10u2) ...
Processing triggers for systemd (241-7~deb10u8) ...
mks@mkspi:~$ sudo systemctl start systemd-timesyncd
Sorry, user mks is not allowed to execute '/usr/bin/systemctl start systemd-timesyncd' as root on mkspi.
mks@mkspi:~$

I then tried without sudo, the commands seemed to work but time/date is still wrong

Last login: Sat Oct 28 00:21:00 2023 from 192.168.1.18
-bash: service: command not found
mks@mkspi:~$ systemctl start systemd-timesyncd
mks@mkspi:~$ sudo systemctl enable systemd-timesyncd
[sudo] password for mks:
Sorry, user mks is not allowed to execute '/usr/bin/systemctl enable systemd-timesyncd' as root on mkspi.
mks@mkspi:~$ systemctl enable systemd-timesyncd
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ===
Authentication is required to manage system service or unit files.
Authenticating as: Mks,,, (mks)
Password:
==== AUTHENTICATION COMPLETE ===
==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: Mks,,, (mks)
Password:
==== AUTHENTICATION COMPLETE ===
mks@mkspi:~$ sudo timedatectl set-ntp true
[sudo] password for mks:
mks@mkspi:~$ date
Sat 28 Oct 2023 12:36:16 AM CST

[CChen616]

@greg9504
try using

dpkg-reconfigure tzdata 

to set the timezone and run sudo timedatectl set-ntp true agian

If it shows NTP service: active

mks@mkspi:/root$ sudo timedatectl set-ntp true
mks@mkspi:/root$ timedatectl
               Local time: Sat 2022-12-17 06:25:17 CST
           Universal time: Fri 2022-12-16 22:25:17 UTC
                 RTC time: Thu 2016-01-21 11:14:39
                Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no

The service is already activated, just wait for a while and the time shall be synced

mks@mkspi:/root$ timedatectl
               Local time: Wed 2024-06-12 09:45:21 CST
           Universal time: Wed 2024-06-12 01:45:21 UTC
                 RTC time: Wed 2024-06-12 01:45:21
                Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

[greg9504]

Thanks, but I just finished installing 4.4.19 via USB (everything is OK after installation). I had to turn off virus protection for the folder I downloaded it to.

[paulmmluap]

Turn off virus protection . . . everything will be fine. NO! Fix your code. This is ridiculous to ask us to turn off a threat protection.

[Moto-EMT]

We need an official Firmware Variant that will allow us to disable Qidilink. As you indicate this is the source of issues. And we have known security vulnerabilities associated with this particular service, and even as such you have not addressed identified issues that have previously been disclosed based on last reports.
https://github.com/snowdroppe/qidi-security-disclosure if anyone else is unware.

Now your customer support is reportedly good, How long until you properly respond to this.

[CarloSartori]

wow... so I can not update the printer because the time is wrong, but instead of just add the possibiliti to set it in the GUI I have to "play" with a consolle, uninstall a software (why was it installed if I can remove it like that?) and execut a bunch of others commands with root access.
And the work around is to download a file that is automatically detected and deleted as virus..
for the moment the printer is working fine, and I will not do any update... but this is very far from my espectations!

[zharptitza]

I think I'm cancelling my printer order after seeing this thread.

[dshonz]

После обновлени постоянно ошибка
Moonraker не смог запустить некоторые плагины, пожалуйста проверьте логи, обновите конфигурацию и перезагрузите moonraker.
file_manager
Moonraker Найдены предупреждения.
Component 'file_manager' failed to load with error: [Errno 5] Input/output error: '/home/mks/gcode_files/sda1/System Volume Information'
Конфигруцию для плагинов Moonraker можно посмотреть здесь.

Печатать не могу... РАспишите план как сделать откат версии без последствий

Это после обнолвения прошивки на 4.4.24

[Kt0-Nado]

A brand-new printer right out of the box refused to print from a USB stick.

It does print, but in the air, even though it performs calibration each time. From OrcaSlicer, it prints normally, and the built-in test models (like the boats) print fine as well. However, files from the USB stick print in the air.

I updated the firmware via USB to the latest version, 4.4.24 but it didn’t help. Instead, the printer broke.

How did this happen?

It’s strange! I started a 6-hour print, monitored it for an hour, and everything was working perfectly. I left for work, but when I came back, I discovered that after about 4 hours, the printer had started dragging strings of filament all over the surface, got tangled in them, ripped off its own fan cover, and then froze.

The result:

The printer is 5 days old.
It has printed 2.5 kg of filament.
Now it shows a printer configuration error, a Klipper error, and does not respond to commands related to movement or heating. The only functions that work are menu navigation and changing the language.
It’s surprising that the printer has no safety system to stop it when it encounters an obstruction. It’s VERY strange that the printer pulled with such force that it ripped off half of its own head...

[paulmmluap]

Orca did the same for me.  Qidi slicer works fine.  Not sure why. —PaulOn Jan 6, 2025, at 1:28 AM, Kto Nado ***@***.***> wrote: A brand-new printer right out of the box refused to print from a USB stick. It does print, but in the air, even though it performs calibration each time. From OrcaSlicer, it prints normally, and the built-in test models (like the boats) print fine as well. However, files from the USB stick print in the air. I updated the firmware via USB to the latest version, but it didn’t help. Instead, the printer broke. How did this happen? It’s strange! I started a 6-hour print, monitored it for an hour, and everything was working perfectly. I left for work, but when I came back, I discovered that after about 4 hours, the printer had started dragging strings of filament all over the surface, got tangled in them, ripped off its own fan cover, and then froze. The result: The printer is 5 days old. It has printed 2.5 kg of filament. Now it shows a printer configuration error, a Klipper error, and does not respond to commands related to movement or heating. The only functions that work are menu navigation and changing the language. It’s surprising that the printer has no safety system to stop it when it encounters an obstruction. It’s VERY strange that the printer pulled with such force that it ripped off half of its own head... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>