Propose your solution
Attachments
Duplicates
Comments
|
|
|
Actually Debian has something like this. I can set it to save the keyring's password or admin passwords and not ask for them again. KDE also has an option of having Wallet Mg have a blank password. If I've already typed in my password to login, or set it not to ask, why should I have to type in my keyring password for Pidgin, Evolution or Wireless?
|
|
|
I am not convinced and I think you're missing something here...
YES asking to unlock the keyring for a wireless key is a bad behavior.
And this planned to change on the version 0.7 of the Network Manager. (see the bug report I attached)
The real question is what do you use the keyring for. A wireless key is IMO not what it should be used for (if someone has access to your computer I guess someone stealing your wireless key is not the biggest problem)
NOW if you were to use the keyring for important information (login to your bank account, credit card number...) you might really want it to be closed by default.
|
|
|
|
How about an option? Let the user decide how he/she wishes to use their computer.
|
|
Ansible
wrote on the 13 Mar 08 at 18:54
|
|
|
Don't know if this is the same problem, but I was having the same thing happen - prompt for keyring whenever connecting to WEP. For me, it was because I changed my password and now the regular password was different from the keyring password. Therefore, I got prompted continually.
I forget what the fix was, but I found the answer on the forums. Some command that reset something or other.
So anyway, now I don't get any keyring prompts anymore.
|
|
DavidONE
wrote on the 26 Mar 08 at 14:46
|
|
|
How is this implemented?
I'm running 8.04 with auto-login and I'm prompted for keyring each login. My login password and keyring password are the same. :/
|
nand
(Brainstorm admin)
wrote on the 29 Jul 08 at 11:58
|
|
|
Changed to "New".
In fact, I'm not sure if this behavior is by design (and in this case, this is a valid idea) or if this is not behaving as designed (and in this case, it is just a bugreport, and it should not be here)
|
|
|
|
In Intrepid you can set the password as blank and it doesn't ask anymore. I'm glad too because I don't want to use Wicd when there is such a nice new network manager.
|
|
|
|
To deal with this problem, run seahorse/"Passwords and Encryption" and go to its "preferences" in the menu. That's the (mostly hidden) location that manages the keyrings.
|
|
saivann
(Brainstorm moderator)
wrote on the 22 Feb 09 at 18:41
|
|
|
How to disable password keyring (and use unsafe password storage) :
Intrepid :
1. Go to Applications / Accessories / Passwords and Encryption.
2. Click on Edit / Preferences
3. In the Password Keyring tab, select the "login" keyring and click on "Change unlock password".
4. Leave the new password blank and apply changes.
Jaunty :
1. Go to Applications / Accessories / Passwords and Encryption.
2. Go to the "passwords" tab.
3. Right click on the login keyring and click "change password".
4. Leave the new password blank and apply changes.
So it's already possible to have unsafe password storage, however I don't know about automatic unlock of the keyring with GNOME autologin, there might be security reasons why it isn't enabled by default at mean time.
|
|
ronchong
wrote on the 15 Nov 09 at 02:55
|
|
|
to stop the keyring from popping up...
right click the connection
EDIT the connection
go to which connection of concern
select it
then click on EDIT...
there will be a pop up asking you if u want to save the default keyring for every connect.. just click YES
and VOILA!
no more annoying pop up!!!
at least it worked for me..
i just tried it and rebooted.. and no pop up.. :)
hope it works for you also!
|
|
|
|
Awesome ronchong, that's just what we need - automatic wireless authentication without insecure global keyring access. Now if I could just figure out how to grant permissions for shutdown/restart...
|
|
RonCam
wrote on the 3 Mar 10 at 14:08
|
|
|
This thread is a few months old, but as a service to folks coming across it with a search engine, here is the solution that worked for me and it's different from the above:
Right-click Network Manager Applet icon, Edit Connections ...
Select Wireless tab, then Select wireless connection experiencing the problem.
Click Edit.
Place check mark into box at bottom: Available to all users
It's not unclear or a bug, once you have the answer. There should be a Help button, or at least a Tool-tip over this selection, so users would know the effect of this setting.
I have just updated the OS -- if this check-box is missing, do the same.
|
|
|
Thanks RonCam. I think your workaround does not work for Ubuntu 8.04 which is in heavy use in 2010.
Also, Thanks Rauli ! Your tip is a good workaround for this very nasty bug.
Steps for Ubuntu 8.04
==============================
- First, get to the point where you see the bug and error dialog by following these steps in the bug report
https://bugs.launchpad.net/bugs/532200
Then....
- From your desktop use the pull down menu Applications-Accessories - Password and Encryption Keys
- Use the pull down menu Edit-Preferences
- You should be on the TAB ""password keyrings"
- See default and login
- With the mouse single click login
- With the mouse click the button "change unlock password"
- type in the old password, and leave the new blank
- See the dialog giving you a warning about weak security
- Click ok
- Shut down, leave off 10 seconds, boot
- Notice you have to logon to get to your desktop
- Use the Pull down menu System- administration - login window
- Use the mouse to click the TAB up top "Security" then put a check in the checkbox for auto logon, and put the username ( example: fred ) in the text field
- Restart your system, bingo! You get to the deskstop and you get WiFi auto logon to a hotspot with a password.
but yikes, that is a lot of crazy steps for something that works easily in Mac and Windows dating back to both OS9 and Win 98. We all know auto logon is a security risk, so there is no need to make a user jump through so many hoops when they willingly take the risk.
Another IDEA.... Why not have someway to set auto desktop logon, and then be able to easily toggle some ( but not all ) cachehd passwords as being unlocked for the auto logged on user? Seems like 20 ways to solve this. Have some type of "Auto Logon" button/widget or User Interface in the Application for Keyrings.
|
|
|
YAY for 10.04! If you don't want to use passwords for wireless networking,
right click wifi icon, edit connections, select wireless tab, select wireless ap, select "make available to all users", hit apply.
Next time you reboot it will automatically connect to that wifi network.
Greg.
|
|
|
I would like to note that while this is fixed for wireless connections ("all users" resolution), Keyring still does not provide any options for what keys should be managed.
As a direct example, I use Auto-login for my home media box and have the following issue:
I have it setup to require users to enter a password for remote desktop (connecting via VNC etc), which then causes a requirement of the keyring being unlocked before it will allow the VNC/remote desktop to connect.
As I use auto-login, I am not concerned with local security in the house. I do not want to use a blank password in keyring to open ALL of my passwords, nor do I want to use no password for remote desktop connections, which would allow anyone to connect.
Ideally, as mentioned previously, some configuration options would be appreciated, so that I would be able to set it so that remote desktop does not use Keyring, or to leave that password unencrypted so that the keyring does not require unlocking before I am connected.
Alternatively, if the unlocking could be done through an SSH session, that would also solve the issue, though less gracefully.
Dan
|
Post your comment
|
