this is probably item #2 of the really-obvious-faq that i'm not
yet aware of, so i'll go ahead and ask because i haven't taken
the opportunity to look like a goober in, oh, about half a day,
now...
doing the ssh-keygen thing works like a charm; you copy your
private keys to the remote box and then just slap it into your
~/.ssh/authorized_keys file and poof, no more passwords! so now
you can run ssh-driven scripts without having to worry about the
username/password interruption.
it's ip-based, isn't it?
workstation workstation workstation
192.168.1.2 192.168.1.100 192.168.1.201
key xyzpdq key 1234567 key x0x0x0x0
| | |
+---------------+----------------+
|
192.168.1.5
firewall
208.33.90.85
|
{web}
|
11.22.33.44
remote box
but the remote just sees all the 192.168.1.* boxes as
208.33.90.85, right? where's the doc on getting ALL the
192.168.1.* boxes to ssh password-free to the remote machine?
(or, when it challenges, the challenge only reaches the
firewall, something like that. hmm?)
so far, my experience has been that i can ssh password-free
only from the 'on-the-public-link' firewall.
--
I use Debian/GNU Linux version 3.0;
Linux server 2.4.20-k6 #1 Mon Jan 13 23:49:14 EST 2003 i586 unknown
DEBIAN NEWBIE TIP #65 from der.hans <[EMAIL PROTECTED]>
:
Wondering about which KEYBOARD SHORTCUTS ARE UNDERSTOOD BY BASH?
Enter this at your bash shell prompt:
bind -p | less
and see how much of that you can interpret :). For more info
about all of this stuff, do "man bash" then search for "emacs"
and "readline" (to search a manpage, press / and then the pattern
to look for).
Also see http://newbieDoc.sourceForge.net/ ...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
