Two security steps for Sovol Zero, SV08 and SV07 owners

Two things worth doing on a Sovol Zero, SV08 or SV07, especially if it’s on a network shared with other people or devices. I’ve reported the details to Sovol privately and will hold them for now, so this is just what to do.

  1. Turn off the WiFi configuration service, on a Zero running 1.4.6 or 1.4.7 and on an SV08 with the Eddy kit update installed. It’s the back end for SOVOL WIFI Tool and runs all the time. Nothing else on the printer uses it. Over SSH:
sudo systemctl disable --now wifi_server

If you need SOVOL WIFI Tool later, turn it back on while you use it, and off again afterwards:

sudo systemctl enable --now wifi_server

A firmware update can turn it back on, so check after updating. systemctl is-active wifi_server should say inactive.

  1. Regenerate your printer’s SSH host keys. Over SSH:
sudo rm /etc/ssh/ssh_host_*
sudo dpkg-reconfigure openssh-server
sudo systemctl restart ssh

The next time you connect, your SSH client will warn that the printer’s host key has changed. That’s expected this once. Remove the old entry on your computer with ssh-keygen -R <printer-ip> and connect again.

Checked on my own Zeros: step 1 on 1.4.7, step 2 on both 1.4.7 and 1.3.7.

Thanks. Didn’t need it for my SV08, since I mainlined it.
But my Zero…
I’ve had some suspicious thoughts about that wifi…

Thanks, and looking forward to hear more about the background.

I had already disabled the wifi_server.py, and also connect_wifi.sh, by commenting them in /boot/scripts/btt_init.sh (probably not the proper way, but works).
I was trying to get WiFi to work reliably on my Zero - But that didn’t help.
Nothing else that I have tried either, so still no success… :angry:

I don’t think I’ve seen any Zero user that have got it working, so its about time for Sovol to to fix the issue… Hopefully this issue by rpcyan can act as a trigger…

I got it to work, you have to turn off WPA3 for it to connect. But that also turned off some of my security cameras, so the Zero stays plugged in.

When you mention it, I think I can recall I’ve read something about WPA3.
I know I have tested WPA2, WPA3 and both. And I then I thought I might have settled with your compromise. But now, looking in my router config, I left it in WPA2..! So that didn’t do the trick.

Why don’t I document my troubleshooting? I know I’m gonna flush my working memory… and that I will want to pursue some day.

Maybe it was turn on WPA3, honestly I forget. I did post it on site somewhere, but I can’t find it.

If I remember correctly, you’re right: you have to disable WPA3.