Bug for 9.04

[Steven Susbauer]

On Sat, 23 May 2009 10:07:00 -0500, Karl F. Larsen <klarsen1 at gmail.com>  
wrote:

> Steven Susbauer wrote:
>> On Fri, 22 May 2009 17:29:40 -0500, Karl Larsen <klarsen1 at gmail.com>  
>> wrote:
>>
>>
>>>     I discover that /usr/bin/nm-applet is a binary file that does
>>> something for network manager and it is somehow screwed up about a
>>> "default keyring". This is too complex for me to fix.
>>>
>>> Karl
>>>
>>>
>>>
>>
>>
>> What issues is it having? Keyrings are usually managed with seahorse (in
>> Applications> Accessories> Passwords and encryption keys).
>>
>> nm-applet is the graphical program that shows in the gnome-panel (IE:  
>> it's
>> a panel applet), which you use to connect to networks.
>>
>>
>     I removed seahorse from my Jaunty but the keyring problem continues.
> So it is not a seahorse problem it appears. But it appears seahorse
> controls the keyrings (and no idea what a keyring is) and I know
> something in this area is making NetworkManager look bad.
>
>     None of this is seen while loading Ubuntu. But it sure comes to
> light if your using WiFi Internet.
>
>
> Karl
>
>

I am using WiFi internet, I set the keyring password once and it has never  
been an issue since. Yes, seahorse manages keyrings. Keyrings are where  
well-written programs store their passwords, it's much better than every  
program storing them in an insecure configuration file. Keyrings can be  
set to have a master password to unlock them, or to unlock on login. All  
of this, including resetting the master password or deleting the keyring  
(it will be recreated, but at least you would know the password), can be  
accomplished in seahorse which you should not remove.

If it is just asking if nm-applet can have access to the keyring, hit  
Always Allow.