theo at markettos.org.uk
Sun Nov 18 15:00:21 PST 2018
On Sun, Nov 18, 2018 at 10:41:33PM +0000, Jeffrey Lee wrote:
> Also, a quick look through the libssh2 source suggests that it'll try to get
> your public/private key by using a Unix domain socket to connect to the ssh
> agent - which obviously won't exist on RISC OS. So it might be that that
> error message is indicative of that failure, or it might be that there are
> two problems to solve.
That's SSH agent authentication. I'm not sure whether RISC OS/Unixlib will handle
Unix domain sockets (RISC OS doesn't really do IPC as there's no P to speak
of), but if not is there a way to make it use use key files
($HOME/.ssh/id_rsa and similar)?
I think Nettle's SSH support [not NettleSSH] manages to use keys and uses
libssh2 on RISC OS, BICBW.
> I've added a !Help file which covers common operations and RISC OS specific
> usage info. It's a bit awkward to use, but since "awkward git client" is
> better than "no git client", I think it's probably in a suitable state for
> us to make a first release.
I'll try and turn the handle manually when I get a minute, unless anyone
gets there first.
Thanks for the patches,
More information about the gcc