Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's all good until I try to clone the git repository I made.
Code:
$ git clone git@HOSTNAME:gitosis-admin.git
Cloning into 'gitosis-admin'...
Enter passphrase for key:
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
It asks for a passphrase, but when I made the key (using PuTTYGen) I didn't put one in there.
When I try to ssh (not using git),
Code:
$ ssh git@HOSTNAME
Enter passphrase for key:
Permission denied (publickey).
Obviously, in both examples I've put my own hostname in. Other users can ssh in just fine.
a) Gitosis is abandoned - use gitolite instead
b) check your /etc/passwd - gitosis from repos on Ubuntu, for example, is under user 'gitosis', not 'git', so it will be ssh gitosis@HOSTNAME
c) ssh git@HOSTNAME - that won't work in any case as Gitosis prevents direct shell login to 'gitosis' user.
This will recreate the public part out of the private part (e.g. in case you lost the public part). If there is a passphrase, it will ask. Otherwise not.
Thank you. I did not know that and am switching to gitolite.
Quote:
Originally Posted by klearview
b) check your /etc/passwd - gitosis from repos on Ubuntu, for example, is under user 'gitosis', not 'git', so it will be ssh gitosis@HOSTNAME
I installed it from source, but thank you, good to know.
Quote:
c) ssh git@HOSTNAME - that won't work in any case as Gitosis prevents direct shell login to 'gitosis' user.
Also good to know.
Quote:
Originally Posted by Reuti
What is the output of:
Code:
$ ssh-keygen -y
It appears this is the problem...ssh-keygen doesn't like my private key. After making a new keypair (with ssh-keygen instead of PuTTY), everything seems to be working.
Just to elaborate: PuTTY has its own format of a private key. You can convert this format in puttygen itself into the openssh format (besides the commercial format). There is a menu entry for it.
Just to elaborate: PuTTY has its own format of a private key. You can convert this format in puttygen itself into the openssh format (besides the commercial format). There is a menu entry for it.
I had done this (export OpenSSH key I think the option's called?) but I probably messed it up somehow moving everything around.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.