I found out there was a discussion in the developer-team of vino in 2006, see https://bugzilla.gnome.org/show_bug.cgi?id=344839
They decided to implement an option to use gnome-keyring for security-reasons, but they also decided to leave it off by default because "it's not really a good idea"
I have no idea why the one who compiled vino-server for Ubuntu 10.04 decided different now and why he doen't tell us.
Please use gconf again to store the vnc-password!
It will be stored Base64-encoded in $HOME/.gconf/desktop/gnome/remote_access/ and this is secure enough, I think. If someone has unallowed access to this file, you have bigger security-leaks than a weak vnc-password-encryption.
I found out there was a discussion in the developer-team of vino in 2006, see /bugzilla. gnome.org/ show_bug. cgi?id= 344839
https:/
They decided to implement an option to use gnome-keyring for security-reasons, but they also decided to leave it off by default because "it's not really a good idea"
I have no idea why the one who compiled vino-server for Ubuntu 10.04 decided different now and why he doen't tell us.
Please use gconf again to store the vnc-password! gconf/desktop/ gnome/remote_ access/ and this is secure enough, I think. If someone has unallowed access to this file, you have bigger security-leaks than a weak vnc-password- encryption.
It will be stored Base64-encoded in $HOME/.