2009/9/3 Robert Collins <email address hidden>:
>> 2- Hooking into openssh so it calls back to our uifactory to get the
>> password and other things.
>
> AFAIK openssh only allows you to do that if you are an agent: and this
> is something I whole heartedly approve of.
Right, we'd perhaps need to be a passthrough proxy for the real agent.
This may be more trouble than it's worth. gpg documents a protocol
whereby you can provide quite a powerful gui but openssh less so, at
least in the man pages.
> On Modern linux machines, you will get a gui prompt for ssh connections
> already; we don't need to do anything special to make this work.
However, you don't get a gui message afaik for eg
* failed to connect
* unknown host key
* wrong host key
We could handle some of these a bit better by parsing the output of ssh.
Anyhow, I've split this to bug 424069 for the unix issue, as it's
mostly separate.
2009/9/3 Robert Collins <email address hidden>:
>> 2- Hooking into openssh so it calls back to our uifactory to get the
>> password and other things.
>
> AFAIK openssh only allows you to do that if you are an agent: and this
> is something I whole heartedly approve of.
Right, we'd perhaps need to be a passthrough proxy for the real agent.
This may be more trouble than it's worth. gpg documents a protocol
whereby you can provide quite a powerful gui but openssh less so, at
least in the man pages.
> On Modern linux machines, you will get a gui prompt for ssh connections
> already; we don't need to do anything special to make this work.
However, you don't get a gui message afaik for eg
* failed to connect
* unknown host key
* wrong host key
We could handle some of these a bit better by parsing the output of ssh.
Anyhow, I've split this to bug 424069 for the unix issue, as it's
mostly separate.
-- launchpad. net/~mbp/>
Martin <http://