The current roadmap for keychain is as follows:
keychain 2.7.0 to be released in the next few weeks, a maintenance
release with various small improvements and a new color scheme as
well.
keychain 3.x development will begin soon, using a new code base, more
modular, structured design, and additional functionality. The new code
base is necessary as the current keychain code base has a pretty
complex design and a lot of global variables that make it unsuitable
for new extensions.
Please note that the version of keychain in git (on funtoo github) is
currently flaky and will be fixed in the next week or so. I was trying
to reduce the complexity of the code, and some of my experiments
worked, and others didn't. My successfull experiments will make it
into 2.7
I'll save the other stuff for 3.0.
-Daniel
I had an unscheduled reboot today - power failure.
At KDM can't login, so went to TTY1,
login as user, which starts keychain,
exit TTY1, and now login at KDM.
I really don't mind this since I reboot so infrequently.
Is this known and/or expected behavior, or a feature?
I don't recall reading anything about this in the docs.
Best wishes for this holiday season,
Mike
It could be a locking bug. Can you reproduce it without using KDM?
-Daniel
Hi Daniel
I can reproduce it, but maybe it's because I've got a somewhat special
setup :x
Qingy starting ~/.xsession
keychain in ~/.xsession doesn't lock my system, it just gives me a
blackscreen, switching to another tty is still possible (same happens
with keychain in .bash_profile)
My solution for now was deleting keychain
from .xsession/.bash_profile, creating another file for keychain and
sourcing that file in my .zshrc
Maybe not the most elegant way, but it's working
Uwe
Oh sure, booting to a TTY is fine. At the shell login, enter the user
password, then the keychain password once and everything is OK.
So when I boot directly to KDM, enter my user password, I'm thrown
back to KDM instead of login to KDE.
I suspect that this is because keychain needs a password, but there is
no dialog in KDM to enter the keychain password.
So I'm thinking that if keychain could be configured to use the
password the user enters at login, then the need for 2 passwords
(login and keychain) would be avoided.
Not sure if this makes any kind of sense. :)
MH
In $HOME/.bashrc I had:
eval $(keychain --agents ssh --eval id_dsa) || die
It works now with this:
eval $(keychain --eval id_dsa)
Sorry. :)
MH