According to WayVNC source at https://github.com/any1/wayvnc/blob/30d ... ain=1#L112 there is no way to have password login without also enabling encryption. RealVNC had the option to have a password protected session without enforcing encryption. Having a password at least sets a basic fence around preventing random wildlife from entering without providing any actual security.
As far as I can tell, TightVNC client does not support encryption at all, so the only way to connect to wayvnc service is changing the 'enable_auth' in /etc/wayvnc/config from true to false.
Beware that WayVNC is way behind RealVNC in terms of experience. Even after getting it to work the mouse cursor can't even follow around without seconds delays vs delays measured in ms with RealVNC. labwc might be better for direct usage (no measurable difference for me yet) but remote usage is terrible. Even RPi4 wired with WayVNC is a slideshow compared to smooth motion with RealVNC over WiFi on an RPi1.
WayVNC on Bookworm will work... but ... just barely...
As far as I can tell, TightVNC client does not support encryption at all, so the only way to connect to wayvnc service is changing the 'enable_auth' in /etc/wayvnc/config from true to false.
Code:
sed -ie "/^enable_auth/ s/=.*/=false/" /etc/wayvnc/configservice wayvnc restartWayVNC on Bookworm will work... but ... just barely...
Statistics: Posted by reukiodo — Mon Dec 02, 2024 11:04 pm
