Unauthenticated VNC

Hello all,

Opening this issue to consult with you guys before keeping out-of-tree patches to bring back some functionality.

In !1021 (merged) a VNC authentication method was added.

This thread provides a good insight on the discussion !1021 (comment 1617088), and this

Maybe if the VNC port is only made available inside a tunnel that already takes care of encryption and authentication?

comment is precisely the scenario I'm trying to achieve right now (the port is exposed/service authenticated with VNC over an SSH connection).

Would the maintainers be opposed to perhaps adding a --dangerous-non-authenticated or similar flag to allow such cases? Having this is fairly common for embedded applications during local development/production programming on airgapped environments, where setting an user/password is an overhead.

Thanks!