Ubuntu Security :: Firefox Asking For Gnome-keyring ?
Jul 11, 2010
For a while now, firefox has been prompting gnome-keyring (twice)
There is one applet i know of on my system that wants me to enter my keyring pw twice "CPU Frequency Scaling Monitor" (i have a core2-duo cpu, a monitor for each cpu), but i have no clue why ff would be invoking a change in how ubuntu controls that app.
Is there any way of finding out, which application (or perhaps an add-on?) is actually asking for my keyring-pw (the input window just says "an application..." not like e.g. "synaptic package manager...".
I have Ubuntu 10.04 configured to login with Kerberos (as in [url]). Everything works fine, except gnome-keyring-daemon:
-If I login with a local user, gnome-keyring-daemon works right. Besides, the keyring is automatically unlocked with the login password.
-If I login with a Kerberos user:
- The session startup is considerably slower.
- /var/log/auth.log says something like:
Code:
- If I execute a program that needs the gnome-keyring (like Evolution), is desperately slow, and it says:
Code:
Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- If I kill all gnome-keyring-daemon (killall gnome-keyring-daemon), start a new one (gnome-keyring-daemon), and restart the application that uses the gnome-keyring, it works fine, but it ask me for the password to unlock the keyring (I think that this is the normal behaviour if gnome-keyring-daemon did not start before).
I have seen the configurations in /etc/pam.d and everything looks fine (with pam_gnome_keyring.so). Indeed, I think that if something was wrong here, the local user would not have the keyring unlocked automatically.
I wana know the difference between PAM and GNOME-KEYRING.
I have googled both of them and I found that they both are for authenticating users. and then some tutorials say that I can use gnome-keyring with PAM support!
So what is the difference and if there is no difference how then can I use gnome-keyring with PAM?
I'm trying Lubuntu for my low-resource netbook and I'm lovin' it.
But I can't get my ssh key passphrase work with the keyring manager.
I even created a new user account with a fresh home directory and it doesn't work. You run "ssh myname@mydomain.net" and it prompts you for the key passphrase in the terminal.
Expected behavior: with Gnome, you run "ssh myname@mydomain.net" and the password manager opens a GUI to ask for the passphrase. Once unlocked, it remains unlocked until you log off. Moreover, at that moment of unlocking you can tell it to remember the passphrase forever so it gets automatically unlocked next time you login.
The keyring works fine for the wireless password, and for luks-encrypted volumes, but not for Secure Shell keys.
I'm using Ubuntu Lucid, installed lubuntu-desktop package, using gdm session manager, all updated.
It seems to me that he passwords kept in GNU Keyring Seahorse, are not kept very safe, because if I'm logged in and someone access my cumputer they can see my passwords that are saved there. I have set a keyring password, but it seems that is it not all the time locked.What are some general follow guide rulles to make sure my passwords are kept safe and my encryption keys that I use.
Every time I log in, I get the "password for keyring default" question two or three times, unless I enter it immediately as it pops up, sometimes even that doesn't prevent it from respawning. What could be causing this? I'm using Maverick.
P.S. Hmm, I don't think I'll be watching the lunar eclipse much now, the sky is covered with smoke, maybe it's lunar apocalypse.
A while ago, I removed the Ubuntu One entry from my Startup Applications because it was annoying having to activate the keyring every time I booted up/logged on. Now, I am prompted for a password once I start Firefox (mind that it's only the first time I run Firefox after boot/login). I'm assuming it's Ubuntu One because of the sequence of events, but feel free to correct me if you think otherwise. How can I stop this?
I'm running an up-to-date installation of Lucid, and have come upon a little problem. It seems that applications are having trouble communicating with gnome-keyring-daemon.
When I connect to wireless networks -- even ones that are in the network manager -- it always asks me for a password.
Gwibber is crashing because it can't connect to the gnome keyring daemon.
And when I open the Passwords and Encryption Keys utility (on the Accessories menu), I get the error: "Couldn't communicate with key ring daemon."
I have verified that the daemon is starting up when I log in, that all of the appropriate keyring-related login items (certificate and key storage, secret service, & SSH key agent) are in place, and that the keyring works in other accounts on my machine. I have tried deleting my extant keyrings, but that has produced any success. And when I kill and restart the keyring daemon once I'm already logged in, the problem seems to abate.
I don't know if it matters, but for OS X compatibility purposes, I'm running as a UID under 1000.
A few days ago, I decided to setup my emailing applications (I use mutt, with offlineimap, imapfilter, and msmtp) to use gnome-keyring rather than have my email passwords stored in plain text inside these application's respective configuration files.
[1].I am successfully able to run them from the command line myself, but looking up the passwords from gnome-keyring fails when running from cron.
I came across a person calling svn with a cron job and authenticating via gnome-keyring
[2]. I've tried to adapt his solution, but I don't think I'm doing it right. I've made a comment on the blog author's post, but am still waiting to hear back.
Does anyone know how I'm supposed to incorporate the bash function from that author's post to give cron the correct environmental variables?
I think this counts as a security question. I didn't know where else to place this.It's really preventing me from doing some things, such as setting up the Empathy IM program for chatting and whatnot, and this default keyring really haulting any progress I can make on that front. It also pops up when I'm just booting up the laptop. My brother set the password and then forgot, so he tried all of these passwords and it would never work. It always pops back up several moments later and reiterates its question. It goes away when I click on 'Deny', but now I can't follow that same route when trying to set Empathy IM Client up. I would like to either do away with this password requirement, or just change it to something I can easily remember
I just reinstalled ubuntu lucid after accidentally damaging it, And I used all the same passwords and user names as before, I can login fine, and I can do sudo commands, but the gnome keyring wont accept my password, I tried changing my password using Applications>accessories>Passwords and encryption but that didn't work. How can I fix this so that keyring will accept my password, I need it to save my wireless router password.
but it doesn't seem to be accessible. Seahorse says: "Couldn't communicate with key ring daemon", and I never get asked to unlock my keyring on login (thus saved wireless keys are not available, for example). If I kill the gnome-keyring-daemon process and run it again from the command line, everything works. There are not messages in /var/log/messages from the keyring daemon, so i don't know what it is doing wrong.
How to permanently disable the gnome-keyring-daemon.
I've seen posts where there was a work around to store passwords in clear text. That's not a real solution. I've seen posts where killing the process and removing ~/.gnome2/keyrings is a temporary solution until next time you log in or reboot machine. Removing the package, will force removal of the whole kitchen sink. That's too intrusive.
There must be a way to stop this thing from starting up, ever.
I tried commenting out the entries in the /etc/pam.d/* files that refer to "pam_gnome_keyring.so", and have also unchecked the 3 keyring related entries under System --> Preferences --> Startup Applications, which are affiliated with these 3 files:
But I still get this one process once I log into the console window:
There must be one more file somewhere that says, "hey when someone logs in and starts up gdm, start the gnome keyring daemon".
For several weeks now I have been experiencing a problem with GNOME keyrings in Fedora 10 x86. Here is the thing: somehow out of the sudden GNOME started requesting the "Default Keyring" in order to connect to protected wireless networks it already knows. I don't remember having set one, maybe I did, and just in case I tried all my passwords to no avail.
On the other hand, XFCE, the desktop environment I use the most in that machine, has lost its ability to 'remember' passwords, which is a little painful in the long run.
I wouldn't want to just delete the keyrings because there are many stored already, and I want them back. Needless to say I have root access to the machine. Is it possible somehow as root (or as user) to fix that problem and restore both access to the stored passwords and the ability for Network Manager to remember them?
Just to be on the safe side I created another user and that one 'remembers' the stored passwords and is not prompted for the "Default Keyring".
On a fresh karmic install, I have a user account with ecryptfs enabled home directory. I want that directory to be secured when I log out.
I have two administrator accounts, user1 and user2. I log in as user1 (with ssh, will test regular logins tomorrow), /home/user1/.Private gets mounted to /home/user1, everything is fine. I log out.
I log in as user2, and /home/user1/.Private is indeed unmounted. But I can do
Code: sudo su - user1 which will ask me for the password of user2, and then I am logged in as user1, /home/user1/.Private is again mounted, without ever typing the password of user1. On the other hand if I invoke Code: ecryptfs-umount-private
Is there a way to identify exactly what application is asking for keyring access at the given time? I get this query every boot and it's getting annoying. The annoyance is there, but more importantly and from a personal security standpoint on desktop systems, it's pretty bad that it doesn't say what application want's the access.
I would like to use a wireless network, I type in the correct password but suddenly a new window pops up saying: 'an application wants to access to the keyring 'Vorgabe', but its is locked password:'
But I don't know what password it's talking about I went to Password and Encryption keys, there are two folders 'password: vorgabe' 'Password: login'
When I installed Ubuntu (Lucid) on my new computer, As well as the login password I was asked for a keyring password. I gave one, but I am not sure exactly why I need this password. It seems that it was required to let me access the wifi - even though this has its own security code. I found I could stop the system asking for it every time I tried to connect to the internet using wifi by checking a button in the network setup, but when I registered for Ubuntu One, I was again asked for it - twice, once when I registered and again when I set up Tomboy notes sync. Now I get asked for it again every time I switch on.
I would like to know why the keyring passwords are needed in addition to the login password for a single user computer, which mine is and also how I can stop it asking for this password when I switch the computer on. One suggestion I have seen is to make the keyring password the same as my login password. If that is the case, then how do I change the keyring password?
I have a problem where I am asked to unlock the keyring every time I use Evolution.I enter my password on the user select screen and login and have evolution save my email password but whenever I open the program it asks for the same password as I use to login. For security reasons I need to have my password requested at login but don't feel I need it for evolution as I thought my email password was enough.
F15 from fresh install off LiveCD. I find that on fresh login my ssh agent situation is a bit confused.
I normally ssh-add my keys to the authentication agent, and then ssh to remote hosts without thinking too much about it. Recently, the ssh command has been hanging. Running with -vvv shows it stops at the point it should talk to gnome-keyring:
At that point it hangs and a ctrl-c will kill it.
The ssh-add command cannot connect to the ssh agent:
If I run to that ssh hang again, and this time grep ps for keyring:
I haven't had any gnome-keyring-prompt window appear on my desktop. Checking all workspaces, and using the Gnome 3 Overview screen to visually view open windows, doesn't show it. "kill -9 2101" returns the hung ssh attempt to the prompt immediately. Thinking about it, I don't believe I've had the Gnome 'enter your password to unlock your keyring' prompt once since installing F15.
I noticed that SSH_AUTH_SOCK seems a little confused:
So it seems that gnome-keyring-daemon is using one tmp directory while my shell has been set up with another. If i manually set the SSH_AUTH_SOCK variable, things start working again:
As I now have to reset SSH_AUTH_SOCK in every terminal I want to use the agent in.
What's the next best step to investigating why the gnome keyring prompt isn't appearing, and how the SSH_AUTH_SOCK variable is getting mismatched with the gnome-keyring-daemon's tmp dir?
I want to store my svn password in the gnome-keyring so it is encrypted and 'secure'. I made the necessary changes to ~/.subversion/config, but even after running a few svn commands, I do not see an entry for SVN in the keyring.
What else do I need to do to get SVN using gnome-keyring? I will also be using this with git-svn.
I have a standard home set-up for my Ubuntu OS, and I would like to know whether its possible to cut out the repetitive prompts to enter the password, as when you connect to the internet or access files on a partition that's not home, or install new software.
I just changed my password now every time I start my computer the keyring wants my old password and it keeps doing weird things even after I type it in. Like Ubuntu will say No keyring found or something to that effect anyway.
It's been awhile since I've been on here. I suppose that can be considered a good thing, since I made the completely transfer to Ubuntu three months ago and everything's been running completely smoothly. Anyway, security is a pretty big thing to me. I usually change the root password, take sudo off (and default gksu, not gksudo), encrypt my hard drives, etc... One thing I also do is create a separate password for my login keyring. I don't mind having to enter one extra password at login, but it started prompting two times, and now three. It's the same password every time, so my question is..
I have never configured any keyrings. I set up Evolution, and it's working, but sometimes Gnome wants me to allow it to access the default keyring to get the email password. It takes 3 cancel-deny tries to finally dismiss this dialog box, after which Evolution is working fine. I see that this is not an Evolution thing. Other users report the same thing in VINO, and on wireless access. The GNOME forum seems to think there is a bug when accessing severs, and has a bug and milestone. Some other distros have the same problem.
One user says that they were able to Delete the default keyring (which must have had an unknown default password) and then create a New default keyring with thier own password. This seems to have solved that user's problem. However there were no instructions on how to do it. I think someone else was able to just stop the default keyring daemon. That would work too, although it's not as elegant. I'm now unable to find instructions.
NetworkManager stores its connection secrets in a keyring called "default". I am prompted to supply the keyring password every time I log in, regardless of whether I select the "automatically unlock this keyring when I log in" radio button.
After launching the gnome-keyring-demon my mounted mp3-player is no longer accessible. In /var/log/messages I get the message "gnome-keyring-demon removes usb device". As long as the gnome-keyring-demon is running, I cant not remount the device though it is visible using lsusb. I'm running an FC12 system.
