Re: Problem with ssh-agent and ssh-add
From: Darren Tucker (dtucker_at_gate.dodgy.net.au)
Date: 11/08/05
- Previous message: Innokentiy Ivanov: "Re: X.509 certificate chains and SSH"
- In reply to: Richard E. Silverman: "Re: Problem with ssh-agent and ssh-add"
- Next in thread: sgprasad_at_dacafe.com: "Re: Problem with ssh-agent and ssh-add"
- Reply: sgprasad_at_dacafe.com: "Re: Problem with ssh-agent and ssh-add"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 08 Nov 2005 04:21:07 GMT
On 2005-11-07, Richard E. Silverman <res@qoxp.net> wrote:
>
>> pclose(fp);
>> system("ssh-add -l"); //testing purpose
>
> I imagine the pclose() terminates the agent.
Probably not since ssh-agent daemonizes itself (and since it writes
the pid of the daemon process to stdout which is read earlier, it's
guaranteed to have happened by then).
To the OP: are you trying too run ssh-agent and ssh-add as different
uids? On platforms that support it, ssh-agent will use getpeereuid()
to determine the user on the other end of the socket connection and
will refuse to talk to any processes running as a user other than the
one that started the agent.
What exactly do the SSH_* environment variables get set to? I had
difficulty following your code, but inside the while loop it seemed to
be trying to do something like:
if ((p = strchr(temp_buff, ';')) != NULL) {
*p = '\0';
putenv(temp_buff);
}
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
- Previous message: Innokentiy Ivanov: "Re: X.509 certificate chains and SSH"
- In reply to: Richard E. Silverman: "Re: Problem with ssh-agent and ssh-add"
- Next in thread: sgprasad_at_dacafe.com: "Re: Problem with ssh-agent and ssh-add"
- Reply: sgprasad_at_dacafe.com: "Re: Problem with ssh-agent and ssh-add"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
