On Thu, 2005-06-23 at 09:46 -0400, Dan Williams wrote:
On Thu, 2005-06-23 at 00:11 -0400, Robert Love wrote:
On Wed, 2005-06-22 at 23:49 -0400, David Zeuthen wrote:
So, I guess my point is that we shouldn't care too much about annoying
gnome-keyring dialogs at this point. Not that it
On Thu, 2005-06-23 at 10:33 -0400, Bill Peck wrote:
Is there a technical reason why the keyring can't be unlocked by the
login? (Obviously the passwords would have to be the same) I know I'm
thinking in fairy land where we might have single sign on one day.. but
I can dream can't I?
The hack
On Thu, 2005-06-23 at 10:33 -0400, Bill Peck wrote:
Is there a technical reason why the keyring can't be unlocked by the
login? (Obviously the passwords would have to be the same) I know I'm
thinking in fairy land where we might have single sign on one day.. but
I can dream can't I?
Well,
On Wed, 2005-06-22 at 22:19 -0400, Dan Williams wrote:
Quite right. At this time NM queries nm-applet for all networks when it gets
the NameOwnerChanged. What you propose sounds reasonable. We don't really
_need_ the key until we try to connect to the access point.
Agreed.
[1]
Attached patch adds support for gnome-keyring to nm-applet and stores
the essid key encrypted in the keyring instead of cleartext in gconf.
It is a first pass, but it seems to work well [1].
One issue is it causes the gnome-keyring decrypt your keyring dialog
to pop up as soon as the applet
On Wed, 2005-06-22 at 22:02 -0400, Robert Love wrote:
Attached patch adds support for gnome-keyring to nm-applet and stores
the essid key encrypted in the keyring instead of cleartext in gconf.
It is a first pass, but it seems to work well [1].
One issue is it causes the gnome-keyring
On Wed, 2005-06-22 at 23:49 -0400, David Zeuthen wrote:
So, I guess my point is that we shouldn't care too much about annoying
gnome-keyring dialogs at this point. Not that it doesn't matter, cause
it does, however all that work is elsewhere really.
Nod.
We can do a lot better, though.
