Hi,

Thanks for your contribution to Debian. Can you please verify that
/usr/bin/ssh-askpass is not a dangling symlink? On Debian systems
/usr/bin/ssh-askpass points to /etc/alternatives/ssh-askpass which point
to the actual ssh-askpass software.

Bye
Cesar Mendoza
http://www.kitiara.org
--
"All truth passes through three stages: first it is ridiculed,
then violently opposed and eventually, accepted as self-evident."
 -- Schopenhauer



On Mon, Aug 29, 2005 at 07:53:02PM -0400, Barry Hawkins wrote:
> 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
> 

Attachment: pgpuei8GpA9rQ.pgp
Description: PGP signature

Reply via email to