Dear Linaro Team,

no I am not confusing with the ssh operations used for the hacking session. My problem is to access our company git server. It just supports ssh access.

On 25.03.2016 13:00, linaro-validation-request@lists.linaro.org wrote:

Send linaro-validation mailing list submissions to linaro-validation@lists.linaro.org

To subscribe or unsubscribe via the World Wide Web, visit https://lists.linaro.org/mailman/listinfo/linaro-validation or, via email, send a message with subject or body 'help' to linaro-validation-request@lists.linaro.org

You can reach the person managing the list at linaro-validation-owner@lists.linaro.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of linaro-validation digest..."

Today's Topics:

1. git ssh access (Felsch Marco)
2. Re: git ssh access (Neil Williams)

---

Message: 1 Date: Thu, 24 Mar 2016 15:36:52 +0100 From: Felsch Marco felschm@tqsc.de To: linaro-validation@lists.linaro.org Subject: [Linaro-validation] git ssh access Message-ID: 56F3FB84.5020609@tqsc.de Content-Type: text/plain; charset=utf-8; format=flowed

Dear Linaro Team,

does LAVA support ssh access for git to receive test definitions?

e.g. definitions: -repository:ssh://git.linaro.org/lava-team/hacking-session.git from:git path:hacking-session-debian.yaml name:hacking

---

Message: 2 Date: Thu, 24 Mar 2016 15:33:51 +0000 From: Neil Williams codehelp@debian.org To: linaro-validation@lists.linaro.org Subject: Re: [Linaro-validation] git ssh access Message-ID: 20160324153351.25e552ab@sylvester.codehelp Content-Type: text/plain; charset="utf-8"

On Thu, 24 Mar 2016 15:36:52 +0100 Felsch Marco felschm@tqsc.de wrote:

...

Dear Linaro Team,

does LAVA support ssh access for git to receive test definitions?

e.g. definitions: -repository:ssh://git.linaro.org/lava-team/hacking-session.git from:git path:hacking-session-debian.yaml name:hacking

No, it does not and I'm not sure how that could be expected to work - ssh needs a user & authorisation. Which ssh user is this expected to be doing the clone? How does this get configured at the remote repository?

Cloning a git repo using ssh is typically for read:write operations to allow git push and similar. That is not something LAVA is likely to be doing. There are also security implications of allowing a LAVA test shell to have SSH credentials with third party sites.

What are you trying to achieve? With the example given, git.linaro.org offers http and https. Are you confusing this with the ssh operations used for the hacking session itself? That is your user and your private key authorising against your public key which needs to be included in the job submission.

If what you want is some level of encryption to guard against packet sniffing, https is what you want.