[SOLVED] Unlock Keyring

[andrewsimpson]

Having been through this too; I found lots people asking, but few answers.

1. Choose Applications --> Accessories --> Passwords and Encryption Keys.

2. In the application, chose Edit --> Preferences

3. Highlight the 'login' text in the main box, and choose 'Change Unlock Password'.

4. Enter your normal login password for current password. Leave the new password fields blank (as in "no password").

5. Click 'Change'. Expect a dialogue box saying that having no passwords is insecure. Click 'Accept', and keep clicking all the way out!

6. Enjoy your password free Network Manager...

Note: There is another application under System --> Preferences --> Encryption and Keyrings. This is not what you want - don't try this application

[lovinglinux]

Note: There is another application under System --> Preferences --> Encryption and Keyrings. This is not what you want - don't try this application

They are both parts of the same tool. You can access the "System --> Preferences --> Encryption and Keyrings" from the preferences menu of "Applications --> Accessories --> Passwords and Encryption Keys". I guess they have different menu entries just to facilitate (or complicate).

[andrewsimpson]

They are both parts of the same tool. You can access the "System --> Preferences --> Encryption and Keyrings" from the preferences menu of "Applications --> Accessories --> Passwords and Encryption Keys". I guess they have different menu entries just to facilitate (or complicate).

Being a long time KDE user (that doesn't like KDE 4.1), you could call me Gnome beginner and usability tester.

There seems to be no (easy) way that you can access the keyring from System --> Preferences --> Encryption and Keyrings. I spent a long time trying to solve this one, and only found the other route by chance. It was very confusing.

[lovinglinux]

I spent a long time trying to solve this one, and only found the other route by chance. It was very confusing.

But that was exactly what I said. You can access the Preferences tool from the Accessories tool, not the inverse.

[andrewsimpson]

But that was exactly what I said. You can access the Preferences tool from the Accessories tool, not the inverse.

Apologies, I misread your post. O.K., I'm getting out of this thread.

[SamNSane]

Having been through this too; I found lots people asking, but few answers.

1. Choose Applications --> Accessories --> Passwords and Encryption Keys.

2. In the application, chose Edit --> Preferences

3. Highlight the 'login' text in the main box, and choose 'Change Unlock Password'.

4. Enter your normal login password for current password. Leave the new password fields blank (as in "no password").

5. Click 'Change'. Expect a dialogue box saying that having no passwords is insecure. Click 'Accept', and keep clicking all the way out!

6. Enjoy your password free Network Manager...

Note: There is another application under System --> Preferences --> Encryption and Keyrings. This is not what you want - don't try this application

You laid it out in a very much nicer format than I did, but that's the same procedure I outlined a couple of posts above yours. Unfortunately, it seems that any alteration at all in the normal scheme of things, logging-in-wise (like using automatic login), seems to discombobulate this feature. And, of course, there are lots of folks who've been through a change of password or two and then run into the problem with needing to set up a new default wireless network. They may no longer have or remember the unlock password they need to use to unlock the manager so they can give it the new password. At this point, direct manipulation of the pertinent file is necessary to fix the issue.

Even though I use wicd to replace Network Manager in HH (because NM in 8.04 is really, really inept for handling lots of different networks, some of which are dhcp and some of which are fixed IP), I continue to go into the Password and Encryption Keys applet to resynchronize the login password after every change of the user account password -- just in case I ever decide / need to revert.

[andrewsimpson]

You laid it out in a very much nicer format than I did, but that's the same procedure I outlined a couple of posts above yours. Unfortunately, it seems that any alteration at all in the normal scheme of things, logging-in-wise (like using automatic login), seems to discombobulate this feature. And, of course, there are lots of folks who've been through a change of password or two and then run into the problem with needing to set up a new default wireless network. They may no longer have or remember the unlock password they need to use to unlock the manager so they can give it the new password. At this point, direct manipulation of the pertinent file is necessary to fix the issue.

The important thing is to set 'no password', then Network Manager can access the keyring without requiring any password.

[SamNSane]

The important thing is to set 'no password', then Network Manager can access the keyring without requiring any password.

In which case, I would argue, it doesn't even make sense to keep using Network Manager -- at least certainly not in Hardy. Better of going with wicd, which is more versatile.

[frankleeee]

In which case, I would argue, it doesn't even make sense to keep using Network Manager -- at least certainly not in Hardy. Better of going with wicd, which is more versatile.

I think it is a matter of choice NM-Manager broke in intrepid, so I installed wicd which took a week to go belly up, I reinstalled NM and haven't had a problem since.

[SamNSane]

I think it is a matter of choice NM-Manager broke in intrepid, so I installed wicd which took a week to go belly up, I reinstalled NM and haven't had a problem since.

The nm applet is a LOT better in Intrepid than it is in Hardy. In Hardy, it is just adequate for those who almost exclusively use dhcp to get their IP addresses. It is downright inconvenient-bordering-on-unuseable for people who have to use multiple fixed / dhcp setups on both wired and wireless networks.

I haven't had either one (nm or wicd) fail on me, no matter how complex the setup I was using. But I can't be bothered to have to go through so much trouble to perform a function that should work darned near automatically, once set up correctly. Wicd has just worked for me in every Ubuntu version I've used. NM, not so much -- until Intrepid.