1 Feb 2003 01:08
ssh keys from two behind-the-firewall boxes?
will trillich <will <at> serensoft.com>
2003-02-01 00:08:31 GMT
2003-02-01 00:08:31 GMT
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
(Continue reading)
This way, even if this key is stolen, all the thief can do is send you
a e-mail and invite you to log into their machine without key word.
> ~/.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?
SSH checks IP as a part of prudence but its core authentication process
is not IP based.
> workstation workstation workstation
> 192.168.1.2 192.168.1.100 192.168.1.201
> key xyzpdq key 1234567 key x0x0x0x0
RSS Feed