Skip to content
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

Using SSH keys #44

Open
swolfish opened this issue Oct 8, 2015 · 5 comments
Open

Using SSH keys #44

swolfish opened this issue Oct 8, 2015 · 5 comments

Comments

@swolfish
Copy link

swolfish commented Oct 8, 2015

Is it possible to use ssh keys instead of user and pass?
So ssh keys of users permitted to do with project's git repository are also on the LFS server and there's no need for double credential in the project.

@Gfurst
Copy link

Gfurst commented Jan 7, 2016

Would also like to see this, though unlikely since it uses http protocol instead, but perhaps a midway communication only for the auth.

@maciej-lech
Copy link

Me either.

@Gfurst
Copy link

Gfurst commented Jan 10, 2016

I've asked on the github-lfs git-lfs/git-lfs#923
It seems that github works this way, when authenticated via ssh, it passes a certification to the https to bypass, if using regular https protocol you only need to authenticate once too.

In both cases I think the server as to be integrated somehow(same https server serving both git and the lfs host). When this is setup you don't even need to set a custom address for the lfs host (per remote), the default path it looks is .../repo.git/info/lfs

@kemin711
Copy link

kemin711 commented Jan 9, 2024

Just a silly question: where do you put the private key and certificate. I am learning how to use the test server with https. In Apache, you put in the configu file:

   SSLCertificateFile /path/to/certs/hellfish.test.crt
   SSLCertificateKeyFile /path/to/certs/hellfish.test.key

@chrisd8088
Copy link
Member

@kemin711 -- note that SSL/TLS for HTTPS is different from SSH, which is what this issue is about. In general, we prefer a new issue to a comment on an unrelated issue. To answer the question, though, I believe you can use any location you like so long as you pass the paths to the key and certificate files in the appropriate environment variables, as documented in the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants