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 was deleting some space off my C Drive and I believe I may of accidentally deleted Fedora, or some of it! I have a dual boot with Fedora and Windows XP so when I started my desktop up it would load into fedora by default or I could press a key to load XP! (It rhymes!) Now, however, it instantly loads up into "Grub"
And that's it! Run, Or Exit, or anything really, doesn't work! Except Reboot! So I'm a little stuck. It's an old PC and the Windows XP disc is long gone, if I ever had one! I had this thought that perhaps if I reinstall Fedora from a CD it many bring back the old command prompt and let me get back into XP again? Or, is that crazy talk??
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".
Whenever I boot up my computer, Ubuntu (10.4) brings me to my desktop, then immediately displays a prompt to enter my login keyring. After some searching on the forums, it appears that this is because I set my laptop to auto-login. Am I missing something here, but what does auto-login have to do the the keyring? Why do I even need to enter that password? I understand that many Ubuntu users are picky about security, but why isn't their any option to disable this? It's almost as bad as UAC from Vista, which is one of the reasons I'm dual-booting Ubuntu in the first place. This is an annoying "problem" that has been bugging me since I first installed Ubuntu - how can I change it?
I am getting a prompt namely unlock keyring when i start up my PC and when i type in my password my wireless gets connected automatically... I didnt have this issue before.. My wireless onnection used to start up automatically when i start my PC...
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 about to turn off the prompt for a keyring password at logon following these instructions. But I wonder whether I'm going to be losing anything in the way of security. To eliminate the prompt for the keyring password, am I going to miss out on anything? In other words, just what does the keyring do? If it matters, I don't use Evolution e-mail (I just use old-fashioned web mail). To my knowledge the only passwords stored on my machine are that for my wireless network and whatever website passwords my browser stores.
Been having trouble connecting to the internet and i am no longer being asked for password/keyring prompt at start-up. Something the prompt comes up 5-15 minutes after start-up.
I even manually set 'password at login' but it doesn't even ask me for that?
ps: over here
HTML Code: https://wiki.ubuntu.com/LucidLynx/ReleaseNotes
i found something about Avahi potentially causing a conflict with network configuration - so i typed the following command and am now online at least:
sudo stop avahi-daemon sudo sed -e '/^start/,+1s/^/#/' /etc/init/avahi-daemon.conf
I recently was playing with some gnome settings and I went to System > Preferences > Startup applications then I hit the Options tab and checked "Automatically remember applications when logging out" was testing to see if it actually worked... and it did.. so I unchecked it and restarted again and... it's the SAME 3 applications I was running.. and its stuck..tried checking it again and then closing everything but now it's still doing it with the same 3 apps I had running (Totem, Firefox, Pidgin).Anybody know how to wipe where it's remembering the applications I'm running? so this can stop when I log in.
somehow checking it again and closing everything worked this time, but does anybody know where I can find the find the remaining information for this function? so i can wipe it clean, whatever may be left.
All in a sudden I can no longer login to my desktop (FC10 Gnome). After I typed in my passwd the desktop was trying to spawn for a few seconds (a black screen with curser and blue spashes) and it goes right back to the Login screen again. I tried to boot with 'single' mode and changed my passwd from root but to no avail. Not sure what I did wrong during my last session: I was fooling around with the NFS setup for my new Eval Board.
I finally got my system to boot to a console prompt. This is a fresh installation of fc10 that I have struggled to get working with my old Adaptec 2940 scsi hardware. I am a little fuzzy on the whole gtk, gdm, gnome thing. So how do I go from this console prompt to configuring the new installation with desktop?So let's say I am logged on as root on the console.
I upgraded my dell inspiron 6000 from ubuntu 10.04 to 10.10 then rebooted and now I am stuck at the grub prompt. I am able to boot from a flash drive and have run the boot script. This laptop did not have a dual boot system on it but it did have windows on it at one time, converted to ubuntu.
openSuSe 11.2/Pidgin 2.6.2/KDE4.3.1 Have seen various threads about this, but no real fix. Everytime I start Pidgin I get the annoying prompt to "Enter password for default keyring to unlock".
I always get this prompt in Ubuntu and the option to auto login is grayed out so i cant choose it. Its not a serious issue but does anybody know how to unlock it when i sign in on Ubuntu 11.4?
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.
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'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.
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...".
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 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.
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.
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.
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".
