Nick's picture
Nick - Tue, 2012/09/11 - 23:27

I've been going pretty strong with git but I still can't seem to figure out how to prevent it from asking for the password everytime I pull/push.  Everything I've read suggests that you need to copy the SSH key generated client side and put it into the ~/.ssh/authorized_keys file. 

 

However, my appliance only has a ~/.ssh file that reads:

 

ssh-keygen -f filename -C 'a comment' -N '' -t rsa -q

 

And of course because of this I can't even create the authorized keys file at that location.  Is there something different that needs to be done for the TKL appliance as opposed to standard linux servers to authenticate multiple users for Git?

Forum: 
Support
Tags: 
git
revision control
ssh
Jeremy Davis's picture

Jeremy Davis - Wed, 2012/09/12 - 00:32

But I use GitHub a fair bit and I'm assuming that the usage of SSH keys would be similar. So I suggest that you have a look at this. These steps are to be done from the client machine (not the appliance) but if you aren't using Linux then this won't work for you. I think PuTTY can create the correct keys, but I'm not sure how... Obviously steps 4 & 5 only apply to GitHub (but you'll still neeed to upload the generated keys to the appliance but I'm unclear where they'd go), but the first few steps would be relevant I would think. Perhaps google may give you a more directly relevant answer?

Also if you don't want to have to use a passphrase then you can just leave that part blank (ie hit enter).

Add new comment