Webvnc and "locked keyring" (updated)
Posted: Tue Dec 15, 2009 11:31 pm
I have upgraded to amahi 5 and f12 fairly smoothly. (It sure is easier if /var/hda/files is mounted on a separate partition, as I had).
At the moment I have one minor problem. I have set the Amahi/Fedora box to auto login to facilitate access via WebVNC. When I try to connect with WebVNC after a boot of the Amahi box, I get the message on the Amahi box "Enter password for default keyring to unlock". I enter the password for the amahi auto login user, and then everything is OK, at least until the next boot. This defeats the idea of webvnc by requiring access to the Fedora beox in order to set up a remote desktop.
Google has turned up a fair bit on this, but so far no luck. Does anyone have a suggestion?
(later - edited on Dec 17) I found a work around, I would still like to know a better solution. There's a bit of discussion here:
http://www.pubbs.net/fedora/200911/55396/
I did the following on the Amahi box:
1. start seahorse (applications->accessories->passwords and encryption keys)
2. on passwords tab, right click Passwords: login,
3. click password
4. enter user password for "old password", leave new password blank, click change
5. you will get a warning about security, accept, and you are done
What this accomplishes is changing the keyring password from your user password to blank. This is insecure because anyone can see whatever passwords are managed by Seahorse from your desktop session. This allows me to start a Webvnc session without having to type the keyring password on the amahi box. Only have to do it once after booting, but it defeats the purpose of autologin.
I don't understand this fully. The way I am using amahi in my home I'm not too worried about the security issue, but I do wish there were a better solution. This looks to me like a bug. Perhaps someone can find a better solution.
Thanks,
Tim
At the moment I have one minor problem. I have set the Amahi/Fedora box to auto login to facilitate access via WebVNC. When I try to connect with WebVNC after a boot of the Amahi box, I get the message on the Amahi box "Enter password for default keyring to unlock". I enter the password for the amahi auto login user, and then everything is OK, at least until the next boot. This defeats the idea of webvnc by requiring access to the Fedora beox in order to set up a remote desktop.
Google has turned up a fair bit on this, but so far no luck. Does anyone have a suggestion?
(later - edited on Dec 17) I found a work around, I would still like to know a better solution. There's a bit of discussion here:
http://www.pubbs.net/fedora/200911/55396/
I did the following on the Amahi box:
1. start seahorse (applications->accessories->passwords and encryption keys)
2. on passwords tab, right click Passwords: login,
3. click password
4. enter user password for "old password", leave new password blank, click change
5. you will get a warning about security, accept, and you are done
What this accomplishes is changing the keyring password from your user password to blank. This is insecure because anyone can see whatever passwords are managed by Seahorse from your desktop session. This allows me to start a Webvnc session without having to type the keyring password on the amahi box. Only have to do it once after booting, but it defeats the purpose of autologin.
I don't understand this fully. The way I am using amahi in my home I'm not too worried about the security issue, but I do wish there were a better solution. This looks to me like a bug. Perhaps someone can find a better solution.
Thanks,
Tim