-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ken Mink wrote: | Hmm. | I had the same problem and I went a completely different route. While | the previous solution makes more sense, I'm throwing mine out to see | if it was a really bad idea. | | I took the host keys from the machine that is available on port22 and | used them as the host keys for the machine that is available on the | non-standard port. It's worked fine. | | Ken | | Yeah, that works too =D. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFB9SiIwsRpgTiXSOERApDVAJ9e1JFq1A5zQeh975UpSoHr9vPbOgCfUzfN J6nJ0GYvTsexWyUrvGvaTOo= =RkIm -----END PGP SIGNATURE----- -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
