-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
git lfs with ssh #2475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Those transfer-hooks are client-side so we can't make that happen unfortunately. Only way to get real SSH-support is to get it upstream in the issue you linked :( |
The only solution today is to have SSH return a JSON-payload for redirecting it to HTTP(S) git-lfs/git-lfs#1044 (comment) which is fairly straight forward to add:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
I can not get ssh authentification to work so I guess this is still an open issue I don't know where to start for the solution proposed by @bkcsoft . Lines 137 to 147 in b03d780
Can you look again at ssh authentification for lfs in gitea @fabian-z @lunny |
Well, we should already be doing what @bkcsoft suggested and it worked in my original tests. This code is responsible for implementing server discovery by returning the proper URL and authentication token if called via SSH: Lines 292 to 326 in b03d780
It seems there is some confusion about the subject of this issue. One aspect is server discovery / authentication using SSH. This should be implemented and working according to the LFS API docs. Another one is transfer of data with SSH instead of HTTPS. This is currently not part of the LFS specification and therefore also not implemented, still to be decided upstream (see git-lfs/git-lfs#1044) @ukos-git: Could you elaborate on what part of SSH authentication is not working for you? What did you do, what errors are you getting? Please make sure your server has a working HTTPS configuration. @laoshaw: Are you only asking for a pure SSH based transport without HTTPS (as in the linked git-lfs issue)? Do you experience issues when using SSH remotes? Please also make sure your server has a working HTTPS configuration. |
Authentification is working now. ssh ssh://git@mygitproject git-lfs-authenticate user/repo download {
"header": {
"Authorization": "Bearer XYZ"
},
"href": "https://mygitproject/user/repo.git/info/lfs"
} I got probably confused during the setup. Since the gitea implementation is actually working, we should close this issue here. implementation of scp is an upstream git-lfs problem. |
To get git-lfs working with ssh/scp it can be redirected to http/https as native ssh support is not implemented upstream, below is related info:
https://github.com/git-lfs/git-lfs/blob/master/docs/custom-transfers.md#using-a-custom-transfer-type-without-the-api-server
git-lfs/git-lfs#1044
The text was updated successfully, but these errors were encountered: