The VNC gui has a password, implemented as official VNC authentication, which is read from /data/conf/vncpassword.txt. Now that VNC GUI transitions to MQTT, users still need to be able to set a password for local (LAN) MQTT use.
Note: this is not for authentication through VRM.
GUI applications will need to get the ability to present the username with a password prompt. The username can be hard-coded (to the application name for instance), because the situation we came from didn't have a username.
[x] Have the dbus-flashmq plugin support the /data/conf/vncpassword.txt file. Done. Any username is accepted, because that password file only specifies the password.
[ ] Have GUIv2 support it.
[ ] Have MFD app (/app) support it.
[ ] Unsure: have VictronConnect support it. Is it needed, or will it all be guiv2?
[ ] Once all done, pull it all together in a Venus build.
The VNC gui has a password, implemented as official VNC authentication, which is read from
/data/conf/vncpassword.txt
. Now that VNC GUI transitions to MQTT, users still need to be able to set a password for local (LAN) MQTT use.Note: this is not for authentication through VRM.
GUI applications will need to get the ability to present the username with a password prompt. The username can be hard-coded (to the application name for instance), because the situation we came from didn't have a username.
/data/conf/vncpassword.txt
file. Done. Any username is accepted, because that password file only specifies the password./app
) support it.