[gccsdk] SimpleGit (!Nettle & ssh keys)

Alan Williams ajw at bigblue.net.au
Sun Nov 18 18:43:17 PST 2018


> I think Nettle's SSH support [not NettleSSH] manages to use keys and uses
> libssh2 on RISC OS, BICBW.


I believe the stock !Nettle only does user/pass.  I worked on this a while
ago and I built a version that would use pre shared keys.  It worked ok on
Virtual Acorn but crashed on my pi so I abandoned it and went back to the
stock one.  Recently I have updated my RISC OS builder VM with the current
GCC-SDK with a mind to fix this.

It might be worthwhile storing the keys somewhere consistent so pre-shared
keys stored for the git client can also be used by !nettle.  I used
!Nettle's hot list 'command' field to pass in the key file name, and at
present use Nettle choices directory to store sshid_dsa and sshid_dsa/pub

Alan







On 19/11/18, 10:00 am, "Theo Markettos" <gcc-bounces at gccsdk.riscos.info on
behalf of theo at markettos.org.uk> wrote:

>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,
>Theo
>
>_______________________________________________
>GCCSDK mailing list gcc at gccsdk.riscos.info
>Bugzilla: http://www.riscos.info/bugzilla/index.cgi
>List Info: http://www.riscos.info/mailman/listinfo/gcc
>Main Page: http://www.riscos.info/index.php/GCCSDK





More information about the gcc mailing list