On 08Sep2018 17:43, bruce <badouglas@xxxxxxxxx> wrote:
Thanks for replies, found the answer was a weird corrupt
authorized_key file. Simply copied the pub keys and reinserted. For
some reason, it appears that one of the pub keys had been split witn a
"\n" in it..
Cut/paste from a terminal or email can sometimes do that.
If you have root privileges on machine B you can look at the ssh log
(/var/log/auth.log or something else, depending on the system - "ls -ltra" in
/var/log will at least show you the active log files to make finding it easy).
If you "tail -f /var/log/auth.log" (adjust to suit) on machine B as you do your
sshes you will see useful log messages scroll by. They can be very helpful in
distinguishing "ssh going to wrong host" (no activity), "ssh as wrong user on
machine B", "ssh as user B but bad keys" and so forth.
For security reasons you see little of this detail on the machine A side as all
such information helps attackers.
Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
