registry team mailing list archive

[Allan Pratt <apratt@xxxxxxxxxxxx>]

I'm not sure I'm reading this bug system's UI properly, but it looks
like this is still open ("New" not "Invalid") as regards the "GNOME
keyring" subsystem, and that's where the upstream bug is being tracked.
This bug is closed ("Invalid") with respect to the subsystem "gnome-
keyring (ubuntu)" but it's been in that state since April and people
have continued to comment on it - most especially Forest adding his
excellent analysis.

It is the upstream bug that I think could usefully be updated with more
information to help it get attention. I can't do it properly myself,
because I don't have a first-hand analysis of the chain of events that
causes the symptoms, the way Forest does.

As for the concern that key storage would be insecure: Enabling auto-
login generally means "Anybody who turns this computer on can see my
private stuff." I should not be prohibited from making that tradeoff
between security and convenience, certainly not by a cascade of bugs and
flawed bug-fixing decisions.

In any case, I found an alternate workaround for my problem: remove
network-manager and network-manager-gnome, and install the network
management package "wicd" instead. After you use "wicd-curses" to
configure the wireless network, you can both auto-logon and auto-connect
to wireless. This doesn't help with "empathy" but that's not the issue
that brought me here.

-- 
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for GNOME Keyring.