From 86206641c85a8c9ff16c97fb7799a6822c11a448 Mon Sep 17 00:00:00 2001 From: Sitaram Chamarty Date: Thu, 3 Feb 2011 19:47:11 +0530 Subject: [PATCH] warnings on non-root method were not scary enough (plus some other minor ssh/install related doc enhancements) --- doc/1-INSTALL.mkd | 9 +++++---- doc/ssh-troubleshooting.mkd | 12 +++++++----- 2 files changed, 12 insertions(+), 9 deletions(-) diff --git a/doc/1-INSTALL.mkd b/doc/1-INSTALL.mkd index 6b6332b..9e5c8a9 100644 --- a/doc/1-INSTALL.mkd +++ b/doc/1-INSTALL.mkd @@ -234,10 +234,11 @@ we mean `conf/gitolite.conf` on your gitolite-admin clone. #### (non-root method) directly on the server, manually, without root access -WARNING: if you use this method you'd better know enough about ssh to be able -to keep your keys straight, and you'd also better have password access to the -server so that if you screw up the keys you can still get on, or be able to -"su - git" from some other user on the server. +**WARNING: if you want to use this method your shell access to the git account +on the server should be via `su - git` from some other userid. If that is not +possible, you should (a) know the password in case you screw up the keys AND +(b) know how to force ssh to ask for a password if required, AND (c) know how +to handle multiple keys in ssh.** * from your workstation, copy your `~/.ssh/id_rsa.pub` file to the server. Put it in `/tmp/YourName.pub`. diff --git a/doc/ssh-troubleshooting.mkd b/doc/ssh-troubleshooting.mkd index 8e212b4..594950e 100644 --- a/doc/ssh-troubleshooting.mkd +++ b/doc/ssh-troubleshooting.mkd @@ -38,18 +38,20 @@ code, and documentation.** Other resources: * people who think this is too hard should take a look at this - [transcript][] to **see how simple it *actually* is**. + [transcript][] to **see how simple it *actually* is**. This transcript + uses the 'from-client' method of install. - * someone also wrote a tutorial, see [here][tut]. + * someone also wrote a tutorial, see [here][tut]. This uses the 'non-root' + method of install, to provide a different perspective. * I **strongly** recommend reading [doc/gitolite-and-ssh.mkd][doc9gas], which is a very detailed look at how gitolite uses ssh's features on the server side. Most people don't know ssh as well as they *think* they do; even if you don't have any problems right now, it's worth skimming over. - * there's a program called `sshkeys-lint` that you can run on your client. - Run it without arguments to get help on how to run it and what inputs it - needs. + * there's a program called `sshkeys-lint` that you can run on your client to + figure out which key is doing what. Run it without arguments to get help + on how to run it and what inputs it needs. ----