<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Bryan -<br>
<br>
I wish there was a "Simplified Linux Admin" book written with your
approach! It worked as advertised, and when I go to the man pages for
more detail, I have a beginning place to start...a place that works.
This is a writing/learning style that I call "spiral learning": you
start with the fundamentals and expand your knowledge from that point
as needed.<br>
<br>
Many thanks! Now I will create the crontab.<br>
<br>
Todd<br>
<br>
<br>
Bryan J. Smith wrote:
<blockquote
cite="mid1134262612.5853.123.camel@bert64.oviedo.smithconcepts.com"
type="cite">
<pre wrap="">On Sat, 2005-12-10 at 10:13 -0800, Todd Cary wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Jim -
I have read the man pages, and with my lack of experience, they are not
that clear. Do you have another reference to suggest?
</pre>
</blockquote>
<pre wrap=""><!---->
Yeah, public key authentication can seem to use a number of concepts and
terms that seem daunting at first. But after just a little practice,
they become second nature.
In a nutshell (uber-simplified):
1) You generate a key pair on the client -- a public and private
2) You copy the public key to the server
The next time you login to the server, the server "challenges" your
client using the public key, of which, only the client has the private
key to decrypt the challenge and respond correctly (again, mega
oversimplification here).
You do #1 on the client with:
ssh-keygen -t dsa
(enter twice for no passphrase)
You do #2 with something like:
scp ~/.ssh/id_dsa.pub <a class="moz-txt-link-abbreviated" href="mailto:user@server:.ssh/authorized_keys">user@server:.ssh/authorized_keys</a>
[ NOTE: When you run scp that time, you _will_ be prompted for your
password. That's the last time you should ever be though. ]
Now that should be it. You should be able to ssh without being prompted
for a password. If you are still prompted, check the /var/log/messages
files on both the client and server for any errors/issues.
I can get more geeky if you have follow-up questions.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Ariste Software
2200 D Street Ext
Petaluma, CA 94952
(707) 773-4523
</pre>
</body>
</html>