[ale] Resolved: SSH key question
John Mills
johnmills at speakeasy.net
Tue Aug 11 13:35:02 EDT 2009
Oops -
Problem was a "cockpit error" setting up 'authorized keys.' Fixed those
entries and shared-key logins now work fine.
- JM
>> On Tue, Aug 11, 2009 at 10:07 AM, John Mills<johnmills at speakeasy.net> wrote:
>>> One way I access a remote SSH login is through a 2-way NAT setup that
>>> assigns out-going and incoming hosts' addresses against pools (or some
>>> other algorithm) so my identity at the remote end is something like
>>> <my_username>@<random_hostname_or_IP>.<their_domain>. I tried storing my
>>> originating account's public keys in my remote server's
>>> '~/.ssh/authorized_keys', but since the originating host appears to float
>>> they are not used. Same problem at the originating end: it looks as though
>>> I'm connecting to a different server every few times I connect.
>>> How can I set up an encrypted, shared-key login in this type environment?
More information about the Ale
mailing list