-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: keychain Version: 2.5.5-3 Severity: normal
Thanks for packaging this most handy utility. After upgrading to keychain 2.5.5-3, the following behavior was encountered when launching a login shell for the first time: *** Begin sample output *** KeyChain 2.5.5; http://www.gentoo.org/proj/en/keychain/ Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL * Found existing ssh-agent (7473) * Found existing gpg-agent (7452) * Adding 2 ssh key(s)... ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory * Error: Problem adding; giving up *** End sample output *** This behavior is repeatable and was tested several times. Keychain is being invoked on the affected system via the user's .bash_profile as shown in the sample script block for bash and zsh in keychain(1): *** Begin .bash_profile excerpt *** # Keychain usage keychain id_rsa id_dsa 80B2D10A [[ -f $HOME/.keychain/$HOSTNAME-sh ]] && \ source $HOME/.keychain/$HOSTNAME-sh [[ -f $HOME/.keychain/$HOSTNAME-sh-gpg ]] && \ source $HOME/.keychain/$HOSTNAME-sh-gpg *** End .bash_profile excerpt *** In case it matters, SSH_ASKPASS is not being set in the .bash_profile script in question. Manually calling ssh-add results in an appropriate password prompt and the reuse of known ssh keys. If I can provide any further information or testing, please let me know. This seems like it may be related to the fix for the issue that was addressed in Bug #324950, though I have not played with the source package to test that theory. Once keychain has the ssh keys, an issue with adding the GPG key is encountered, which I will report separately. Regards, - -- Barry Hawkins site: www.bytemason.org weblog: www.yepthatsme.com Registered Linux User #368650 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDE5/dHuKcDICy0QoRAu4gAKCAkOkkIBTnb+f5C8NhPYgcumtpYQCgwD+D We4mtwET1jAmfaQzKDAHOBY= =Xl0Y -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
