linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Samuel <samuel@bcgreen.com>
To: "Gerd Müller" <gerd.bomber.mueller@web.de>
Cc: linux-admin@vger.kernel.org
Subject: Re: SSH Athentification with public key
Date: Tue, 27 May 2003 10:22:59 -0700	[thread overview]
Message-ID: <3ED39EF3.70706@bcgreen.com> (raw)
In-Reply-To: <oprptltevdfb0muc@gmane.org>

Gerd Müller wrote:
> Hello,
> 
> i want to update hourly a remote mirror-server with rsync via ssh. In 
> order to enable the file-server to establish a ssh-session without 
> password prompt, i created on file-server a keypair with ssh-keygen -t 
> rsa (empty passphrase) and copied the public key (id_rsa.pub) to the 
> /root/.ssh/authorized_keys File (on mirror-server). This file didn't 
> exist before.

Try:
	cd .ssh
	chmod og-w auth* . ..
	mv authorized_keys authorized_keys2

The authorized_keys file must be owned and readable by root,
(or owned and readable by the user that  is being authenticated for)
The authorized_keys file, the .ssh directory and your home directory
must ONLY be writable by the owner. They CANNOT be group-writable.

Matt Hemingway wrote:
 > Could be a couple things:
 >
 > 1. When you copied the id_rsa.pub file, did you do a copy and paste from an xterm window to an xterm window or did you sftp/scp/ftp the file over?  I had a similar 
problem, where I had copied the contents from an xterm window to an xterm window and instead of the lines wrapping at the end of the window, line breaks were inserted. 
Each public key entry must be one line.
 >
 > 2. Make sure the authorized_keys file is owned and readable by root.
 >
 > Also, try ssh -vvv root@mirror-server and see if you get any usefull info.   strace can come in handy as well.

if you're using the DSA or RSA public keys. They should go into the
authorized_keys2 file.
                ^
It's only identity.pub (the ssh1 public key file) who'se contents
get coppied into authorized_keys


-- 
Stephen Samuel +1(604)876-0426                samuel@bcgreen.com
		   http://www.bcgreen.com/~samuel/
Powerful committed communication, reaching through fear, uncertainty and
doubt to touch the jewel within each person and bring it to life.

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2003-05-27 17:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27  7:30 SSH Athentification with public key Gerd Müller
2003-05-27 14:57 ` Matt Hemingway
2003-05-27 22:40   ` Keith Morse
2003-05-28 23:06     ` Stephen Samuel
2003-06-02 16:48       ` Keith Morse
2003-05-27 17:22 ` Stephen Samuel [this message]
2003-05-27 17:55   ` Mikel Bauer
2003-05-27 18:12     ` Jean M. Bouchara
2003-05-27 21:15 ` pacho baratta
2003-05-28  6:31 ` Solved: " Gerd Müller
  -- strict thread matches above, loose matches on Subject: below --
2003-05-27 18:08 gerardo juarez-mondragon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ED39EF3.70706@bcgreen.com \
    --to=samuel@bcgreen.com \
    --cc=gerd.bomber.mueller@web.de \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).