Re: Resored account

David Cooper <[email protected]> writes:

> I apologize that your account was somehow missed in the host
> migration. Why didn't you say something sooner?

Good question.  I think the problem I had predated the host migration so
the host migration did not change the status quo for me.

> I just synchronized your account and its home directory contents, 
> replete with its .ssh/authorized_keys, to the current host, so you
> should be able to ssh to current common-lisp.net now. If not, please
> let me know. 

Thank you.  Will do.

> And, I added you to sudo group so you can add an additional user with
> restricted access for doing the rsync's, if you like.   And feel free
> to look into installing the needed rsync service, and go ahead and
> install it if you can, if that is running on the old host. Our initial
> goal is to replicate as many of the legacy services as possible. Ever
> since I started using rsync heavily (maybe 15-20 years ago), it always
> seems to go by default over ssh, so I'm not familiar with the actual
> rsync transfer protocol or service per se.  Maybe I should be, if the
> server I'm purporting to administer has documentation which assumes
> that...

For whatever it's worth, this inspired me to try and point the rsync to
the legacy host which does seem to accept connections suggesting that
the service is still running.

I think rsync uses ssh when you specify a source or destination that
includes the name of a user and a host.  For anonymous rsync that talks
directly to rsyncd, ssh is not used.

Anyway, sounds like the next step is for me to dust off my old private
key and get myself logged-in again.  Once that happens, I can scope out
what is needed to restore anonymous rsync access.  If I can make it
work, I hope others can benefit from it, too.

Kindly,

Carl